Decisions
Record the choice, the alternatives, and the reasoning that made the trade-off appropriate.
npm install -g @tryjourney/cli
Your code shows what you built.
Journey shows how you built it.
Automatically capture the decisions, trade-offs and
problems that shaped your work.
Built into the work
The story between the commits.
Journey gives your coding agent a small set of structured MCP tools. The agent records only the moments that explain why the code became what it is.
agent · Journey MCP
// A meaningful trade-off appears
journey_record_decision({
title: "Keep SQLite for the MVP",
context: "One local deployment",
alternatives: ["PostgreSQL"]
})
✓ Decision added to this journey
Provenance and reasoning preserved.
Provenance and reasoning preserved.
Problems
Capture meaningful blockers and failures when they change the path of the implementation.
Resolutions
Link the fix back to the original problem so the completed learning remains easy to follow.
Signal, not surveillance
Remember the reasoning. Leave the noise behind.
Journey does not store raw conversations or routine edits. It creates a sparse, readable trail of the engineering moments your future team will actually need.
No raw conversation pipeline
Your prompts and full agent sessions are not the product. Only structured events are recorded.
Provenance stays attached
Journey distinguishes the person who made a decision from the agent that proposed an approach.
Readable outside the repository
Publish a concise journey for teammates, reviewers, hiring managers, or your future self.
A useful artifact
A build log people will read.
Each published journey turns structured events into a calm, scannable explanation of how a project took shape—not a transcript and not another wall of commits.
Engineering journey · 23 events
Open example Building Try Oz without premature infrastructure
Decision 01
PostgreSQL over MongoDB
Relational data matched the relationships between users, projects, and events.
Problem 02
Processing slowed inside the request
Enrichment work made the interactive path increasingly expensive.
Resolution 03
Move work to a background worker
The request stays predictable while event processing continues safely.
Your next build starts here
Make the work worth remembering.
Connect Journey to Codex or Claude Code, then keep building. The meaningful moments become a story as the work happens.
Start your journey