Trajectory

The description states that Trajectory is a Chrome side-panel extension. It analyzes ChatGPT conversations currently open in the browser and organizes them into two views:

• Arc: Shows the conversation as a sequence of phases.
• Findings: Surfaces patterns, tensions, and decisions across exchanges.

Each finding is connected to supporting messages, which can be viewed directly via a "Show in chat" feature. The extension uses:

• Content scripts to extract messages from ChatGPT
• Chrome storage for caching
• A Node.js/Express backend that interfaces with OpenAI’s Responses API
• Structured Outputs and GPT-5.6 for analysis

The system avoids accessing private credentials or URLs, and only runs analysis upon user request.

Inference The product is a browser-based tool designed to enhance understanding of long-form AI conversations by structuring them into phases and findings.

The author claims Trajectory helps users understand how thinking evolved in a ChatGPT conversation. It is positioned not as another summary but as a way to reconstruct the arc of thought and surface patterns that may be hard to notice during real-time interaction.

Key positioning elements:

• Not just a summary, but a tool for understanding reasoning paths
• Emphasis on verifiability: users can inspect evidence behind each finding
• Focus on user agency, not AI dictating conclusions

Inference The product aims to improve cognitive clarity and traceability in AI-assisted thinking — particularly useful for complex or multi-step decision-making.

The description does not explicitly define a target customer segment. However, the author’s stated use case is:

“I spend a lot of time working through ideas in ChatGPT.”

This implies an early-stage user who engages deeply with ChatGPT for ideation, problem-solving, or research.

Inference The primary ICP likely includes individuals using ChatGPT for complex tasks requiring structured thinking, such as writers, researchers, strategists, or developers exploring solutions.

There is no evidence of pricing, monetization strategy, or business model in the description. The project was submitted to a hackathon and appears to be a personal development effort.

Inference No commercial model has been established yet; this remains unproven.

The extension is built using:

• Manifest V3 Chrome APIs
• Content scripts, background workers, side panel UI
• Node.js + Express backend
• OpenAI Responses API with Structured Outputs
• TypeScript, HTML/CSS, Vite, npm, Codex

Key technical features include:

• Transcript fingerprinting for cache invalidation
• Deterministic validation of model outputs
• Message normalization and stable identifiers
• Sanitized demo mode without OpenAI keys or credentials

Inference The product shows a strong engineering foundation, with attention to correctness, performance, and user experience.

There is no evidence of traction, including:

• No customers
• No revenue
• No usage metrics
• No public deployment or distribution beyond the Devpost submission

The author notes that the product went through many versions before settling on its current form, suggesting iteration and refinement.

Inference The project is at a developmental stage, likely pre-launch, with no proven adoption or market validation.

The description does not mention any direct competitors. However, it implies a space where:

• AI conversation tools are used for complex tasks
• Users seek clarity and structure in long conversations
• Tools exist to summarize or extract insights from AI interactions

Inference Trajectory operates in a nascent market segment — potentially overlapping with note-taking, idea-tracking, or cognitive support tools. No known competitors were cited.

1. No traction or usage data: The project is described as a personal effort without any evidence of real-world adoption.
2. Limited scalability assumptions: The extension works only within Chrome and for ChatGPT; no cross-platform support or broader AI platform integration mentioned.
3. Dependency on OpenAI APIs: Reliance on GPT-5.6 and structured outputs may limit flexibility if API availability or pricing changes.
4. Single-person team: With only one member, the ability to scale development or product management is unclear.

Inference The lack of traction and limited scope raise questions about viability as a commercial product.

1. How many people are currently using Trajectory?
2. What feedback have you received from early users?
3. Are there plans to expand beyond ChatGPT or Chrome?
4. Has the extension been tested with real-world use cases beyond your own?
5. What is the roadmap for monetization or commercialization?
6. How do you plan to handle changes in ChatGPT’s interface or API?