A record built for understanding
Commits are excellent evidence of what changed. Issue trackers explain planned work. Raw agent transcripts capture everything—and therefore make the important moments difficult to find. Journey occupies the space between them.
Its structured MCP tools let a coding agent preserve a small set of decisions, problems, and resolutions while the work is still fresh.
Three principles
- Sparse by default. A useful journey contains only meaningful events.
- Provenance over polish. The record should say who proposed and who decided.
- Readable by people. The result should help teammates, reviewers, and future maintainers quickly understand a build.
Built in the open
Journey is organized as a public landing site, a hosted web app, a Python API and MCP server, a CLI, and shared contracts. Start with the documentation, then explore an example journey.