swmcc / swmcc/agentic-development
swarm: agents run headless; no interactive sessions, one runner per invocation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Two related constraints in thrawn swarm, both inherited from the runner abstraction (argv templates with a {prompt} placeholder):
-
Headless agents. Each pane runs e.g.
claude -p <prompt> --output-format stream-jsonon the issue — you watch and steer at the git level, but can't type into the session. An interactive mode (claudeREPL started in the worktree, issue text pre-seeded, perhaps viaherdr agent prompt) would suit "user as orchestrator" even better. Would likely need an optional per-runnerinteractive_argvin runners.toml. -
One runner per swarm invocation.
--runnerapplies to every issue. Mixing runners currently means runningswarmtwice. Could supportCOS-2101:codex COS-2102:opussyntax if wanted.
From the swarm mode PR (#4).
🤖 Generated with Claude Code
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the swarm mode PR (#4) and the runner abstraction behind thrawn swarm, including the runners.toml argv templates. Compare the proposed interactive_argv/herdr agent prompt flow with the current --runner behavior and decide whether per-issue runner selection is also in scope. Done should be defined as an agreed, testable design for interactive sessions and/or mixed runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100