Spawn named Crush subagents and pin Yolo with permissions safe/block
Crush v0.100.0 runs named background subagents you can follow up, stop, or move to another model; adds Sysadmin mode (ctrl+p or shift+tab); lets you mark Yolo commands with permissions safe/block/unblock; and handles SSH passwords and GPG pinentry inside Crush.Why this loop
v0.100.0 changes parallel work and shell trust in Crush. Subagents now run as a named background team in the transcript, sidebar, and header; address one by name for mid-run follow-ups, stop it, or move it to a different model. Split implementation, tests, and review across named workers instead of one serial session. Yolo still blocks dangerous commands, but the list is yours: permissions safe marks commands auto-approved, permissions block forbids them, permissions unblock restores restricted ones—e.g. permissions safe "go build" "cargo check", permissions block kubectl terraform, permissions unblock curl. Put those in the project so daily builds are unattended and infra CLIs stay gated. Sysadmin mode (ctrl+p palette, or shift+tab through modes) can run any system command; leave it off unless you need unrestricted shell. Use Crush SSH password handling and pinentry so GPG/SSH secrets never land in the transcript. Ignore the 28 omitted changelog lines; adopt these surfaces first.
Proposed actions
- In this Crush project run: permissions safe "go build" "cargo check" then permissions block kubectl terraform then permissions unblock curl
- Crush: spawn a named background subagent team for this change (implementation, tests, review). Watch them in the transcript, sidebar, and header. Refer to each by name for mid-run follow-ups; stop any that drift; move a stuck subagent to a different model.
- Keep Sysadmin mode off. Only when Crush must run unrestricted system commands, open the command palette with ctrl+p and choose Sysadmin, or cycle modes with shift+tab, then switch back immediately. Yolo still blocks dangerous commands unless you marked them safe.
- Authenticate SSH and GPG inside Crush using its SSH password handling and pinentry. Do not paste SSH passwords, Yubikey PINs, or GPG passphrases into the agent transcript.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costAGENTS.md / CLAUDE.md / GEMINI.md rule update
DevAgentRadar → Repo Harness Rule Patch
Goal: update our repository's permanent harness instructions based on this release.
Update the file that tool actually reads. Do not dump everything into one file.
- Claude Code → CLAUDE.md plus
.claude/(skills, hooks, settings, agents, commands). It does not read AGENTS.md natively; start CLAUDE.md with@AGENTS.md. - Codex, Copilot, Cursor, Factory Droid, Grok Build, Roo Code, Goose, OpenCode, Amp, Zed, Aider → AGENTS.md.
- Gemini CLI / Antigravity → GEMINI.md. AGENTS.md only if
context.fileNameis set. - Cursor glob-scoped rules →
.cursor/rules/*.mdc(plain.mdis ignored), not a second constitution. - Codex MCP →
.codex/config.toml, not.mcp.json. - Copilot extra instructions →
.github/copilot-instructions.md; custom agents →.github/agents/. - Windsurf →
.windsurf/rules(do not assume AGENTS.md). - Cline →
.clinerules. - Procedures → a skill (
SKILL.md). Enforcement the model must not skip → a hook. Isolated roles → subagents. - Do not fork the same rule into three tool files.
Context
Assistant: Crush Proposal: Spawn named Crush subagents and pin Yolo with permissions safe/block Summary: Crush v0.100.0 runs named background subagents you can follow up, stop, or move to another model; adds Sysadmin mode (ctrl+p or shift+tab); lets you mark Yolo commands with permissions safe/block/unblock; and handles SSH passwords and GPG pinentry inside Crush. Primary source: https://github.com/charmbracelet/crush/releases/tag/v0.100.0
Why it matters
v0.100.0 changes parallel work and shell trust in Crush. Subagents now run as a named background team in the transcript, sidebar, and header; address one by name for mid-run follow-ups, stop it, or move it to a different model. Split implementation, tests, and review across named workers instead of one serial session. Yolo still blocks dangerous commands, but the list is yours: permissions safe marks commands auto-approved, permissions block forbids them, permissions unblock restores restricted ones—e.g. permissions safe "go build" "cargo check", permissions block kubectl terraform, permissions unblock curl. Put those in the project so daily builds are unattended and infra CLIs stay gated. Sysadmin mode (ctrl+p palette, or shift+tab through modes) can run any system command; leave it off unless you need unrestricted shell. Use Crush SSH password handling and pinentry so GPG/SSH secrets never land in the transcript. Ignore the 28 omitted changelog lines; adopt these surfaces first.
Suggested actions
- In this Crush project run: permissions safe "go build" "cargo check" then permissions block kubectl terraform then permissions unblock curl
- Crush: spawn a named background subagent team for this change (implementation, tests, review). Watch them in the transcript, sidebar, and header. Refer to each by name for mid-run follow-ups; stop any that drift; move a stuck subagent to a different model.
- Keep Sysadmin mode off. Only when Crush must run unrestricted system commands, open the command palette with ctrl+p and choose Sysadmin, or cycle modes with shift+tab, then switch back immediately. Yolo still blocks dangerous commands unless you marked them safe.
- Authenticate SSH and GPG inside Crush using its SSH password handling and pinentry. Do not paste SSH passwords, Yubikey PINs, or GPG passphrases into the agent transcript.
Config surfaces this release may change
- permission rules — check your repo before applying
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/crush-v0-100-0-spawn-named-crush-subagents-and-pin-yolo-with-permissions and mark Applied, Skipped, or Failed. Proposal id: 0b21e14f-510a-4b43-9a12-06466abd8798
Instructions:
- Read the existing context files and settings for the tools in this repo.
- Draft an explicit Git diff. Update ONLY agent harness rules or tool configuration.
- Call out deprecated flags, obsolete habits, or changed permission boundaries.
- Do not touch application logic.
Start with the proposed diff and say which layer and which tool's file it belongs in.
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.