daimon

Your team just hired a data scientist.

daimon is a collaborative data science agent in your team's Discord or Slack. It writes and runs code, fits Bayesian models with PyMC, and delivers charts and runnable notebooks in the thread.

Add it to your server in one click → or self-host it from this repo.

Most chat bots are one agent shared across a workspace. daimon is many-to-many: you deploy it once, on your own Anthropic API key, and any number of Discord servers install it from that single deployment. Every server is isolated: one tenant, its own data, scoped to that server. Adding a server takes about two minutes: invite the bot, run /agent-setup, and everyone in it can @mention a working agent.

Built on Anthropic Managed Agents by PyMC Labs, the team behind the PyMC project.

Status: early. The code is public and you can run it yourself (see below), but self-hosting is not a supported path yet. Expect rough edges and breaking changes. The hosted version at daimon.decision.ai is the easy path.

• @daimon in a channel starts (or continues) a threaded conversation with session continuity
• Slash-command admin surface: /agent-setup, /routines, /billing, /privacy, /help. Setup and routines require Discord's Manage Server permission; the rest are open to everyone
• Scheduled routines: recurring agent runs dispatched headlessly
• Slack adapter (optional) with full Discord parity, per-workspace OAuth install, and opt-in per-user access (docs/slack.md)
• CLI and MCP adapters sharing the same core turn pipeline
• Tenant isolation enforced at the database tenant_id layer, so one shared Anthropic key can safely power every guild

flowchart LR
    a["your Discord server"] --> d
    b["another Discord server"] --> d
    c["a Slack workspace"] --> d
    d["daimon<br>one deployment, your Anthropic key"] --> e["Claude<br>(Anthropic Managed Agents)"]

You run one copy of daimon. Every community that installs it gets its own agent with its own memory, and none of them can see each other's data. When someone @mentions the bot, daimon hands the conversation to Claude and posts the replies back into the thread.

flowchart LR
    subgraph adapters
        direction TB
        Discord
        Slack
        CLI
        MCP
        Scheduler
    end
    adapters --> core["daimon core<br>turn pipeline"]
    core <--> ma["Anthropic Managed Agents<br>agents &middot; sessions &middot; skills"]
    core --> pg[("Postgres<br>tenants &middot; thread&harr;session map")]

Unsupported, but it works. You need an Anthropic API key with Managed Agents beta access (a closed beta: request access first, or session creation will fail) in a workspace dedicated to this deployment (daimon manages the workspace's Managed Agents resources as its own, so sharing the workspace with anything else causes collisions), Docker, and uv.

cp .env.example .env

Open .env, then uncomment and fill in:

• DAIMON_ANTHROPIC__API_KEY: your beta-enabled Anthropic key
• DAIMON_MCP__JWT_SECRET: any random string (e.g. openssl rand -hex 32)
• DAIMON_MCP__PUBLIC_URL: http://localhost:8765/mcp is fine for local use
• POSTGRES_PASSWORD: a strong, URL-safe value (avoid @ : / % #)

All four must be set before your first docker compose command: docker-compose.yml interpolates them for every service with fail-fast ${VAR:?...} guards, even for docker compose up -d postgres. You'll add the Discord bot token in step 4. .env is gitignored, so secrets never get committed.

uv sync --all-extras --all-packages

docker compose up -d postgres
export DAIMON_DATABASE_URL=postgresql+asyncpg://daimon:<your-POSTGRES_PASSWORD>@localhost:5432/daimon
uv run alembic upgrade head

The export is required because the alembic CLI reads the shell environment and does not auto-load .env.

Then seed the default agents, environments, and skills:

uv run daimon defaults apply

1. Create an application in the Discord Developer Portal.
2. Under Bot, create a bot user and copy its token into .env as DAIMON_DISCORD__BOT_TOKEN.
3. Still under Bot, enable the Message Content Intent. It's a privileged intent, and without the portal toggle the bot can't read mentions.
4. Under OAuth2 → URL Generator, select the bot and applications.commands scopes, then under Bot Permissions select at least Send Messages, Send Messages in Threads, Create Public Threads, Manage Threads, and Read Message History.
5. Open the generated URL in a browser and invite the bot to a test server you control.

uv run python -m daimon.adapters.discord

Send a message that @mentions the bot. It replies in a new thread, and that's a working deployment. docker-compose.yml also runs the full stack (Postgres plus the mcp, discord, and scheduler process groups) from one image if you'd rather not run processes by hand.

• packages/core/ — daimon-core library (MA client, stores, turn pipeline)
• packages/adapters/cli/ — the daimon admin CLI
• packages/adapters/discord/ — the Discord bot adapter
• packages/adapters/mcp/ — the MCP server adapter
• packages/adapters/slack/ — the Slack adapter (optional)
• packages/adapters/scheduler/ — the routines scheduler adapter
• packages/testing/ — shared test fixtures/harness
• apps/notebook-host/ — standalone marimo notebook host service
• defaults/ — YAML defaults seeded into Managed Agents + local DB
• tests/ — cross-package integration tests

See CONTRIBUTING.md for dev environment setup and the quality gates every PR must keep green.

See SECURITY.md for how to report a vulnerability.

MIT