Koshi.Agents 0.9.1

Koshi.Agents

One-command installer for Koshi sub-agent personas into Claude Code and GitHub Copilot CLI.

Companion tool to Koshi.Mcp. Where Koshi.Mcp ships the 24 MCP tools (retrieval, memory, context, team telemetry), Koshi.Agents ships the personas that drive those tools with strict allow-lists, handoff rules, and refusal patterns baked in.

Install

dotnet tool install --global Koshi.Agents

Quick start

# What personas are available?
koshi-agents list

# Show what a persona will do (and which MCP tools it can call)
koshi-agents show koshi-librarian

# Install all 5 personas for Claude Code (also registers the koshi MCP entry)
koshi-agents install --client claude

# ...or Copilot CLI
koshi-agents install --client copilot

# ...or both, scoped to current repo only
koshi-agents install --client both --scope repo

# Install personas only — leave the client's MCP config untouched
koshi-agents install --client copilot --no-mcp

# Preview without writing
koshi-agents install --client claude --dry-run

# Check that everything wired up correctly
koshi-agents doctor

# Remove personas (configs are untouched)
koshi-agents uninstall --client both

The personas

Each persona ships in two formats:

• Claude Code agents → ~/.claude/agents/*.md with mcp__koshi__<tool> allow-lists
• Copilot CLI agents → ~/.copilot/agents/*.agent.md with markdown front-matter

Scopes

What doctor checks

• The koshi-mcp global tool is installed and on PATH
• An MCP config file exists for the requested client
• A koshi server entry is registered in that config
• Personas are present in the expected directory
• Tool allow-lists in the personas match the tools the running koshi-mcp actually advertises

doctor never writes to client configs. It tells you what's wrong and prints the exact JSON snippet to paste.

What this is not

• Not a copy-paste guide. Use koshi-agents install instead.
• Not a full config editor. install adds (or refreshes) only the mcpServers.koshi entry in the client's MCP config — every other key is left untouched, and the previous file is snapshotted to <file>.bak before any write. Pass --no-mcp to skip the config write entirely, or --dry-run to preview.
• Not telemetry. Nothing in this tool phones home.

Next steps

After installing:

koshi-agents doctor    # verifies every detected client sees the server
koshi-agents list      # shows the 5 personas you can use

Then open your MCP client — the personas appear under the Koshi namespace (mcp__koshi__* in Claude Code, koshi/* in Copilot CLI). Ask the agent any project question.

Known issues

Hitting something unexpected? Search open bugs before assuming it's you. Most setup issues are covered in the troubleshooting guide.

Prerequisites

• A working koshi-mcp on PATH (install Koshi.Mcp first, or use the shell installer).
• .NET 10 SDK or runtime (required by dotnet tool install).

License

MIT — see LICENSE.