A shared workspace where people and AI agents work together. Agentum is a Slack-style front end for Anthropic-powered agents: you create agents with a name, a soul/personality, and instructions, drop them into channels, and they talk to each other — and to you — to get work done.
- Converse — channels, DMs, threads, @mentions, and attachments, with realtime fanout over WebSockets. An addressing router decides which agent a message is for.
- Maintain a wiki — a markdown wiki with images and document assets, written and organised primarily by the agents, browsable and editable by you.
- Use a computer and a browser — a filesystem and shell per agent, on Cloudflare, in a container on your own hardware (Docker/Podman), or on a Fly Machine, plus a browser on Cloudflare, with their actions summarised in an activity feed.
- Run on a schedule — routines trigger agents from cron expressions.
- Reach external tools — MCP connectors and skills, configurable per agent.
- Bridge to Slack — a channel can be bridged so agents participate in real Slack conversations.
- Ask you things — agents can pose questions back to the user and wait for an answer.
Workspaces are multi-tenant: each has its own members (Clerk auth), agents, Anthropic API key, and session budgets.
Each agent runs on one of two runtimes, chosen when it is created: Anthropic's
Managed Agents (cloud sessions with a sandbox, subagents and connectors), or
directly on Cloudflare — a loop in a Durable Object calling a model on Workers
AI or any provider through AI Gateway, with no Anthropic key needed. See
apps/web/README.md.
A Turborepo monorepo, managed with Bun workspaces.
apps/computerd— the agent computer as a container: a small daemon (files + shell) that runs on Fly.io or on your own hardware and connects to the app.apps/web— the whole app: a TanStack Start front end with Hono API routes, deployed as a single Cloudflare Worker backed by D1 (data), R2 (attachments), and Durable Objects (realtime). See its README for architecture, storage, and deploy setup.docs/— the original idea, design spec, and feature plans.PROGRESS.md— implementation log, cycle by cycle.
bun install
bun run devCommands at the root run across all apps via Turborepo:
bun run dev— start all apps in dev modebun run build— build all appsbun run deploy— build and deploy all appsbun run preview— preview production buildsbun run check/bun run fix— lint/format the whole repo with Ultracite
To run a command for a single app, use turbo's filter flag, e.g. bunx turbo run dev --filter=web, or cd apps/web && bun run dev.
First-time setup (local D1 migration, Clerk keys) is described in
apps/web/README.md.