Question 1

What is MCP?

Accepted Answer

MCP servers give Claude access to external tools: Notion MCP → Read and write Notion pages GitHub MCP → Create PRs, manage issues Memory MCP → Persist memory across sessions

Question 2

Why only the Karo updates dashboard.md

Accepted Answer

1. Single writer: Prevents conflicts by limiting updates to one agent 2. Information aggregation: The Karo receives all Ashigaru reports, so it has the full picture 3. Consistency: All updates pass through a single quality gate 4. No interruptions: If the Shogun updated it, it could interrupt the Lord's input

Question 3

Why Mailbox System?

Accepted Answer

Why use files instead of direct messaging between agents? | Problem with direct messaging | How mailbox solves it | |-------------------------------|----------------------| | Agent crashes → message lost | YAML files survive restarts | | Polling wastes API calls | inotifywait is event-driven (zero CPU while idle) | | Agents interrupt each other | Each agent has its own inbox file — no cross-talk | | Hard to debug | Open any .yaml file to see exact message history | | Concurrent writes corrupt data | flock (exclusive lock) serializes writes automatically | | Delivery failures (character corruption, hangs) | Message content stays in files — only a short "you have mail" nudge is sent through tmux |

Question 4

Why a hierarchy (Shogun → Karo → Ashigaru)?

Accepted Answer

1. Instant response: The Shogun delegates immediately, returning control to you 2. Parallel execution: The Karo distributes to multiple Ashigaru simultaneously 3. Single responsibility: Each role is clearly separated — no confusion 4. Scalability: Adding more Ashigaru doesn't break the structure 5. Fault isolation: One Ashigaru failing doesn't affect the others 6. Unified reporting: Only the Shogun communicates with you, keeping information organized

Question 5

How it Works

Accepted Answer

1. Install the ntfy app (free, no account needed) 2. Speak to your phone: "dentist tomorrow", "invoice due Friday" 3. AI auto-organizes → morning notification: "here's your day"

Question 6

What is SayTask?

Accepted Answer

Task management for people who hate task management. Just speak to your phone. Talk Coding, not Vibe Coding. Speak your tasks, AI organizes them. No typing, no opening apps, no friction. Target audience: People who installed Todoist but stopped opening it after 3 days Your enemy isn't other apps — it's doing nothing. The competition is inaction, not another productivity tool Zero UI. Zero typing. Zero app-opening. Just talk "Your enemy isn't other apps — it's doing nothing."

Question 7

What shutsujin_departure.sh does:

Accepted Answer

✅ Creates tmux sessions (shogun + multiagent) ✅ Launches each agent with the CLI configured in config/settings.yaml (Claude/Codex/Copilot/Kimi/OpenCode) ✅ Auto-loads instruction files or generated agent definitions for each CLI ✅ Resets queue files for a fresh state ✅ Starts ntfy listener for phone notifications (if configured) After running, all agents are ready to receive commands! --- 🔧 Manual Requirements (click to expand) If you prefer to install dependencies manually: | Requirement | Installation | Notes | |-------------|-------------|-------| | WSL2 + Ubuntu | wsl --install in PowerShell | Windows only | | Set Ubuntu as default | wsl --set-default Ubuntu | Required for scripts to work | | tmux | sudo apt install tmux | Terminal multiplexer | | Node.js v20+ | nvm install 20 | Required for MCP servers | | Claude Code CLI | curl -fsSL https://claude.ai/install.sh \| bash | Official Anthropic CLI (native version recommended; npm version deprecated) | | OpenAI Codex CLI | Install from the official OpenAI Codex distribution | Required only for agents with type: codex | | GitHub Copilot CLI | Install and authenticate GitHub Copilot CLI | Required only for agents with type: copilot | | Kimi Code CLI | Install and authenticate Kimi Code | Required only for agents with type: kimi | | OpenCode CLI | npm install -g opencode-ai | Required only for agents with type: opencode; provider API keys must be available in the agent shell | | Cursor CLI | See Cursor CLI docs — use cursor-ag

Question 8

What install.bat does automatically:

Accepted Answer

✅ Checks if WSL2 is installed (guides you if not) ✅ Checks if Ubuntu is installed (guides you if not) ✅ Shows next steps (how to run first_setup.sh)

Question 9

Why CLI (Not API)?

Accepted Answer

Most AI coding tools charge per token. Running 8 Opus-grade agents through the API costs $100+/hour. CLI subscriptions flip this: | | API (Per-Token) | CLI (Flat-Rate) | |---|---|---| | 8 agents × Opus | ~$100+/hour | ~$200/month | | Cost predictability | Unpredictable spikes | Fixed monthly bill | | Usage anxiety | Every token counts | Unlimited | | Experimentation budget | Constrained | Deploy freely | "Use AI recklessly" — With flat-rate CLI subscriptions, deploy 8 agents without hesitation. The cost is the same whether they work 1 hour or 24 hours. No more choosing between "good enough" and "thorough" — just run more agents.

Question 10

What makes this different

Accepted Answer

Zero coordination overhead — Agents talk through YAML files on disk. The only API calls are for actual work, not orchestration. Run 8 agents and pay only for 8 agents' work. Full transparency — Every agent runs in a visible tmux pane. Every instruction, report, and decision is a plain YAML file you can read, diff, and version-control. No black boxes. Battle-tested hierarchy — The Shogun → Karo → Ashigaru chain of command prevents conflicts by design: clear ownership, dedicated files per agent, event-driven communication, no polling.

Question 11

Why Shogun?

Accepted Answer

Most multi-agent frameworks burn API tokens on coordination. Shogun doesn't. | | Claude Code Task tool | Claude Code Agent Teams | LangGraph | CrewAI | multi-agent-shogun | |---|---|---|---|---|---| | Architecture | Subagents inside one process | Team lead + teammates (JSON mailbox) | Graph-based state machine | Role-based agents | Feudal hierarchy via tmux | | Parallelism | Sequential (one at a time) | Multiple independent sessions | Parallel nodes (v0.2+) | Limited | 8 independent agents | | Coordination cost | API calls per Task | Token-heavy (each teammate = separate context) | API + infra (Postgres/Redis) | API + CrewAI platform | Zero (YAML + tmux) | | Multi-CLI | Claude Code only | Claude Code only | Any LLM API | Any LLM API | 7 CLIs (Claude/Codex/Copilot/Kimi/OpenCode/Cursor/Antigravity) | | Observability | Claude logs only | tmux split-panes or in-process | LangSmith integration | OpenTelemetry | Live tmux panes + dashboard | | Skill discovery | None | None | None | None | Bottom-up auto-proposal | | Setup | Built into Claude Code | Built-in (experimental) | Heavy (infra required) | pip install | Shell scripts

Question 12

What is this?

Accepted Answer

multi-agent-shogun is a system that runs multiple AI coding CLI instances simultaneously, orchestrating them like a feudal Japanese army. Supports Claude Code, OpenAI Codex, GitHub Copilot, Kimi Code, OpenCode, Cursor, and Antigravity. Why use it? One command spawns 7 AI workers + 1 strategist executing in parallel Zero wait time — give your next order while tasks run in the background AI remembers your preferences across sessions (Memory MCP) Real-time progress on a dashboard.

Panoramica

Funzionalità chiave

Prezzi

Casi d’uso

Scegliere il modello giusto per un'attività

Confrontare i modelli di Claude e Codex

Pro & contro

Pro

Contro

Recensioni

Domande e risposte

Fai una domanda

Alternative a Competenze