storm: #38 - feat: war-room multi-agent mode#39
Closed
casperpanduro wants to merge 2 commits intomainfrom
Closed
Conversation
Contributor
Author
Storm Agent Summary
|
7 tasks
Contributor
Author
|
Please update the docs for this new command |
Contributor
Author
Storm Continue Summary
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #38
Summary
feat: war-room multi-agent mode
Overview
Add a
storm war-roomcommand that spins up multiple named Claude Code agentsin a shared workspace. Instead of one agent working alone, a team of agents with
defined roles collaborate, debate, and divide work until the task is done.
Motivation
Complex issues benefit from multiple perspectives — an Architect to plan, an
Engineer to implement, and a QA agent to validate. Rather than one agent doing
everything sequentially, war-room lets them run in parallel and self-organize.
Proposed CLI
storm war-room --issue 42
storm war-room --issue 42 --agents architect,engineer,qa
storm war-room --prompt "Build a dark mode toggle"
How it should work
claude -pprocess with a defined role + personalitytalk [room] [message]— post a message to the shared roombash [command]— run a shell command (costs kibble)transfer-kibble [amount] [agent]— send budget to another agentread-file [path]— read a file (costs kibble)%%STORM_DONE%%and a PR is openedAgent roles (defaults)
Roles should be configurable via
.storm/agents/directory (same primitive patternas contexts and instructions).
.storm/agents/ structure
.storm/
└── agents/
├── architect/
│ └── AGENT.md # role description, kibble budget, personality
├── engineer/
│ └── AGENT.md
└── qa/
└── AGENT.md
AGENT.md frontmatter
name: Johnny
role: Engineer
kibble: 20
model: sonnet
You are Luna, a pragmatic senior engineer. You implement what the Architect
specifies, ask clarifying questions when the spec is unclear, and always run
the typecheck before declaring work done.
Shared event log format
Each event is a JSON line appended to
.storm/session/{id}/events.jsonl:{ "ts": 1234567890, "agent": "Johnny", "type": "talk", "room": "war-room", "data": "..." }
{ "ts": 1234567890, "agent": "Storm", "type": "bash", "room": "war-room", "data": "git diff" }
{ "ts": 1234567890, "agent": "Johnny", "type": "kibble", "room": "war-room", "data": { "to": "Storm", "amount": 3 } }
Terminal UI
Split view similar to the reference screenshot:
Acceptance criteria
storm war-room --issue <n>starts a session with default agentsclaude -pprocess%%STORM_DONE%%is emitted.storm/agents/References
storm runimplementationChanges
index.tssrc/__tests__/war-room-agent.test.tssrc/__tests__/war-room.test.tssrc/commands/war-room.tssrc/core/constants.tssrc/core/types.tssrc/core/war-room.tssrc/primitives/war-room-agent.ts8 files changed, 973 insertions(+)
Considerations
Test Plan
Automatically generated by storm-agent on branch
storm/issue-38-feat-war-room-multi-agent-mode.