open source · MIT

Run a multi-agent
engineering team.

Allen is an open-source AI engineering team that runs on your repos — specialist agents, deterministic orchestration through workflows, and approval gates you control. Drive it from chat, Slack, or Linear.

MIT licensedSelf-hostedRuns on Claude or OpenAI
allen.local · fix checkout crash
Conversation/eng-412just now
Reply…
Workflow· bug-fix-by-severity running
01
Pick up ticketENG-412 · Linear
02
Spin up workspaceisolated git branch
03
Investigatetrace cart-empty path
04
Plan3 lanes proposed
05
Implement · in parallelfrontend ∥ backend ∥ tests
06
Converge & test42 tests · all green
07
Code reviewscoped reviewer agent
08
Open PR#412 · ready
why allen

One agent isn't a team. Allen is.

Most AI coding tools give you one assistant in your editor. Allen is an orchestration framework that runs many — a planner delegates to builders, builders fan out in parallel, a reviewer signs off, all on a workflow you can replay step for step.

01 · multi-agent

Teams that delegate.

A product-manager scopes the work and hands it to the engineering-lead, who spawns specialists — technical-designer, backend- and frontend-developer, test-writer, code-reviewer — each with its own role, model and tool scope.

02 · parallel

Many agents at once.

Long-running work fans out across independent lanes — frontend, backend, tests — each in its own isolated branch and terminal. They run concurrently, then converge.

03 · deterministic

Workflows, not vibes.

Long jobs run as graphs with explicit nodes, structured outputs and human checkpoints. Retries on failure, branches on condition. Every run is fully traced — replay it step by step.

how it works

Four steps. Then it runs.

Fix the checkout crash on ENG-412 and open a PR.
Loaded ENG-412 from Linear. I see a stack trace from yesterday — want me to start there?
routed to workflow · bug-fix-by-severity
engineering-leaddelegates
+ backend-developer, frontend-developer, test-writerspawned
workspacebranch eng-412
frontend-developerCartContext.tsx · running
backend-developersubmit.ts · running
test-writervitest · spinning up
3 agents · same workflow · isolated branchesparallel
approved by you3 lanes merged · tests passed · reviewer signed off.
Fix race condition in checkout submit
#412 · main ← eng-412 · 3 files changed · +12 −4
tests ✓ 42 pass
review ✓ approved
full execution tracereplayable
what's inside

Works with what
you already use.

Allen plugs into the tools you're on — Linear, GitHub, Slack — and runs on the AI coding agents you trust. Bring your own keys.

GitHub
Linear
Slack
Claude Code
OpenAI Codex
MCP servers
Cron schedules
Database
from anywhere

Drive Allen from Slack.

You don't need to be at your desk. Allen plugs into your Slack workspace as a teammate — same agents, same workflows, same context as the UI.

  • · Ask questions in any channel or DM
  • · Assign tickets and kick off workflows
  • · Approve checkpoints from your phone
  • · Get streaming status while you're away
#eng-coordination12
MR
Maya R.2:14 PM
@allen what's the status of ENG-412?
[a]
allenAPP2:14 PM
ENG-412 · bug-fix-by-severity · step 6/8 · code review in progress (28s).
MR
Maya R.2:18 PM
@allen review PR #412 — security, perf, style.
[a]
allenAPP2:18 PM
Running resolve-pr-reviews on #412. 3 reviewers in parallel — security, perf, style.
[a]
allenAPP2:19 PM
Findings: 4 blocking · 7 nitpicks · inline comments posted.
MR
Maya R.2:24 PM
@allen approve the checkout fix.
[a]
allenAPP2:24 PM
✓ Approved. Workflow resumed · ETA 2m.
Message #eng-coordination
running on day one

Allen starts as a team,
not a blank page.

Spin up Allen and a full engineering org is already running — six teams, 20+ agents, pre-built workflows. Edit them in chat. Add your own without writing a line of YAML.

the org

6 teams. 20+ agents.

seeded

Team leads delegate, specialists execute. Use as-is — or edit, extend and add your own.

executive
ceo
product
product-managerrequirements-analystbrainstormerdoc-auditor
engineering
engineering-leadbackend-developerfrontend-developercode-reviewersecurity-specialistbug-investigatorpr-creator
quality
qa-leadtest-plannertest-writer
meta
workflow-builder-agentagent-builder-agentresearch-agentrepo-scanner
unassigned
+ your custom agents
the workflows

Deterministic pipelines.

ready

Plan, build, fix, review, document — ship-ready graphs you can run unchanged or fork.

  • 01feature-plan-and-implement.yml
  • 02bug-fix-by-severity.yml
  • 03tdd-design-by-severity.yml
  • 04milestone-implementation-from-prd-tdd.yml
  • 05resolve-pr-reviews.yml
  • ·+ describe one in chat, Allen drafts the YAML
  • ·+ visual builder for your own
  • ·+ YAML for your own
