A new repository,understood by lunch.
Ask an agent to map the codebase instead of reading it cold. It runs the project in a terminal card, clicks through the running app in a browser card, traces how a request flows and writes it all into a note — with a list of what only your team can answer.
A three-package monorepo, a map in CODEBASE.md, four questions for the team. Allow the install when it asks.
Your first day on a repo: the agent runs it in a terminal card, walks the app in a browser card, writes a codebase map into a note and lists the questions to ask the team — without editing a line.
Read-only on purpose
Say “don’t change any code” and it doesn’t — every command it wants to run still asks you first.
Runs it, not just reads it
The app comes up in a terminal card and gets clicked through in a browser card, so the map matches what really runs.
A map that stays
The result is a Markdown note on the canvas: folders, how to run, a request end to end, the gotchas.
Questions, not guesses
What the code can’t explain goes onto a todo card — your agenda for the first chat with the team.
From clone to map
Four cards around one agent.
More ways to ship with agents
Every scenario runs on the cards you already saw — pick the next one.
Start your next repository with a map
Your agent, your machine, no edits.
macOS and Linux are coming later.
The first-run wizard installs an agent CLI, Git and the dictation model for you — or skips each step.