Code is the layer you stop reading. The next one is the user journey.
Write what should be true for your user in a few plain sentences. Bring any coding agent. It builds the change, runs the journey in your real product and shows you every step.
Get early accessShare my work by link
Say what should be true. See if it is.
A journey says who's involved, where they start, what they do and what should be true after. No code. Your agent follows it in the real product and checks each step.
Bring any agent.
Use the coding agent your team already has. Journeys are an open format, so any agent can run them and send back the results.
Review what your user sees.
Agent pull requests keep getting bigger. A journey run shows each step as a screenshot, so you see whether the product works without starting from the diff.
Anyone on the team can write one.
PMs, designers and engineers write journeys in the same plain sentences. Engineers set it up once.
Open source at the core.
The journey format and the runner are open source. Coming with Cloud: run history, a second check on every run, and review for your whole team.
How we build Tempo now
The journey is the missing layer between what people want and the code agents write.