abegma/nautelle-api repository overview

One place to see, steer, approve and pay for every AI coding agent you run.

Nautelle, formerly AgentDock.

Documentation⁠ · Install⁠ · Concepts⁠ · Wiki⁠ · Website⁠

Nautelle is a self-hosted control plane for Claude Code agent fleets. You describe work in one sentence. Nautelle interviews you, turns the answer into cards, can draw a design for them and runs a dedicated agent per card on your own machines. Each agent opens a pull request and fixes its own CI. You stay in charge of what merges, what it costs and what an agent may do — from the browser, from Telegram or from the terminal you already use.

It works alongside the Code Sentinel⁠ orchestrator, and GitHub issues and pull requests stay the source of truth.

⁠Quick start

To try it, one container is enough:

docker run -p 8000:8000 -v nautelle:/data abegma/nautelle

It runs a demo PostgreSQL and Redis inside, so it is not for production. Open the setup link it prints to create the first administrator. The install guide⁠ has the details.

To install it for real, on a Linux host with Docker:

curl -fsSL https://raw.githubusercontent.com/AndreyBegma/Nautelle/main/deploy/compose/install.sh | sh

1. Run the command above. It writes a Docker Compose stack into ./nautelle and starts it.
2. Open http://localhost:8000⁠.
3. Create the first administrator on the setup page.

The images are on ghcr.io (ghcr.io/andreybegma/nautelle-*, the default) and on Docker Hub as abegma/nautelle-api, abegma/nautelle-web and abegma/nautelle, with the same digests and signatures. Add --registry docker.io/abegma to pull them from Docker Hub.

Then pair a runner on the machine that holds your repositories, with a code from Admin › Runners › Add runner:

brew install andreybegma/tap/nautelle-runner      # or: npm i -g nautelle-runner
nautelle-runner pair --server http://localhost:8000/api --code XXXX-XXXX --allow-root ~/dev
nautelle-runner install-service

--tunnel-token puts the install behind a Cloudflare tunnel and --domain serves your own domain with automatic HTTPS. The install guide⁠ covers the three modes, the requirements⁠, upgrades⁠ and backups⁠.

On Kubernetes, the Helm chart runs the control plane; runners stay on the developer machines:

helm install nautelle oci://ghcr.io/andreybegma/charts/nautelle --version X.Y.Z \
  -n nautelle --create-namespace

Values, Ingress, external databases and backups are in Kubernetes (Helm)⁠.

⁠Features

⁠How it works

flowchart LR
  people["Browser · Telegram · terminal"] --> cp
  subgraph cp["Control plane — your server"]
    web["Web<br/>Next.js"] --> api["API<br/>NestJS"]
    api --> pg[("PostgreSQL")]
    api --> redis[("Redis")]
  end
  subgraph machine["Each of your machines"]
    runner["nautelle-runner"] --> agents["Claude Code<br/>(Codex: sessions listed)"]
    agents --> repo["worktrees · tmux · gh"]
  end
  runner -- "outbound WebSocket<br/>events up · typed commands down" --> api
  repo -- "pull requests" --> github[("GitHub")]

• The control plane never reads a project's filesystem. A runner on each machine does, and it dials out, so the machine needs no open port (ADR-0001⁠).
• The runner runs typed commands from an allowlist and refuses anything outside the folders you allowed, under a local policy the server cannot change (ADR-0010⁠, ADR-0047⁠).
• Code and credentials stay on your machines. Claude Code and GitHub credentials never reach the server.

A card goes from an idea to a merged pull request like this:

flowchart LR
  idea(["One sentence<br/>web · Telegram · assistant"]) --> intake["Interview<br/>one card · split · stack"]
  intake --> todo["To Do<br/>you accept candidates"]
  todo --> design{"Needs a<br/>design?"}
  design -- yes --> mock["Mockups<br/>pin · revise · approve"] --> run
  design -- no --> run["Run<br/>own worktree + Claude session"]
  run --> pr["Draft PR<br/>→ ready on finish"]
  pr --> ci{"CI"}
  ci -- red --> fix["Fix round<br/>(up to 3)"] --> ci
  ci -- green --> merge["Auto-merge<br/>or your Accept"]
  merge --> done(["Completed<br/>worktree cleaned up"])

⁠Documentation

⁠Contributing

Pull requests target develop. Read CONTRIBUTING.md⁠ and CLAUDE.md⁠ for the conventions; help is in SUPPORT.md⁠, vulnerabilities go through SECURITY.md⁠. An architectural change records a new ADR in the same pull request.

To work on Nautelle itself you need Bun⁠ 1.4.0+, Node.js 24+ and Docker:

git clone https://github.com/AndreyBegma/Nautelle && cd Nautelle
bun install
cp apps/web/.env.example apps/web/.env

bun run db:setup       # docker/.env + apps/api/.env with generated passwords, PostgreSQL 127.0.0.1:5421, Redis 127.0.0.1:6421, migrations, seed
bun run admin:create   # the first admin
bun run start:dev      # API http://localhost:8180 · web http://localhost:3517
bun run docs:dev       # the documentation site at http://localhost:4321/Nautelle/

Pair a development runner with --server http://localhost:8180.

⁠License

MIT⁠