A page for answering Plan2Code's questions, reading what it has
written and approving things, instead of typing it all into the
terminal.
New here?
Everything stays on this computer. Both ends have to be running.
A small program running on your own machine, started for you by
Plan2Code in your terminal. Nothing here goes over the internet, and
there is no account and nothing to install.
On this machine only
The address starts with 127.0.0.1, which always means
"this computer". Nothing you type leaves your machine, and a colleague
cannot open your link from theirs. To work through a session together,
share your screen.
The app loads this page from 127.0.0.1, which always
means "this computer". Nothing you type leaves your machine, and the
page's address stays inside the app, so there is no link to pass
around. To work through a session together, share your screen.
How long it runs
It stays up while this tab is open. Close the tab and
it shuts itself down 2 minutes
later. It also stops after 30
minutes without hearing from anyone, and after
4 hours unless answers you sent are still waiting for the agent. Reopening the same link brings everything back: nothing you
typed is kept in the browser alone.
It stays up while the app's window shows it. Close the
window and it shuts itself down 2
minutes later. It also stops after 30
minutes without hearing from anyone, and after
4 hours unless answers you sent are still waiting for the agent. When it
stops, the app's own bar notices and brings it back on the same
session, or offers Reconnect the console: nothing you
typed is kept in the window alone.
Two halves, both running
The terminal is the other half. This page collects your
answers; Plan2Code, in the terminal you started it from, is what reads
them and writes the files. Both have to be running for a question to
reach you or an answer to reach it.
The terminal panel is the other half. This page collects
your answers; Plan2Code, the agent running in the app's terminal panel,
is what reads them and writes the files. Both have to be running for a
question to reach you or an answer to reach it.
If it stops. Press Send anyway. Answers are written to
disk the moment they leave this page and are held until something
collects them, so starting Plan2Code again picks them up where you
left off. Nothing is lost by closing this tab either.
When something looks stuck
This page and Plan2Code in your terminal are two programs, and either
can stop without the other. Nothing you have typed is lost either way.
Check this first
If nothing seems to be happening, look at your terminal. Plan2Code
often stops there to ask your permission, and this page cannot see it.
What you might see
You see
The line beside Planny stays quiet for half a minute or more while it is working.
Likely cause
A permission prompt is waiting in your terminal.
Do this
Switch to the terminal and answer it.
You see
Not running (Planny gray and still).
Likely cause
Plan2Code has not checked in for a few minutes.
Do this
Look at the terminal. If it is idle, type continue there.
Look at the terminal panel. If it is idle, press continue in the line beside Planny, which types it there for you. Panel collapsed? Press terminal in that line to expand it.
You see
Not connected (Planny faded, his star shut).
Likely cause
The program behind this page shut itself down.
Do this
Ask Plan2Code to resume the session (or run the command again), and use the new link.
You see
Nothing on the page changes after you press Send.
Likely cause
The agent is busy, or has finished its turn.
Do this
Your answer is saved. Check the terminal.
Whatever you find, nothing you have typed is lost.
Not running, or not connected?
Not running (Planny gray and still): this page is
fine, but Plan2Code in the terminal has not checked in for
3 minutes. It may have finished
its turn, hit an error, or be waiting on you there.
Not connected (Planny faded, arms hanging, his star shut in red):
this page cannot reach its own program, after
8 seconds without contact.
Usually it has shut itself down; see "Getting a new link" below.
"Reading Planny" shows every mood side by side.
It may be waiting for you in the terminal
Plan2Code sometimes stops in the terminal to ask your permission
before it runs a command or changes a file, and this page cannot see
that. After about 30 seconds of silence while it is working, the line
beside Planny asks "Still working, or waiting on an approval in your
terminal?" Have a look at the terminal: answering there sets it going
again.
If it stays quiet a couple of minutes longer, the line changes to
"Still working on it. Longer tasks can go a few minutes between
updates", with Planny still
in his working pose. It may be busy, or still waiting on you in the
terminal; the terminal is where to look. A build that said a task may
take longer gets that long before the line changes.
Hands-off modes, such as auto mode in Claude Code or
smart mode in Devin, cut down on those stops, though some
may still need you.
Answering anyway
You can keep answering and press Send while Plan2Code is not running.
What you send is written to disk and held until something collects it,
so starting Plan2Code again picks it up where you left off.
Getting a new link
The program behind this page shuts itself down:
2 minutes after the last tab
showing it closes,
2 minutes after the app's
window closes,
after 30 minutes without hearing
from anyone, or
after 4 hours, unless answers
you sent are still waiting for the agent.
To get it back, ask Plan2Code in the terminal to resume the session,
or run the step's command again, and use the new link it gives you.
Everything you typed, sent or not, is still there.
resume the session and print the web console address here
Finding your way around
The page is laid out the same way in every session: a bar across the
top, the outline on the left, the question or document in the middle,
your notes on the right and the Send button at the bottom.
The numbers follow the sections below, top to bottom.
The top bar
The name of the step you are in, and the session's title.
The progress bar, for example "4 of 9 answered", or
"4 of 9 done" while something is being built.
The gear button opens User Preferences, and the
? button beside it opens this Help. Preferences has four tabs:
your theme, card width, colors and role, then agents and models,
cleanup, and sounds and whether Activities shows.
The megaphone button opens GitHub in a
new tab, where you can report a bug or suggest an idea.
The megaphone button opens Plan2Code's
GitHub issues, where you can report a bug or suggest an idea.
The die beside it opens Activities,
small games to play while you wait. See "Activities".
Stop session ends the session and saves your place.
See "Stopping and finishing".
The triangle beside it, pointing left, saves your
place and takes you back to the dashboard. It is there on every step
except the dashboard itself.
Planny and the outline, on the left
Planny sits at the top, with a line beside him saying whose turn it is
and what Plan2Code is doing. Below him the outline lists the session's
topics and every question in them, with how many are settled. Click any
question to jump to it.
The view tabs
Under the top bar: Questions first, then
Overview when the session is working on a spec, then
one tab per document Plan2Code has written, and Ask,
always last.
Each tab remembers where you scrolled for as long as this browser tab
stays open.
Moving between questions
Previous and Next under each card walk
the questions still waiting for you, so you never have to hunt for the
next one in the outline.
Notes, on the right
Notes on this shows the back and forth about the
question you are on, with a box for a note of your own. See "Notes and
attachments".
The footer
What is ready to send, on the left.
In the middle, the folder the session was started from, any folders
you added, and its git branch. Click it to open your workspace. See
"Your workspace".
Clear and Send to Plan2Code on the
right. See "Sending and what happens next".
Your notebook
The Notebook button, a small notebook with an elastic
band, sits beside Stop session on every screen. It opens a notebook of
your own for this folder, somewhere to jot things down as you go.
A notebook is a row of tabs, each with its own text
and its own pictures. + New tab asks for a name
first. Notes you made before tabs existed show up as a tab called
Notes.
Under the row, Rename changes the current tab's
name (double-click a tab or press F2 works too). Drag a
tab to reorder it, or use Move left and
Move right, or Alt with the arrow keys.
The tab you leave open is the one you come back to.
Delete asks twice before it removes a tab, and
takes its text and its pictures with it. That cannot be undone.
With no tabs left, you are asked to make one.
Text is styled as you type. Write Markdown, such as
**bold** or # Heading, and headings grow
and bullets draw in place. The marks come back on the line you are
on.
Images go in the strip under the text. Paste one, drop one on the
notebook or press Add image. Click a picture to see
it full screen: the arrow keys step through them and
Esc closes it. The × on a picture asks
before it deletes it.
Everything saves as you go, one notebook per project folder and one
folder per tab on disk. There is no Save button.
It is private to this machine and never sent to Plan2Code.
Private: the agent never reads your Notebook. A tab reaches it only
when you start a workflow with it.
A lit card's confirm pane can offer Start with a note from
your Notebook. On the dashboard, Pathfinder, Plan, Quick
Task and UI Prototype offer it on Start fresh, Diagnose whenever
it is lit, and Revise plan on a picked spec with no plan change
waiting. A tab you started a workflow with wears a
small sent badge.
Two open pages on the same folder share one notebook. If both change
it, the last save wins.
Cleanup, in User Preferences, offers to remove a
notebook only after a month untouched. Nothing removes it on its own.
Your workspace
The folders Plan2Code uses as context in this session: the folder you
started in, plus any others you add, such as a shared library or a
design folder next door.
Opening it
Click the folder name in the middle of the bottom bar. It shows your
folder's name and branch, such as shop · main, and
shop + 2 folders · main once you have added some.
It carries across steps you start from the dashboard.
Remembered for next time
Every change is saved as you make it, so the next console session in
this folder starts with the same folders.
Each spec keeps its own list. The first time you pick a spec on the
dashboard it starts as a copy of the project's list (the one shown
under Start from scratch), and after that the two
are separate. Picking a spec loads its list; the line under the
dialog's title says whose list you are looking at.
The lists live in workspaces.json in your own
Plan2Code settings folder, beside your look and feel, never in the
project. Finalize offers to forget a spec's list when it archives the
spec.
Adding a folder
Paste or type its path and press Add. A path such as
../shared counts from the folder you started in.
Or press Browse… to pick it from your computer's own
folder window. Browse… is hidden when the page is being reached from
another machine; type the path instead.
Each folder gets a short name, such as @shared, made
of lowercase letters, numbers and hyphens. Change it, and add a line
on what the folder is, in the boxes under its path.
The folder you started in can be renamed and described, but not
removed. Remove takes any other one out, and
Plan2Code is told.
Using @names
Type @ in the Ask box, a note or a typed answer and a
list of your folder names appears. Pick one, and Plan2Code knows
exactly which folder you mean, for example "use the button styles from
@shared".
What Plan2Code does with them
It reads the added folders for reference, and changes them only if you
ask it to. Before it first uses one, it reads that folder's own notes
for agents, so it follows that folder's rules as well.
Marks you may see
This folder no longer exists: it was moved, renamed
or deleted since you added it. Remove it, or put it back and the mark
goes away.
The agent can't read this yet: Plan2Code tried and
was refused. Most agents ask your permission the first time; allow it
in the terminal. In Claude Code, the mark carries a command such as
/add-dir followed by the path: copy it and run it in the
terminal.
Inside another folder in the list: fine to keep. It
only means one folder already contains the other.
Reading Planny
Planny, the little box with a star for an eye at the top left, shows at a glance whose turn
it is, and the line beside him says it in words.
Planny's six moods, left to right: your turn, working, all caught up, done, not running, not connected.
Your turn
Leaning in and waving, his star lit in your highlight color. Something on this page is
waiting for you: a question to answer, or answers ready to send.
Working
Star turning, arms pumping, feet walking on the spot. Plan2Code has your answers and is thinking, or is
busy building. The line beside him says what it is doing. After about
30 seconds of silence it asks "Still working, or waiting on an approval
in your terminal?", because the terminal may have stopped to ask your
permission for something, and this page cannot see that.
All caught up
A green star. Nothing is waiting on either side: every question is
answered and Plan2Code has nothing new yet.
Done
A green star and both arms up. The session is finished. You can close the tab.
Not running
Gray, still, arms down out of sight. This page is fine, but Plan2Code has not checked in
for 3 minutes. Anything you answer
is still saved.
Not connected
Faded, arms hanging, his star shut in red. This page cannot reach its program, after
8 seconds without contact. Your
answers are saved.
For what to do about the last two, see "When something looks stuck".
Answering questions
Each question is a card, and every card works the same way: answer it,
add a note if you like, and send when you are ready.
The kinds of card
Pick one. Choose a single option. The trade-off for each is written under it.
Pick any. Tick as many as apply. Some cards have quick-pick buttons that tick a set in one go.
Type an answer. A box for your own words.
Yes or no. One of two buttons, sometimes with what each would lead to spelled out.
Is this right? Plan2Code plays back what it understood. Agree, or say what is off.
Read, then approve. Open the document it points to, then approve it or ask for changes.
Steps only you can do. A checklist of things to do outside this page, ticked off as you go.
Put in order or edit a list. Drag the rows, or use Move up and Move down, and edit any row.
What to do next. A short menu of where to go from here.
Something to read. A notice. Nothing to answer.
Help with an answer
Autofill suggestion puts the example into the box as
a real answer for you to edit. It disappears as soon as you have typed
anything of your own.
Starter templates sit above the first "What's the
idea?" box in Pathfinder, Plan and Quick Task. Blank
comes first, then outlines to fill in, in the order your role puts
them. Picking one fills the box with text you can edit; if you have
already typed something, it asks before replacing it. Only what is in
the box is sent.
Something else, in your own words sits among the
options on a pick-one card when none of them fits. It is an
alternative, not an extra: whichever you touched last is your answer.
Anything else, in your own words sits under a
pick-any card. What you write there joins your ticks rather than
replacing them.
Skip this one appears on questions that are optional,
and moves you on to the next question by itself; Do not
skip brings the question back.
After you answer
A settled card reads as an answer: what you chose,
stated in words, with everything else locked.
A card you have sent is held until Plan2Code replies,
showing what you sent. It unlocks by itself when it answers. The rest of
the page keeps working, so you can read ahead or answer the next
question meanwhile.
If a card has been held for a long time, Take this back and
answer again puts your answer back in the box so you can change
it and send again.
Sending and what happens next
Nothing leaves this page until you press
Send to Plan2Code, so you can answer, change your
mind and answer again without committing to anything.
Nothing leaves this page until you press Send.
Before you send
Everything you pick or type is a draft that Plan2Code cannot see
yet, and every bit of it can be undone.
Drafts survive a closed tab and a reload: open the same link again and
your half-typed answers are still there.
Drafts survive a closed window and a reload: when the app shows this
session again, your half-typed answers are still there.
The footer says what is ready to go, and the Send button pulses gently
while there is something to send.
Clear throws away everything you have not sent yet. It
asks first.
Sending
Press Send to Plan2Code, or
Ctrl+Enter (⌘+Enter on a
Mac).
What happens next
Your answers are written to disk straight away, and held there until
Plan2Code collects them, so nothing can write over them.
A second send waits until the first has been collected. Send stays
off until then.
Planny switches to Working while Plan2Code reads them.
The next questions appear on their own, with a chime if sounds are on.
There is nothing to reload.
Notes and attachments
A note lets you say more about any question, and an attachment lets you
show instead of describe.
Notes
The Notes on this panel on the right belongs to the
question you are on. Type in Add a note, attach a file, or ask
something and it goes with your next send. A note qualifies
your answer without replacing it: "B, but keep the header row" is an
answer and a note together. Plan2Code's replies appear in the same
panel.
On a question with options to pick, Ask for suggestions
asks Plan2Code what it would pick and why, on its own: anything you
already ticked stays as it is, and anything typed in the note box goes
along with it. The answer appears in the same panel, and sometimes the
question comes back reworded.
Attaching a file
Three ways, whichever is handiest:
the + Attach file button by the box,
paste a screenshot or a copied file into the box, or
drag and drop files onto the notes panel.
Each file uploads straight away while you keep typing, and sits in a
tray with a remove button. A failed upload offers to retry or remove,
and holds back only that note, so the rest of your answers still send.
What you can attach
Up to 5 attachments per note,
images and documents counted together.
Images are shrunk in your browser to a JPEG at most
2000 px on the long edge, and must
be under 4 MB after shrinking.
Documents up to
10 MB each, uploaded exactly as they
are: plain text, Markdown, JSON, YAML, TOML, INI, CSV, TSV, logs, XML,
HTML, CSS and SCSS, code (JavaScript, TypeScript, Python, Java, C#, Go,
Rust, Ruby, PHP, shell, PowerShell, SQL) and PDF.
Anything else is refused with a message naming the file: Word files
such as .docx, files that are too large, and dotfiles such
as .env, which is where secrets tend to live.
Where the files go
With the session, in
~/.plan2code/console/sessions/<id>/uploads/, never in
your project. They are removed along with the session after
30 days untouched.
The exception is a note attachment Plan2Code cites in a spec file.
Before it writes that file, it copies the attachment into
specs/<idea>/attachments/, so the link still works
after the session is gone. Files attached on the Ask tab always stay
in the session.
Documents and printing
What Plan2Code writes appears here as it takes shape, one tab per
document, so you can read along without opening a file.
Reading a document
Each document has its own tab beside Questions, with
its version number next to the title. It is built from sections, and
each section tells you how firm it is:
Settled sections are plain: decided, and they will not move.
Assumed for now, still open sections have a dashed
edge. Plan2Code had to pick something to keep going, and it is still
yours to change.
Draft sections are dimmed: placeholders, still to be worked out.
Out of date by the title means answers have landed that
the document does not reflect yet.
The Overview, Map and Plan draft tabs
When the session is working on a spec that has an
overview.md, the Overview tab shows it. It
is read-only, and read fresh from disk each time you open the tab, so an
edit shows up straight away. No file, no tab.
On the dashboard, a picked spec that is not documented yet shows its
main files the same way instead: Map for its
Pathfinder map and Plan draft for its plan draft, each
when it exists.
Printing and saving
Back to Questions (Dashboard or Git on those
screens) takes you back to the main flow. The row with it stays at
the top of the tab while you scroll.
Print prints the document alone, without the rest of
the page. Choose "Save as PDF" in the print dialog for a PDF.
Download saves it as a Markdown file. When the
document is already a file on disk, the page shows
Saved as and its path instead.
Briefs (Pathfinder)
Write a brief, in the top bar, asks how far back to go:
Today, This week, Since a
date or Everything so far. Press
Write the brief and Plan2Code writes a plain-English
report of what has been decided, what is still open and what happens
next. It opens in its own tab, ready to print or hand to someone who has
not been in the room. Save as HTML, beside
Print, downloads it as a single web page that opens in
any browser, formatting and images included.
The dashboard
The front door: run /plan2code and every step Plan2Code
can take is laid out as a card. Pick one and it starts right here, on
this page.
Implement runs once per phase, so it repeats until every phase is done.
Asking for your role
Until you pick a role, a one-line banner at the top asks for it, so the
starter templates can be ordered for you.
Set up preferences opens User Preferences;
Not now puts the banner away. Either way it does not
come back, and you can change your role any time from the swatch
button.
When an update is out
When a newer Plan2Code release is out, the dashboard shows
UPDATE AVAILABLE at the top. Click it for the command
to run in your terminal, plan2code update; × hides it until the next
/plan2code. The version at the bottom of Help links to
the Releases page.
The cards
They come in three groups.
Picking a spec
Once your project has specs, Pick up a spec, or start
fresh, at the top, lists every spec folder with where it
stands, plus
Start from scratch for a new idea. The one you pick is
what a step works on, and it decides which cards make sense: a spec
that is half built has no use for Pathfinder, and a new idea cannot be
implemented yet. Cards that do not fit are grayed out with the reason
why.
Hide unavailable workflows, under the picker, hides
them instead. It is on to begin with, and remembered on this machine.
The ✕ on a spec deletes its folder, after two steps:
one says what goes, the other wants the spec's name typed. A fixed
bug has its own Delete button at the bottom of its
chip instead, and needs just one confirm, since the work is done.
A Handoff is a note a step left when you stopped it
with a handoff. It shows as a dashed chip after the specs. Pick one
and the cards give way to a preview with its Next task and four
buttons: Pick it up here carries on in the same step
and spec, Read it all shows the whole note,
Copy for a new conversation puts a ready prompt on
the clipboard, and Delete removes it. A picked-up
handoff drops off the list, but stays in
~/.plan2code/handoffs/ until the 30-day sweep.
The Suggested flag
One card may carry a Suggested flag: where Plan2Code
would start, given what it found in your project. No AGENTS.md yet
suggests setting up; a spec part way through suggests its next step,
with a line on the card saying where it stands.
Starting a step
Click a card and it asks you to confirm: what the step does, which spec
it is for, and a Start button named after the step,
such as Start Plan (Back,
or Esc, returns to the cards). Press Start and Planny flies
while it gets ready. A few seconds later this same page is that step,
already running. No command to type, no second window.
Coming back
When a step finishes, its last screen has a Back to the
dashboard button that turns the page back into the cards, so
the next step can start straight away. See "Stopping and finishing".
Learning
Plan2Code can learn your codebase as your team works in it. A step
offers what it learned at the end of a run; you choose what to keep,
and the next run, yours or a teammate's, starts out knowing it.
What a lesson is
A lesson is one sentence about the code, with why it holds, a kind
(a correction, a convention, how something works, or a command) and
the files it is about. Lessons are about the code, never about you.
A game's saved number goes through the flat keys in looks.json, never browser storage.
Why: you corrected this while fixing Bounce Road's best score.
About: src/web-console/public/activities/
The four states
The dashboard's Learning row says which one the project is in:
Not set up: nobody has chosen yet. Runs read
nothing, and the first time a run learns something it asks whether
to switch Learning on, showing that lesson.
Off: the team said no for this project. Runs
work as they did before Learning.
On: runs read the lessons that fit the files they
work on, and the steps that build, review, test, diagnose or explain code offer
what they learned at the end.
Paused for you: Learning stays on for the team,
but your own runs neither read nor offer lessons until you switch
Pause for me back. Nobody else is affected.
On and Off are the team's choice and travel with the repository;
the pause is yours alone. More on the row switches
Learning off, moves the failure log in AGENTS.md into
lessons, or removes all lessons. When lessons are waiting, a banner
above the title offers Review.
Choosing what to keep
At the end of a run each item gets its own choice, in words that fit
it. Nothing is picked for you.
The item
Its choices
A new lesson
Keep, Reword, Drop
A saved lesson the step doubts
Keep, Reword, Retire
A fix to AGENTS.md
Apply, Reword, Drop
A failure log line
Move, Reword and move, Leave in the log
A new area of code
Create, Rename, Drop
Nothing is saved without your approval, and nothing is committed for
you: what you keep shows up as changed files, to commit with the rest
of the work. A lesson you have not decided on yet stays waiting for
30 days.
Where lessons are kept
Where
What it holds
The project's lessons (.plan2code/lessons/, saved with the repository)
The lessons your team kept, one file per area of code plus a general one, and the Learning switch beside them. Commit it; it is how your teammates get them.
On this machine only (~/.plan2code/)
Lessons waiting for your review and your own pause. Never shared.
Session meter
The small ring in the top bar counts how much work this console session
has done, and tells you when a fresh one would serve you better.
The three colors
Green, "Session: fresh". Under
5 points. Carry on.
Yellow, "Session: getting long". From
5 points. Fine for now; think
about a fresh start after this step.
Red, "Session: time for a fresh start". From
10 points. The dashboard also says so
in a banner.
What it counts
Each step you run here adds points: a plan or a set of documents
weighs more than a quick task, and a built phase more still, by how
many tasks it completed: a big phase adds more than a small one.
Every two questions you answer within one step add a point too
(rounded down, so a single answer adds nothing), so a long
back-and-forth counts for more than a short one. Click the ring to see the count and a list of each step that added
points, with what it added. It is a rule of thumb, not a
reading of Plan2Code's real memory: long sessions tend to make it
miss things, and the ring is there to remind you.
What red means
Starting a new console session will keep Plan2Code
sharp: stop this one, then start Plan2Code again in a new
conversation. Resuming this session carries its count along, so it
does not help. Your work is all on disk, so nothing is lost.
A fresh start will keep Plan2Code sharp: finish the step, then press
New Session at the top of the window. The agent starts
again on a clean context, in a new console session whose meter starts
over, and the dashboard offers a brief of where you were. Your work is
all on disk, so nothing is lost.
The meter never blocks anything. Red is advice; you can keep going.
Watching a build
Implement, Implement + review and Quick task spend most of their time
building rather than asking, so the page shows you the build as it
happens.
What it is doing now
The line beside Planny says what Plan2Code is working on, for
example "Task 5 of 9: the rate limiter". Tasks are counted within the
phase, and the progress bar counts the same way: "5 of 9 done".
The phase file
The phase file, such as phase-3.md, has its own tab:
what has to be true before the phase starts, and every task in
full, each one ticking as soon as it is finished and saved.
Questions along the way
Anything the build needs from you, such as which phase to do next, a
clash in the spec or tests that are failing, arrives as an ordinary
card. Answer it like any other.
Signing off
When the phase is built, a Completion report tab says
what was done, which files changed and how to check it, and an
Approve this phase card asks for your approval.
Nothing is marked complete until you give it.
Reviewing before you approve
Review the code first, on the approval card, runs a
careful review of exactly the files the phase changed. The findings
come back in their own tab, and a Which to fix card
lists each one with how serious it is. Tick the ones to fix, or use
Critical and warnings or All of
them, and send. Plan2Code fixes and re-checks them, then
the approval card comes back.
A quick task has no approval card, so its last screen offers
Review it now instead, with No thanks, I am
done beside it.
Implement + review offers neither: it reviews every phase before
asking for your approval anyway.
Long tasks
Some tasks take a while without anything to show. The build tells the
page how long it may go quiet, and Planny only says it has stopped
checking in once that time has passed.
Implementation Loop
In the desktop app, the Implementation Loop builds every remaining
phase of a documented spec for you, one after another, while you do
something else. The dashboard's Implementation Loop card starts it.
Review, fixes and re-check are on only when you choose them in the setup.
What it does
It runs on its own, one fresh agent session per phase,
and, when you leave commits on, commits each phase locally to the
branch you are on. It never pushes.
Review fixes are chosen with Smart pick by a fresh agent
that skips what is not worth fixing and records each skip, or
by level (Critical, Warning, Suggestion).
It uses the launch agent and model the app is running, and it needs
permission checks off: with them on, an agent would
wait on a prompt nobody sees, so Start stays grayed out.
Strength per phase
Turn on Set strength per phase in the setup to run each
phase on Thrifty, Balanced, Best
or Match my session. A phase you leave untouched runs on
the launch model. The one retry after a crash or a quiet agent (when retry
is on) goes one step up (Match my session stays on the launch model),
and the phase's helpers follow.
Click a dot in a phase's row to pick (the arrow keys move along a row);
a line steps through each row's pick so the choices read at a glance.
What is locked while it runs
Answers, sign-offs, launches, Workspace, Helpers and
Back are read-only, starting a new session is held
back, and Ask is off, except for a question the loop is waiting on. Still
open: Activities, Notebook, Help, Preferences, the docs and the code
review.
Stopping it
Stop after this phase, on the banner at the top of the window, lets the
phase finish its review, mark and commit, then ends the loop.
Stop now ends the agent at once, after you confirm.
Quitting the app ends the loop too.
When a phase asks a question
By default the agent takes its best guess and records the
assumption. If you chose to pause instead, the loop holds, with
no time limit, and nothing is lost. The app calls you back
with the taskbar dot, a flash of the window and the question sound. Answer,
and it carries on.
Being told when it needs you
Fill in Send a notification in the setup and the app sends a message
when the loop waits on your answer or ends, unless you stopped it yourself. Send it to a
Discord, Slack, Microsoft Teams or Google Chat webhook, or to any http or
https address, with the message in its query string or a JSON body.
Send a test tries it right away. One that fails during a loop does not
change what the loop does; the finish line or the stop screen says so.
When it stops by itself
Failing tests or a failing quick check, Critical or Warning findings
left over at a level you chose to fix, a blocked task, a conflict in the spec, a commit that was
refused, or a Critical finding the Smart pick skipped.
A crashed or silent agent gets one retry per phase, if you left that on. After that
the loop stops.
A stop screen leads with why it stopped, and the evidence is one
button away. Every button has a line saying what it does, and the
one that fits the stop is highlighted.
Continue building carries on unattended from that
phase (recommended when the agent crashed, went quiet or you
stopped it); Fix together with an agent opens an
ordinary Implement session on it (recommended when a check failed,
a task is blocked or the commit was refused).
Ask a question wakes an agent that only answers,
in the Ask tab. Nothing is lost on a stop: your work stays on disk.
The report
One report follows the whole build, across stops and Continue building: what each
phase built and committed, the findings it fixed, the findings it chose
not to fix and why, the findings left open, each assumption, any other
decisions the agent reported, and every retry and stop. The agent writes
most of it, so it holds what the agent noticed. The finish screen counts
each kind, and Read the full report opens it, saved as
specs/<feature>/LOOP-SUMMARY-<date>.md. After a
stop, the stop screen shows the report so far.
The git board
The Git card opens a board for your repository: three tabs — Changes,
Branches and Sync — and the next step on top. Every button is a request
to Plan2Code, which runs the git commands and says what each one did.
The header
The branch you are on, and how far it is ahead of (↑) or behind (↓)
its remote copy, or that it is not published yet.
With more than one remote, a badge names the one your branch follows.
With no remote at all, a No remote line shows the
command that adds one, with a copy button.
Last refreshed says when the remotes were last
fetched. If a refresh fails, the line says so.
The tabs
Changes lists your uncommitted files, ready to
commit. Its badge counts them, or shows a dot when the only files
left are held back (secrets and very large files).
Branches lists your branches with Switch and Delete,
plus new branch and clean-up. Its badge counts branches already
merged, or whose remote copy is gone, that can be cleaned up.
Branches that exist only on the remote sit under Remote
only, showing the first
50; Search
branches filters both lists.
Sync holds pull, push and publish. Its badge shows
↑ and ↓ counts, ↑ alone when the branch is unpublished, or ? when the
remotes have not been checked lately. During a rebase or merge it
shows ! instead. Once your branch is pushed, Sync
also offers Open pull request, into the default
branch or the one you pick beside it; the first time a host is
unknown, it asks which kind it is and remembers the answer.
A filled badge marks the tab where the next step is.
The next step
The tab that holds it opens with one main button and, at most, one
quieter one beside it: Commit, Push, Publish, Open pull request, and
so on.
On the other tabs, a line reads Next step is on
‹tab›; click it to go there.
Held-back files never count toward the next step. The board offers
to add them to .gitignore instead.
When the remotes were last checked over an hour ago, it says
Checked … — Refresh?.
With nothing to do it says All caught up, or
Nothing to commit … no remote yet when there is no
remote.
Push, Publish, Delete and Clean up always show exactly what will
happen and wait for your yes. Nothing is ever force-pushed, and a
remote branch is never deleted.
Moving between tabs
Once a click of yours has landed, the board moves to the tab of the
next step. Anything else that changes leaves you where you are.
Reloading the page keeps the tab you were on.
The arrow keys move between tabs, and Home and End jump to the first and last.
While something is running
Everything grays out except switching tabs, searching and opening
folds, so nothing queues up behind the running command.
What is running shows where the next step usually sits.
Plan2Code's questions appear under the tab strip.
When it is done, a result line says what happened, with the commit
hashes, and the board redraws from the repository as it now stands.
Mid-rebase or merge
A rebase or merge that stopped on conflicts shows one block on Sync,
with the files still to fix. Continue becomes the main
button once no conflict markers are left; a single Abort
puts everything back as it was. The other tabs wait until it is
finished or aborted.
Done with git
Done with git ends the board. If anything happened, the
last screen lists the commits, pushes and branches created or deleted,
with Back to the dashboard; if nothing did, the page
goes straight back to the dashboard. It grays while a command runs and
comes back when it is done; if Plan2Code stops checking in,
Stop session in the top bar ends the session instead.
While a question of Plan2Code's waits, it cancels that question and
finishes.
Update dependencies
The Update dependencies card clears a dependency
backlog in one sitting. It scans every manifest in the project (npm,
pnpm and Yarn, Cargo, pip and uv, Go and .NET), labels each update,
applies the ones you pick in batches, runs your install and checks
after each batch, and puts back whatever breaks.
The labels
Safe: in range, notes read, nothing breaking found. All Safe is the suggested pick.
Check first: a bigger jump or notes it could not read. Applied one at a time, with its own checks.
Warning: the notes say something your code uses changed. Tick it to write an upgrade brief instead of applying it.
Held back and Not scanned: shown for the record, never picked.
The pick list
Rows are grouped by label. Open a row to read its notes, the breaking lines and where your code calls the package.
The count under the list says how many check rounds your picks take.
Nothing is updated until you send.
When a batch breaks
A batch whose install or checks fail is put back exactly as it was
found and reinstalled, then narrowed down to the pick that broke it.
That pick is marked failed with its output; the rest go on. Stopping
mid-run keeps the batches that passed.
Upgrade briefs
A ticked Warning writes specs/<package>-upgrade/UPGRADE-<date>.md.
The dashboard shows that folder as Upgrade ready, with
Quick task and Plan lit: Quick task applies it, Plan plans a big one.
Once Quick task has applied it and its checks pass, the folder shows as
Upgrade done, offered for archiving, and deleted after
one confirm like a fixed bug.
What it never does
It never commits, installs a tool, edits your source code or updates
anything you did not pick. The changed manifests and lockfiles wait
for you to commit.
Helpers (subagents)
On most skills (all but the dashboard, Finalize, Changelog, Git and
Handoff), Plan2Code
can hand independent pieces of work to helpers (subagents) while it
keeps the conversation with you. The Subagents button in the top bar, after
Stop session, is lit while helpers are on.
The switch
Clicking the button opens the Subagents dialog; it
never switches helpers on or off by itself. Pick Use
helpers or Work alone, edit the instruction
Plan2Code follows (Reset to default puts the
shipped one back), and say how many may run at once.
It is on until you turn it off, and saved for this project and this skill, so
the next session of the same skill here starts the same way.
The change reaches Plan2Code at its next check-in, as a setting,
not as something you typed. How many helpers it can really start is
up to your agent; some have no helpers at all.
The button only appears on skills that use helpers, and only when Plan2Code can pass the setting on.
Helper strength
Under Helpers, the dialog also asks how strong the helpers should be.
Like the rest of the dialog it is saved for this project and this
skill, and it does nothing under Work alone.
Balanced (the default): each helper gets the
strength its job needs: light for lookups, stronger for reviews and
design work.
Thrifty: one step lighter everywhere to save cost;
reviews stay at standard or above.
Best: the strongest model and high effort for
everything except lookups.
Match my session: helpers run on whatever your
session uses; nothing is set for them.
The Subagents tab
With the first helper, a Subagents tab appears before
Ask: one row each, with what it was asked, whether it is running, done
or failed, and a one-line result at the end. The number on the tab is
how many are still running.
Helpers report through Plan2Code, so the rows change at its
check-ins, not live. The page cannot stop a helper; ask Plan2Code
on the Ask tab if one should stop.
Under each helper, a line such as "Standard, medium effort" shows
what that helper actually ran with. "Session model" means the agent
could not set a strength for it, so it ran on the session's own
model. A helper that reported neither shows no line.
Working alone means your agent reported it has no
way to start helpers here. If it starts one after all, the note
goes away and the helper's row shows instead.
Pathfinder always uses helpers for its research questions, whatever
the switch says, and they show here too.
The tab clears when you go back to the dashboard.
Ask a quick question
The Ask tab, always the last tab, is a chat for
anything you want to know, without waiting for a card to ask it on.
Asking
Ask about this project's files, or about anything at all. Plan2Code
answers at its next check-in (during a build, once it finishes the task
it is on), and the work carries on meanwhile. Asking never holds up
your answers to the cards, and sending those never holds up a question.
Prompts to carry away
When what you ask is really a new task, or you ask for a prompt,
the answer ends with a ready-to-paste prompt in a box with a
Copy button. Copy it into a new conversation: it
names the skill to use and the files to read, so nothing said here
needs repeating.
What it is about
The box starts with no context, so a question is a general one unless
you say otherwise. + Add context, beside
+ Attach file, lists the last three places you
visited (question cards, document sections, and a spec you picked on
the dashboard) and This spec. Pick one and a chip, About: followed
by its name, sits above the box. Press × on it to
remove it. It clears after each send, so pick it again for a
follow-up.
Starter questions
An empty conversation offers a few starter questions for this step,
with the ones most useful to your Role first. Clicking one fills the
box for you to edit; it never sends by itself. They come back with
New conversation.
How much you can ask
Up to 10 questions per
conversation. The counter at the top of the tab ("3 of 10") is
always in view.
Once the last one is answered, New conversation
starts a clean one. So does switching steps through the dashboard.
Up to 4,000 characters per
question. A count appears near the limit.
Up to 5 attachments per
question, added the same ways as on a note: + Attach
file, paste, or drag and drop onto the box.
Typing and sending
Enter starts a new line in the Ask box.
Ctrl+Enter (⌘+Enter on a
Mac), or Send, sends the question. It sends only the
question, never your answers to the cards.
Changes need your approval
Ask for a change to a file and Plan2Code replies with a summary and
the list of files it would touch, with Approve and
Decline buttons. Nothing changes until you approve.
Afterwards it lists what changed, with line counts. Nothing is
committed, and it never touches the running step's own files under
specs/.
A chat message never answers a card or moves the work on. That is what
the cards are for.
When you cannot send
"That's 10 questions in this conversation" means press
New conversation to keep going.
"No agent is available right now" means the session has finished or
Plan2Code has gone quiet. Check the terminal, or resume the session,
to ask.
"No agent is available right now" means the session has finished or
Plan2Code has gone quiet. Check the terminal panel, or press
New Session if the agent has ended, to ask.
Either way, the conversation above stays readable.
When an answer lands
If you are on another tab when a reply arrives, a dot appears on
Ask and a chime plays once (if sounds are on).
Activities
The die in the top bar opens
Activities: small games to play while you wait, say
through a long build. Thirteen games ship: Snake,
Mini golf, Light Trails,
Bug Hunt, Sunset Drive,
Stack Deploy, Bumper Ring,
Rapids Run, Hot Potato,
Crossing Rush, Bounce Road,
Ghoul Rush and Flock Dash. The window opens on a card for each game, with its best score; click one
(or walk them with the arrows and press Space) to play it,
and All games takes you back. One game plays at a
time: a round left for the cards waits, paused, on its card, and
picking a different game ends it. Nothing you do in it reaches
Plan2Code.
The games
Snake: steer to the food and grow. The snake speeds
up as it grows, and a wall, a rock, a comet or your own tail ends
the round. Food eaten quickly builds a combo of up to x5. Every 5
foods is a new level, which starts in Slow-mo, and each of the first few brings something
new: rocks (a flashing cell turns to stone), mystery boxes, portals,
comets that cut your tail, then chaos. Power-ups turn up on their
own: Shield, Turbo, Slow-mo, Magnet, Ghost and Scissors, and a
mystery box can hold any of ten surprises, good or bad. The start
and end screens count how many of them you have found so far.
Mini golf: six themed courses of eighteen silly
holes, seen from above. Its card opens a dashboard of the courses,
each with a picture of one of its holes, its par and your best on
it: Pirate Cove (a shark sea, cannonballs, a
kraken and a ghost ship), the Caves of Doom (lit
only around your ball, with lava, a bottomless pit, mine carts and
stone crushers), Dino Valley, Candy
Carnival, Cosmic Glow (where black holes
bend your putt) and Frosty Peaks (where the ball
glides on ice). Pick one to play its eighteen holes, and
All courses takes you back. The aim starts on the cup and follows your mouse once you
move it, and a click putts where the arrow points. Click (or press
Space) to start the power meter, then click again to
set the power: the gold MAX band near the top
gives a boosted putt, but go past it into the red and you shank it.
Dawdle for 6 seconds and the meter starts by itself. Hold the mouse
button or Space while the ball rolls to speed it up.
Each hole has a par, and after 8
strokes the ball is picked up. The scorecard between holes shows how
the round stands against par.
Power-ups: roll over a glowing pad to hold it for
your next putt. A Lucky Doubloon makes it free, a
Cannonball fires it 1.6 times as hard, a
Ghost Ball floats over water, sand and bumpers, a
Parrot Magnet bends it toward the cup, a
Rubber Duck bounces off walls at full speed, a
Treasure Map makes the cup huge, and a
Spyglass shows where it will roll while the meter runs.
You hold one at a time, and it carries over to the next hole.
Light Trails: you and your rivals each leave a
glowing wall behind, and the last rider still moving wins the heat.
A wall, any trail (yours too), a crystal or another rider is out,
though you hold in place for a split second first, so a quick
turn still gets you clear.
Win a heat to move on through nine arenas; a crash costs one of
five lives and runs the heat again, and every 750 points or a
Heart pad gives one back. The arenas bring more rivals, crystals,
portals, walls that close in a ring at a time (flashing red
first) and ever more power-up pads: Boost, Phase through trails,
an Eraser, Slow-mo for the rivals, coins, a Heart and a Shield that
takes a crash, then a Laser that zaps rivals in your line, Score
x2, a Wide Trail three cells across, Coin Rain, a Hyperjump to open
space and a Mystery pad that could be any of them. A rival out
scores, and more if your trail or your laser got it.
Bug Hunt: fly Planny's ship along the bottom and
squash waves of bugs before they dive at you. New bugs join as you
go: Beetles that split in two, zigzagging Race conditions,
Exceptions that throw things, Null pointers your shots pass
through while they fade, and Firewalls that take five shots. Every
fifth wave is a boss: the Memory Leak, the Spaghetti Monster (shoot
its tentacles off first) and the Heisenbug. Squashed bugs drop
coins and power-ups (Spread shot, Rapid fire, Shield, Slow-mo,
Magnet, Refactor and a 1UP), and quick kills build a combo.
Sunset Drive: race Planny's convertible down an
endless road against the clock. Each stage ends at a checkpoint
that adds time, and just before it the road splits: the side you
keep to picks the next road, and the harder one scores more.
Six roads to find: Sunset Coast, Canyon Road, Maple Valley,
Snowcap Pass, Neon City and Starlight Highway. Traffic, roadside
props and the median slow you down; coins, clocks (+5 seconds)
and nitro cans line the road, and passing a car close at speed
scores a close call. The round ends when the time runs out.
Stack Deploy: one button. A block slides back and
forth above the tower; drop it, and whatever hangs over the edge
is sliced off, so the next block is narrower. Miss the tower and
the round is over. Land one dead on for a
Perfect: nothing is sliced, a run of them scores
more (up to x5), and every third in a row grows the block back.
Gold blocks turn up from floor 15, worth more and growing it
twice as much. The floors speed up from 10 and bring twists:
blocks from either side that may turn back at 20, lag spikes that
freeze a block for a beat at 30, wind at 40, a rush through the
middle at 70 and everything faster at 90. The tower goes
from server racks to office floors, glass towers and rockets, and
a dashed line marks the highest floor you have ever reached.
Bumper Ring: sumo in bumper cars, on a ring over
the void. Push into your rivals and the harder hit wins; a car
whose middle goes past the edge falls, and the last car on the
ring wins the heat. A rival lets go and revs before it dashes:
that is your moment to step aside, and a rival that misses near
the edge may fly off on its own. Win a heat to move on through
nine arenas, from the Training Mat to the
Grand Final, then Finals that keep getting
sharper; a fall costs one of three lives and runs the heat again.
After a while the ring shrinks a band at a time (the band flashes
red first), and a heat that drags on past the smallest ring goes
to sudden death, shrinking on until two cars no longer fit. The arenas bring rivals (the Bully, the heavy Turtle,
the Sniper, the Scrapper and the Mirror, who copies your moves),
power pads (Heavy, Spring, Charge, Shield, Grow, Ghost and
Slick), bumpers, ice, a turntable, holes, a magnet and a ring
that turns square. A knockout scores for the last car to touch
the one that fell, and quick knockouts build a combo of up to x5.
Rapids Run: pilot Planny's jet-skimmer up a
winding river that scrolls down the board, its banks narrowing and
splitting around islands. Hold Space to fire. The
battery drains all the while, a little faster at full speed: run
over a green charge buoy to top it up, or shoot it for a few
points if you can spare it. A bank, an island, a foe, a bolt or a
flat battery costs one of three lives, and you start the stretch
again from the last dam (or, once you have reached a mini-boss,
from the mouth of its basin); a dam you blasted stays open. Each
stretch ends at a dam across the river: shoot it open to pass
(slow down to give yourself time).
Eight named stretches, from Willow Run to
Old Lock, then Night Water again and again,
quicker. Patrol skiffs drift from bank to bank and bob mines sit
still from the start; gull drones swoop across from stretch 2,
bank sentries shoot back from stretch 3, whirlpools tug you from
stretch 5 and darters swerve into your lane from stretch 6. Every
fourth dam a mini-boss holds the basin before it (the river stops
and your battery holds while you fight): the Dredger, Ironclad and
Old Leviathan. Crates hold Spread shot, a Shield (one crash of any
kind but a flat battery), a Magnet for charge buoys and a Surge
(a full battery). Points: 1 for every 5 units of river, 2 at full
speed; 5 for every quarter second you skim a bank at speed (10 at
full speed); 20 to 60 for each foe, times your combo (sinks within
1.6 seconds of each other, up to x5); 10 for a buoy shot; 100
times the dam's number for each dam, 50 times it more for a
stretch with no life lost; and 400 for each of the first three
mini-bosses (800 each the next time around, and so on), each of
which also gives a life back.
Hot Potato: one fizzing bomb (a merge conflict,
its <<<<<<< markers showing) and a
fuse that keeps getting shorter. Whoever holds it passes it on by
touching someone, and whoever holds it when the fuse runs out is
blown out of the match. Someone just handed the bomb cannot pass
it on for a moment (it flashes white), and while three or more are
left nobody can hand it straight back to the one who just passed
it (a white ring at their feet shows who is safe). Handed the bomb
at its last moment, you still get time to pass it: a pass tops the
fuse up to 1.4 seconds, once a fuse for each runner. The holder runs a little faster, so a chase can end, and a
rival crouches before it lunges: that is your moment to dodge. The
last one standing wins the match and moves on through nine venues,
from the Break Room to the
Finale, then Finales that keep getting sharper;
being blown up costs one of three lives and runs the match again.
The venues bring rivals (the Sprinter, the Hider, the Trickster,
who feints before it dashes, the Pal and the Clingy), pickups
(Freeze, which stops every fuse for 2 seconds, Sneakers, Extra
Fuse, which adds 2 seconds to every fuse, and Swap, which trades
places with a random runner), long rows of server racks, a roof
with no wall at the bottom (off it is out), ice, conveyor belts, a
blackout and two bombs at once. Points: 10 times the venue for
every fuse that ends on someone else, 2 for each pass you make, 15
more for a hot pass (under a second left) times your streak of hot
passes in a row (up to x5; a pass that is not hot ends it, and so
does a life lost), and 50 times the venue for a match won.
Crossing Rush: hop Planny up a strip of lanes,
racing two rival hoppers to the top: roads of cars and trucks,
rivers where you ride the logs and turtles (the water, or riding
off the edge, sends you back), train tracks that flash red and
ring before a train, and grass with bushes and rocks in the way. A
car, a train or the water sends you back down to the last grass
row, never out. Space shoves the hopper in front of you a cell, so
a well-timed shove puts a rival in the traffic (they will do the
same to you). First to the top wins the heat and moves on through
nine zones, from Side Street to
Rush Hour, then Rush Hours that keep getting
quicker; second or third costs one of three lives and runs the
heat again, though in the first two zones second place still gets
you through. The zones bring logs, trains, diving turtles, trucks
and lanes that speed up, a night lit only by headlights, rivers
that turn round and icy lanes that slide you a cell on, and rivals
(the Hopper, who waits for a clear gap, the Daredevil, who takes
the tight ones, the Bruiser, who shoves, and the Tagalong, who
follows you up and shoves near the top). Pickups sit on the
grass: Spring (your next hop goes two cells), Shield (the next hit
does not send you back), Coin and Horn (the nearest road stops for
a moment). Points: 1 for each row higher than you had got in the
heat, 50 times the zone for a heat won, times your streak of clean
wins (a win where you were never sent back adds one to it, up to
x3; any other win, a second place or a lost heat ends it), plus 3
for each row the runner-up still had to go, 15 for a rival you
shoved that is sent back, 5 for a close call (a car or a train
through the cell you just left within a tenth of a second), and 10
for a coin.
Bounce Road: race Planny's springy toy car up a
road laid across a giant's house and yard, with rival toy cars on
it that mean to stop you. Bump one sideways off the road, and press
Space to jump (you need a little speed, and a faster jump
goes further). Land on a rival to flatten it and bounce up again,
and land on another before your wheels touch the road to build the
bounce chain, up to x8. Every stunt in quick succession (a crush, a
rival bumped off, a hole, train, ball or barrier jumped, a ramp's
big air, a close shave, a boost strip) steps the combo: every
third in a row multiplies your points once more, up to x4, until
you go 2.6 seconds without one. In the air, a ring in your
highlight shows where you will come down, and a red one where a
rival will. Water or a hole under your wheels, a crash (a
flowerbed or a toy block nose first, a train, a truck's back), or
anything landing on you costs one of three lives. Ten stages, each
bringing something new:
Chalk Lane (cracks, boost strips and cones),
Hose Creek (broken bridges, a sprinkler, the Frog,
who hops), Kitchen Floor (oil slicks, a rolling
orange, the Sneak, who drops cones), Flowerbed Fork
(the road splits, ramps, falling flowerpots, the Nudge, who swipes
at you), Sandbox Run (road that crumbles behind
you, the Hauler too heavy to bump, the Bruiser, who shoves),
Toy Room (a toy train crossing, toy-block
chicanes, the Racer to catch), Garden Pond
(swaying bridges, drawbridges, the Cop, who chases you and pushes
you toward the edge), Rooftop Gutter (gusts of
wind), Night Lights (everything, in the dark) and
Monster Mash, where the Monster truck hops at
you: land on its roof five times to beat it. Then the road goes
round again from Kitchen Floor, quicker and meaner. Every hole has
a warning sign and a straight run-up, and can be cleared at 80% of
the top speed. Power-ups lie on the road from Hose Creek: Spring
(your next jump goes further), Bubble (one free save), Nitro (a
burst of speed) and Mega wheels (bigger and heavier: flatten
whatever you touch). Points: 1 for every 10 units of new road (a car
is 7 long); each rival's own points when you land on it (100 to
300, the Racer most), times the chain; 60 for a rival that leaves
the road within a second and a half of your bump; 25 a hole and 40
a train, ball or barrier jumped; 60 for a ramp's big air; 30 for a
close shave; 10 a star and a boost strip, all times the combo;
250 a stomp on the Monster and 2,000 for beating it, with a life
back. At each stage line: 100 times the stage, 15 for every second
under the stage's par, and, with no life lost, 250 more and a life
back, up to five.
Ghoul Rush: blast Planny through a haunted
mansion, a room at a time, seen side on with the view scrolling
along with him. His flashlight blaster fires the way he faces, and
a bolt tilts a little toward a monster ahead near his height. It
heats up as it fires: after about three seconds of shooting it
slows, down to one bolt a second, a HEAT pill shows
how hot it is, and letting go of fire cools it. Rapid fire never
heats it. Grab
each room's key, then reach its door; a boss guards every fourth
room, and beating it opens the door. Zombies
shamble out of doors in the wall and lurch when you are close (two
bolts), crawlers come up through loose boards,
bats swoop down to your height in passes,
ghosts drift through walls and can only be hit,
and only hurt, while they are solid, and
skeletons throw bones you can shoot down. A bolt
to the head or a stomp from above doubles a kill, and kills in
quick succession build a chain that multiplies them, up to x8, but
it runs out in a second and a half. The rooms bring pits, shelves to jump up
through (down drops through one), boards that crumble and
chandeliers that come down on whatever is under them. Eight rooms,
the Foyer, Portrait Gallery,
Library, Ballroom (the
Great Gourd, which hops to where you stood:
watch its shadow), Kitchen,
Conservatory, Attic and
Crypt (Old Rattlebones, whose
shockwaves you jump), then round again, quicker and tougher.
Power-ups: Spread shot, Rapid fire, a Garlic shield (shrugs off one
hit) and a 1UP. A hit or a fall costs one of seven lives and puts
you back at the room's start (in a boss fight, the arena's), safe
for a moment. Points: 100 a zombie, 75 a crawler, 50 a bat, 150 a
ghost, 200 a skeleton, 40 a gourdling, all times the chain, 25 a bone shot down, 10
a candy, 50 a power-up; through a door, 300 times the room number
plus the time bonus left (1500, dropping 30 a second; once it runs
out, zombies shamble in from the edges) and 500 more with no life
lost; and 2000 for the Gourd and 2500 for Rattlebones, times the
lap, with a life back.
Flock Dash: lead Planny's flock through a sunset
sky. Strays drift in from the right; fly into one and it joins the
flock, following the exact path you flew. Balloons, gusts,
slipstreams, storm clouds and kites are in the way: a hit on the
leader costs one of three lives, and a hit on the line snaps it
there, scattering the birds behind (pick them back up within 3
seconds or they are gone). Eight stages, each ending at a jet
stream portal that forms a V for a bonus when enough birds reach
it; the final portal moves. Tailwind, shield and magnet crates help,
and quick pickups build a combo of up to x5.
It never hides your turn
A new question, a sign-off or a finish pauses the game at once, and
a banner above the board says Plan2Code needs you.
Go to it closes the window on that question.
Switching to another tab, or clicking outside the page, also pauses it.
Hiding the window, or clicking outside the page (the app's own bar
too), also pauses it.
Nothing resumes by itself. Any game key plays on, and so does a
click on the Mini golf or Stack Deploy board. Playing on puts the banner away until
the next new question.
Starting a round, and playing on after a pause, counts down 3, 2, 1
first, so the game never moves before you are ready.
Keys
Snake: the arrow keys, or WASD, steer.
Mini golf: hold left or right to turn the aim (faster the longer
you hold), press Space once to start the power meter and
again to set the power, and hold Space while the ball
rolls to speed it up.
Light Trails: the arrow keys, or WASD, steer, and Space spends a
boost charge for a burst of speed (two a heat, up to three).
Bug Hunt: the arrow keys, or WASD, fly the ship, and hold Space to fire.
Sunset Drive: hold up (or W) to drive and down (or
S) to brake, left and right steer, and Space
burns a nitro can for a burst of speed (two to start, up to three).
Stack Deploy: Space, up (or W) or a click
on the board drops the block.
Bumper Ring: hold the arrow keys, or WASD, to push your car that way (two at once
push on the diagonal), and Space dashes (two charges a
heat, one back every few seconds, up to three).
Rapids Run: left and right (or A and D)
steer, hold up (or W) to speed up and down (or
S) to slow down, and hold Space to fire.
Hot Potato: hold the arrow keys, or WASD, to run that way (two at once run on the
diagonal), and Space dashes: a lunge for a tag while you
hold the bomb, a dodge while you do not (two charges, one back
every 4 seconds).
Crossing Rush: the arrow keys, or WASD, hop one cell, one hop a press (a press
during a hop waits its turn), and Space shoves the
hopper in front of you a cell the way you face (once every 3
seconds).
Bounce Road: hold up (or W) to drive and down (or
S) to brake, left and right steer (only a little in the
air), and Space jumps, once a press. A ramp launches you
on its own.
Ghoul Rush: hold left and right (or AD) to
run, up (or W) jumps, once a press (let go early for a
short hop), down (or S) drops through a shelf, and hold
Space to fire (in bursts: the blaster slows as it heats
and cools once you let go).
Flock Dash: up and down (or W and S) climb and
dive, left and right (or A and D) ease forward
and back.
Space starts a round, and plays again after a pause.
P pauses and plays.
R starts the round over, from the countdown.
F, or Full screen under the board, gives
the game the whole screen: the board as big as the screen allows,
black bars where its shape leaves room, and a panel over it for the
game's name, your score and best, the game's Music slider, and Exit full screen.
The panel sits in a black bar when one is wide enough; otherwise it
floats in the top corner and, while you play and the pointer is
still, shrinks to your score in the bottom corner. The pointer hides while you are not
moving it. F or Esc
puts it back. A question, a sign-off or a finish puts it back too,
as it pauses the game.
It uses the browser's own full screen where the browser allows one.
Enter does both: it starts a round, pauses it and plays on.
Esc closes the window, with the game paused where it was (in full screen, the first Esc leaves full screen).
Activities need a keyboard: on a touch-only screen the window says so instead of showing the board.
Best scores
The window's title shows the best for the game on screen, and the
line under the board shows it beside your score, and each card shows
its game's. For Snake, Light Trails, Bug Hunt, Sunset Drive, Stack Deploy, Bumper Ring, Rapids Run, Hot Potato, Crossing Rush, Bounce Road, Ghoul Rush and Flock Dash the best is
your highest score; for Mini golf it is your lowest full round of eighteen holes,
kept for each course on its own, and a round left halfway never counts. Reset best
scores, at the bottom of the window, clears them all after a
second click to confirm.
Showing and hiding it
The die is off until you tick Show Activities in User
Preferences (the gear); untick it again and it is gone from every screen. To play
without sound, untick Play activity sounds beside it.
A game with music (turn on Play activity music there) has
its own Music slider under the board for how loud it plays.
Best scores, Snake's surprises found, Light Trails' furthest arena, Bug Hunt's finds, Sunset Drive's roads found, Stack Deploy's highest floor, Bumper Ring's furthest arena, Rapids Run's furthest dam, Hot Potato's furthest venue, Crossing Rush's furthest zone, Bounce Road's furthest stage, Ghoul Rush's furthest room, Flock Dash's furthest stage, each game's music volume, your last pick and that switch are saved privately on
this machine, with your other preferences, and never sent anywhere.
Stopping and finishing
Every session ends with a screen that says what happened and what to
run next, whether it finished on its own or you stopped it.
Stopping early
Stop session, at the top, ends the session and saves
your place. Any answers you have ready go with it, and Plan2Code
gives you a command to pick up where you left off, in a new
conversation.
It only works when it is your turn. While Plan2Code is busy with
what you last sent, the button waits, so a stop never lands half way
through writing your answers down.
It asks first, and offers two ways to stop.
Stop with a handoff saves your place and writes a
note the dashboard can offer to pick up later;
Just stop and save saves what the step keeps on
disk and gives you a command to resume, without the conversation;
Keep going backs out.
A handoff lands in ~/.plan2code/handoffs/ and shows on
the dashboard, next to your specs, until you use or delete it.
At points where nothing is saved yet, such as early in a plan, the
dialog says what would be lost and the button reads Stop
anyway instead.
Back to the dashboard, mid-way
The triangle left of Stop session leaves the step you
are in for the dashboard, in this same session. Your place is saved
the way a stop saves it, with any answers you have ready going along,
and the menu appears here instead of a finish screen. From there,
pick the same step again to carry on, or pick another one. It follows
Stop's rules: it only works on your turn, it asks first, and it
shows the same warning where nothing is saved yet.
The three endings
A next step. What was done, and under
Next step the exact command to run next, with a
Copy button: the next phase, Finalize, or a commit.
All done. "All done, nothing left to run." There is
nothing to copy but the command that opens the dashboard.
Paused. You pressed Stop session.
The screen names what was saved and gives the command that picks it
up later. Nothing else is offered.
Paused means there is more to do and your place is kept. Finished means
this step is over.
Running the next command
Press Copy, then paste the command into the terminal
where you started Plan2Code, in a new conversation. When the next
step is another Plan2Code step, the command already ends with
--web, which asks Plan2Code to open this page again, so
you carry on here rather than in the terminal.
Back to the dashboard
A finished screen (never a paused one) has a Back to the
dashboard button. It turns this page back into the cards, in
the same conversation, so the next step starts right here.
Plan2Code listens for it for as long as the session is open.
Once the session has closed, the button becomes the
/plan2code command to run in a new conversation
instead.
After a long step, a new conversation is the better choice anyway: it
starts with a clean slate.
Update CHANGELOG first
A finished quick task or finalize that ends on a commit can also show
Update CHANGELOG first beside Commit it
now. It opens Changelog right here; when Changelog asks
"Commit this now?" and you say yes, it carries on to Git.
Continue here
When the next step is another Plan2Code step, the Next step block also
has a Continue here button. It starts that step in
this same conversation, the way a dashboard card would, with this page
turning into the new step. It goes away once the session meter is red,
because a long conversation is the reason to start a fresh one: copy
the command above into a new conversation instead.
Keyboard and preferences
Everything on the page works from the keyboard, and the gear button
lets you make it look and sound the way you like.
Keyboard shortcuts
Keys
What they do
Ctrl+Enter (⌘+Enter on a Mac)
Send your answers (not while this Help is open). In the Ask box, send the question.
Enter in the Ask box
Start a new line.
Esc
Close a dialog, this Help included. On the dashboard, back out of a card you picked.
Tab / Space
Move between options, and pick one.
Arrow keys, Home, End in Help
Move between topics.
Arrow keys, Home, End in User Preferences
Move between its tabs: up and down in the side list, left and right in the strip on a narrow window.
Every control is a real button, option or checkbox, so screen readers
and keyboard-only use work too.
Your preferences
The gear button at the top, beside ?, opens
User Preferences, always on its first tab. Its four
tabs sit in a side list, or in a strip along the top on a narrow
window:
Appearance: Theme, Card width, Highlight color and
Role.
Agents & models: the agents you can start and
the models each one offers. Each agent is a card; open one to edit
it in a side drawer.
System: Cleanup, and Desktop
app.
Sounds & activities: Sounds and Activities.
On Appearance and Sounds & activities, each change is saved the
moment you make it, and a small Saved mark shows
beside it. Close (or Esc) shuts the dialog.
Appearance
Theme: Follow my system (the
default), Light or Dark.
Card width: how wide the questions, documents and dashboard are.
Narrow (720 px),
Comfortable
(880 px, the default),
Wide (1,080 px) or
Ultra wide (1,440 px),
for an ultrawide monitor.
On a smaller window they fit the space there is.
Highlight color: one of
38, ocean blue to begin with. It marks
what is yours to do, and Planny's star uses it while he works.
Role: Engineer, Product lead / PM, Architect / tech
lead, Designer (UX), QA / test engineer or Engineering manager, or
Not set / none of these (the default). It puts the
starter templates and Ask starter questions most useful to you first,
and never changes the questions a skill asks.
Agents & models
Most people never need to change this: Plan2Code finds the agents
installed on this machine and ships an up-to-date model list with
every release. The tab opens on a table of every agent, with its
models and whether it was found on this machine. Edit
opens one agent's form, and Add agent a blank one.
Strengths in the loop: each agent's
In the loop box shows the model Thrifty, Balanced
and Best use, and you change one by tapping that word on a model in
the list below it. The Implementation Loop's per-phase strength
reads them. Untouched rows stay as shipped.
Models: each built-in agent (Claude, Devin, Codex)
shows the models that come with Plan2Code, which every update
refreshes, and below them Models you added: a model
id and the name shown in the menu. Models you added stay through
updates. Restart plan2code to see a change in its model
menu.
Agents: an agent you add is another command-line
tool the plan2code launcher can start, beside the
built-in ones. Add agent offers the starter
templates (each says whether its command is installed) or a custom
command. Give it a name, the command to run and, if you like, a
start prompt and models, on the drawer's Launch
tab. Test checks the command
is on your PATH. The Command-line arguments fold
holds the arguments it is started with, the ones that skip its
permission prompts, and the ones that pick a model, where
{prompt} and {model} are filled in for you.
Added agents are saved in ~/.plan2code/agents.json;
Delete agent removes one.
Nothing here is saved as you type. Each form has its own
Save and Discard, and an
Unsaved badge while it holds a change. Leaving a form
with an unsaved change (another tab, another agent, Close) asks
first: save it, discard it, or keep editing.
System
Cleanup: Find files to clean up
lists what Plan2Code doesn't need in your
~/.plan2code folder: sessions nobody has opened for
30 days, and files or folders that ended up there by mistake. It
also lists this project's specs--completed/ folders
nobody has touched for 30 days, and deletes one only when git
tracks it, so git can restore it; one git does not track (the
folder is usually gitignored) is kept, with the reason shown. It
shows each one with its size, and Delete these
removes exactly that list. Your preferences, saved folders, models,
the launcher and the session you are in always stay, and the
handoffs/ folder is Plan2Code's own, so it is never
offered for removal.
Desktop app: shown only in the desktop app.
Show on the taskbar when Plan2Code needs me puts a
green dot on the taskbar button on Windows when it is your move and
a red one when it needs you, or a red badge on the dock icon on
macOS when it needs you.
Desktop app: shown only inside the desktop app,
where a switch puts a dot on the taskbar button when Plan2Code
needs you.
Sounds & activities
Sounds: Play sounds switches every
sound on or off at once. Below it, each moment has its own box:
Planny snoring and waking up, starting a skill from the dashboard,
the session opening, a started skill being ready, the session
ending, new questions for you, a reply on the Ask tab and a new tab
joining the strip. Keep only the ones you want; ticking a box plays
its sound.
Activities: Show Activities puts
the die in the top bar, which opens small games to play while you
wait. It starts unticked; untick it again to hide the die on every screen.
Play activity sounds turns the games' sounds on or
off, leaving every other sound as it is; with Play sounds off, the
games are silent too.
Back to default resets only the tab on screen:
Appearance's four settings (Role goes back to Not set), or every sound
and the two Activities switches. Agents & models and System have
nothing to reset, so it is not shown there. Your Activities best
scores stay: only Reset best scores, in the
Activities window, clears them.
Your choices are remembered on this machine and carry over to every
session you open here.
Less motion
The page has no motion switch of its own. It follows your computer's
"reduce motion" setting, and with it on, the animations stay still.
Plan2Code runs an AI agent for you. When this page shows, it could
not find one on this computer, so its whole job is getting you one.
What the states mean
Each agent on the page says what Plan2Code found when it looked:
Found: the agent is installed and ready. Pick it
and Plan2Code starts it.
Found outside PATH: the agent is installed, but
your computer's PATH does not know it, so Plan2Code cannot start
it by name yet.
Not found: the agent is not installed, or not
anywhere Plan2Code looks. Its install lines are right there, each
with a Copy button.
After you install one, press Check again: the page
re-checks without you restarting anything.
Found outside PATH
Use it from here saves the location Plan2Code found,
so the agent works without you touching PATH at all. If you would
rather fix PATH yourself, the page shows the steps for your computer.
Templates
Under the agents are templates: starting setups for
agents Plan2Code does not ship. Using one opens the same form as
adding an agent by hand, already filled in; nothing is saved until
you press Save.
Signing in is yours
Some agents ask you to sign in or enter an API key the first time
they run. Only you can do that, in the agent's own window:
Plan2Code never signs in, types a key or accepts terms for you.
Privacy and where things are saved
Nothing on this page leaves your machine, and nothing it keeps lives in
your project.
On this machine only
The page is served on 127.0.0.1, which only this
computer can reach. It is not visible on your network, so sharing the
link with someone on another machine will not work, by design. To work
through a session together, share your screen.
The page is served on 127.0.0.1, which only this
computer can reach. It is not visible on your network, and the app
shows it in its own window, so there is no link to share. To work
through a session together, share your screen.
The link is a key
The link carries a long private code. The first time it is opened, the
page swaps that code for a cookie in this browser and takes it out of
the address bar, so it does not linger in your history or show in a
screenshot. Treat the link like a password all the same: anyone on
this machine who has it can open the session.
The page's address carries a long private code. The app opens it for
you, and the page swaps that code for a cookie in the app's own web
view, so it never shows in the window, and the agent leaves it out of
the terminal panel. Anyone on this machine who has the address can
still open the session, so treat it like a password if you ever see it.
What is kept, and where
Everything lives in your home folder, under
~/.plan2code/console/ unless noted:
each session's questions, your drafts and your answers, in
sessions/<id>/;
files you attached to notes and questions, in that session's
uploads/ (a note attachment cited in a spec file is also
copied into the spec's attachments/ folder; see "Notes
and attachments");
your role, theme, colors, card width and sounds, the Show
Activities switch, the last activity you picked and your best
scores, in looks.json;
your Subagents switch for each project and skill, in
subagents.json;
handoffs you save when you stop or with the Handoff skill, in
~/.plan2code/handoffs/, one .md and one
.json each, removed after the same
30 days.
A session nobody has touched for
30 days is removed, uploads and
all, the next time a session opens. Your preferences are never removed.
Folders you add to your workspace last for one console session. The
page keeps only each folder's path, name and description, and never
looks inside.
Your project is the real record
What Plan2Code decides and builds is written to specs/
and your code, in your project. This page and the terminal are two ways
of working on those files; neither owns them. Losing a session loses
nothing that matters, and you can switch between the page and the
terminal at any time.