kiro-discord-bot

繁體中文 README | Full documentation

A Discord bot and control plane for project-bound ACP agents.

kiro-discord-bot connects Discord channels and threads to ACP-compatible coding agents over stdio. Kiro CLI is the default engine, while OMP can be enabled as an optional replacement behind the same Discord commands, MCP policy, audit, usage, cron, memory, and thread-agent controls.

Each initialized channel can bind to a real project directory, keep its own agent session, remember project guidance, and expose Model Context Protocol (MCP) tools through explicit channel policy.

This repository README is intentionally short. The detailed user guide, admin guide, MCP setup, release runbook, and troubleshooting docs live on the documentation site.

New deployments should start with Kiro CLI unless an OMP workflow is already prepared. See Agent Engines for the product-level tradeoffs and runtime details.

Kiro CLI and OMP are external agent CLIs. This project starts and controls them from Discord, but their installation, authentication, model access, and CLI updates are maintained by their own projects.

Why It Is Different

  • Project-bound ACP agents: each Discord channel maps to a working directory and an agent session.
  • Engine flexibility: keep Kiro as the default, or enable OMP for selected channels and threads without changing the Discord workflow.
  • Trainable context: use memory, flash memory, steering files, conversation history, and project knowledge instead of starting from zero every time.
  • Safe tool expansion: MCP servers are discovered as a catalog, then exposed per channel through policy and a proxy.
  • Operational controls: admin panels and sensitive diagnostics use private replies where Discord supports them.
  • Automation: cron jobs and reminders let an agent run scheduled work under channel ownership.

Quick Start

  1. Install and authenticate at least one ACP engine: kiro-cli or omp.
  2. Create a Discord bot with bot and applications.commands scopes, Message Content Intent, and the required channel/message permissions.
  3. Download the latest release archive or build from source.
  4. Provide environment variables such as DISCORD_TOKEN, DISCORD_GUILD_ID, DEFAULT_CWD, and DATA_DIR.
  5. Run the bot once in the foreground and confirm it logs in.
  6. In Discord, run /cwd in a channel to bind it to a project.
  7. Run /doctor to verify permissions and enabled engine readiness.

Continue with the full installation guide.

Common Docs

Topic Start here
First-time setup Getting Started · Installation
Daily use Command Reference · Listen Modes
Agent engines Agent Engines · Environment
Agent context Steering Files · Core Concepts
Tool access MCP Policy · Bot Tools · Discord MCP Server · Media MCP Server
Operations Environment · Deployment · Release Runbook
Security and review Security Model · Audit, Usage, and Privacy
Support Troubleshooting · macOS MCP Networking

Build From Source

VERSION=$(git describe --tags --always 2>/dev/null || echo "dev")
go build -ldflags "-X main.Version=$VERSION" -o kiro-discord-bot .
go build -o mcp-discord-server ./cmd/mcp-discord
go build -o mcp-media-server ./cmd/mcp-media

Release and Operations

Run the release preflight before tagging or deploying:

scripts/release-preflight.sh

Follow the release runbook for tagging, publishing, deployment, and rollback.

License

MIT