no manual config

Build agents and workflows by chatting.

chat → built

You don't have to hand-author YAML or click through a builder. Describe the agent you want, or the pipeline you need — Allen scaffolds the prompt, picks the model, scopes the tools, wires the graph, and saves it to your Allen instance. Tweak, replay, ship.

you
Make me a security-reviewer agent that scans PR diffs for secrets and unsafe deserialization. Block on findings, never auto-fix.
[a]
Drafted agents/security-reviewer.yml · scoped to read_file,grep,github.review · modelsonnet. Ready to commit?
you
Also wire it into the bug-fix workflow as a blocking checkpoint before the PR opens.
[a]
Updated bug-fix-by-severity· new node security-review added before open_pr, gated on approval.
make it yours

Define your own agents.
Wire your own workflows.

The built-in team is a starting point, not a ceiling. Add agents with their own prompts and tool scopes. Compose workflows from a visual canvas or write them as YAML. Both ship in the repo.

Custom agents

One role, one prompt, one scope.

bring your own

Pick a model, write the system prompt, scope which tools and MCP servers it sees, and declare who it can delegate to. Drop it in and Allen picks it up automatically.

name: security-reviewermodel: sonnettools: [read_file, grep, github.review]delegates_to: [test-writer]prompt: |  # role  Audit diffs for secrets, injection,  unsafe deserialization. Block if  found. Suggest a fix, never apply.
Custom workflows

Deterministic graphs, your way.

visual or YAML

Compose nodes on a canvas or describe them in chat — Allen drafts the YAML. Conditional branches, parallel lanes, retries, structured outputs, human checkpoints. Versioned in your repo.

trigger
investigate
approval
frontend
backend
tests
converge
open PR
built-in context engine

The right context,
fed to the right agent.

Allen ships with an inbuilt context engine. It starts with the context you already have and keeps learning as you work — then feeds each agent only the slice that's relevant. No noise. No wasted tokens. No hallucinated detail.

Context Enginecontext.db · learning
live
ticketENG-412
ticketacceptance criteria
repo-mapcheckout/
decisionuse idempotency-key
artifactstack-trace.log
artifact+12 −4 diff
conventionsrepo-style.md
historyrun-2026-05-19
planner agentpulling…
scoping ENG-412
backend developer
implementing submit.ts
reviewer agent
reviewing PR #412
faq

Questions teams ask
before running Allen.

Why use Allen instead of Claude Code CLI or the Codex app?

Claude Code and Codex are great for direct single-agent coding sessions. Allen is for coordinated engineering work: multiple agents, delegated tasks, isolated workspaces, workflow checkpoints, live traces, artifacts, and repeatable execution across real repositories.

Does Allen replace Claude Code or Codex?

No. Allen builds on them. It can run Claude Code CLI and Codex as execution engines, then adds orchestration, visibility, approvals, integrations, and team-level workflow management around them.

How does Allen make agent work easier to trust?

Allen keeps agent work observable. Every run has live traces, logs, tool calls, artifacts, isolated workspaces, and human checkpoints, so teams can see what happened, review outputs, and approve important steps before work continues.

Can I control agents from Slack?

Yes. Allen can integrate with Slack so teams can communicate with agents from existing Slack threads, dispatch work, follow progress, and keep engineering conversations connected to the actual agent execution.

Is Allen self-hosted and open source?

Yes. Allen is MIT licensed and self-hosted, so your team can run it on your own infrastructure, connect your own repositories and tools, inspect the code, and adapt the system to your workflow.

quickstart

Up and running in 5 minutes.

Run Allen on your laptop, on a dev box, or in your own cloud — it's the same binary. The setup script installs Database, the Claude Code CLI and Codex CLI, generates keys, and verifies the toolchain end to end.

  1. 01Clone the repo.
  2. 02Run ./scripts/setup.sh — toolchain, secrets and health check, automatic.
  3. 03Sign in to your AI account once.
  4. 04Start. Locally on localhost:5173, or deploy to your infra.
Get the repo
terminal — bash
git clone https://github.com/Inomy-shop/allen.gitcd allen./scripts/setup.sh# ✓ Node 22 ✓ Database ✓ Claude Code ✓ Codexclaude # sign in oncenpm run build && npm startAPI http://localhost:4000UI http://localhost:5173
MIT licensed · self-hosted

Built in the open.

Read the docs. Fork the workflows. Add your own agents and tools. Self-host the whole thing inside your network — no SaaS dependency, no per-seat fees.

View on GitHub Run it locally