Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

Hotfix: built-in PM section: never block people on a start; long reading goes to a subagent (#3121)

0xken152e7edbf1cd55
diff --git a/backend/src/superTabs/pmSchedule.test.ts b/backend/src/superTabs/pmSchedule.test.ts
index 578bbe31c..41dc1cf7a 100644
--- a/backend/src/superTabs/pmSchedule.test.ts
+++ b/backend/src/superTabs/pmSchedule.test.ts
@@ -117,6 +117,27 @@ describe('the built-in PM schedule', () => {
expect(text).toContain('follow the instructions and say so')
})
+ // Ken, 11-05: River's own script started Poplar on Gray.local at 14:01 and waited in the foreground until the start failed
+ // at 14:09; for 6.5 minutes no person's message was read. The CLI's start returns in about 20 s; the wait was the PM's.
+ it('tells the coordinator to run a start in the background and keep answering people', () => {
+ const text = PM_SCHEDULE_TEXT.replace(/\s+/g, ' ')
+ expect(text).toContain('while a command runs you read no one\'s messages')
+ expect(text).toContain('When your tool runs commands in the background (Claude Code: run_in_background)')
+ // Only resume finishes a pending start, and an assignment before it settles is refused (START_PENDING): a PM without
+ // background commands needs the command by name, once a turn (review of #3121).
+ expect(text).toContain('on your next turn run `resume START_ID` once')
+ expect(text).toContain('Never repeat `resume` in a loop in the foreground')
+ })
+
+ // Ken, 11-05: River ran 1,389 Swarm commands in a day in its own session, and long reads fill its context until it is
+ // compacted and the instructions fall out of it.
+ it('tells the coordinator to hand long reading to a background subagent, which never writes code or decides', () => {
+ const text = PM_SCHEDULE_TEXT.replace(/\s+/g, ' ')
+ expect(text).toContain('to a subagent that runs in the background')
+ expect(text).toContain('take back only its summary')
+ expect(text).toContain('A subagent never writes code and never decides')
+ })
+
it('keeps the instructions short, and counts what a person had to repeat in the nightly reflection', () => {
expect(PM_SCHEDULE_TEXT).toContain('past 150 lines')
expect(PM_SCHEDULE_TEXT).toContain('is a repeat')
diff --git a/backend/src/superTabs/pmSchedule.ts b/backend/src/superTabs/pmSchedule.ts
index 588b94b26..c3b8a26fe 100644
--- a/backend/src/superTabs/pmSchedule.ts
+++ b/backend/src/superTabs/pmSchedule.ts
@@ -36,6 +36,14 @@ message names it. This section is not part of the project's document: never save
How you work:
- You never write code yourself, even when a person asks you directly: open a task and give it to an Engineer.
+- Never make people wait on a start: while a command runs you read no one's messages. When your tool runs commands in the
+ background (Claude Code: run_in_background), run the start, \`resume START_ID\` until the agent is ready, and its
+ assignment as one background command, and keep answering people; act on its result when it ends. Without background
+ commands, run \`start\` once and go on; on your next turn run \`resume START_ID\` once, and assign the agent when it is
+ ready. Never repeat \`resume\` in a loop in the foreground.
+- Hand long reading (a pull request's diff, CI logs, a long thread, production numbers) to a subagent that runs in the
+ background when your tool has them, and take back only its summary: your own context stays small, so these instructions
+ stay in it. A subagent never writes code and never decides; you do.
- The project's instructions outrank the repository's own agent files (CLAUDE.md, AGENTS.md). When they conflict, follow
the instructions and say so.