Sync upstream web console updates into v2.5.0: a Subagents switch that tells the agent to use helpers (per project and skill, sent as a standing instruction only when it changes), a Subagents tab listing the helpers the agent reports, a standalone review that asks what to review instead of assuming the branch diff, a refusal for doc patches that move a version backwards, and the project name in the footer and browser tab title

This commit is contained in:
jparkerweb committed 2026-10-06 17:57:22 -07:00
1 parent 8fb19ec933
commit eac5f6590f
179 files changed
+14955 -466

No files matched your search

@@ -64,6 +64,13 @@ progress bar is the first thing someone watching a build looks at. The session
meter counts the build's tasks from `cleared` as it rises, so keep it current,
and start every phase (a second one in the same run too) at `"cleared": 0`.
`"version": 1` is for the first phase of a session only. A doc's version
never goes back (console.md → House rules, rule 9), so a later phase in the
same session reposts `phase` and `phasefile` at one more than the version the
page holds, with the new phase's title and content. The same goes for
`report` at sign-off and `review` in a mid-session review: version 1 the
first time, then up from wherever the page has it.
`phasefile` is the whole `phase-X.md`, verbatim from disk, as its own tab —
the person can read the prerequisites and task specs while you build. Re-post
it whenever the file changes, which is every task: the checkbox write that
@@ -111,6 +118,12 @@ printed), never into the project or into `~/.plan2code/console/` directly:
- Do not call `wait` while building. There is nothing to collect, and the page
holds anything the person sends until you next look.
A build may receive a `Subagents:` standing instruction, on `open` output or a
`chat` check between tasks. Follow console.md → Standing instructions for
handing independent tasks to helpers and reporting them as `helpers`. Keep the
per-task progress posts, the checkbox writes, the chat checks and the sign-off
with you.
### Quick questions between tasks
The person can ask a Quick question on the Ask tab at any point in a build
@@ -195,7 +208,8 @@ only ever be offered once nothing could come of it:
`reply` carries `Approve this phase: approved`, which is the terminal's
`approved`. If the note that came with an approval asks for a change, treat it
as "describe any issues": do the change first and ask again. `changes` means
exactly what it says: address it, bump the report's version, and reopen the
exactly what it says: address it, bump the report's version (a later phase's
report starts above the last one's, too), and reopen the
item (`"status": "reopened"`) with a reply in its `thread`. `review` is the
person asking for the code review before they approve anything — see "The
review, mid-session" below.