blerg

Run any coding agent. Never lose a session.

Free, open-source. Blerg runs your coding agents, Claude Code, Codex, Hermes, or OpenCode, on any machine you own, against any model, and gives them an agent-first board to work from. Start with prompts. Scale to tickets. Never lose a session.

Get the code on GitHub Install in one command

Apache-2.0. Bring your own harness and model. No hosted service, no account.

sessions 3 running, 1 idle
  1. api-ratelimit claude code sandbox running
  2. gallery-upload-fix codex desktop running
  3. alert-rule-writer hermes cluster pod running
  4. blog-import opencode desktop idlerecovered after reboot
Open any row for the live terminal, from a laptop or a phone.

You have probably been here.

  1. One terminal

    One agent, one prompt, and you watching it.

  2. Several terminals

    Tabs everywhere. Which one just asked you a question?

  3. tmux, or the harness's own sub-agents

    More in flight, still tied to one machine and one screen. Close the lid and it is gone.

  4. Blerg

    Every session on every machine in one list, from any device, back after a reboot. And a board for when prompts stop scaling.

Two ways to work. One platform.

Keep prompting the way you do today, only with fewer limits. When a project outgrows a single prompt, move to tickets. Both run on the same install.

Prompt-driven sessions

What you do now, made more useful.

  • Any harness, any model, local or cloud
  • Resume a session on another machine, or after a reboot
  • Watch and answer from your phone
  • One laptop today, a cluster when you need it

Ticket-driven engineering

For when the work outgrows one prompt.

  • An agent-first kanban board, shipped in the box
  • Tickets designed for agents to write and read, not just humans
  • An admission gate that rejects duplicates and vague cards
  • Dispatch a card straight into a session, review the result on the card

Runner

Launches sessions in the harness you pick, keeps them alive, shows them in any browser, and brings them back after a restart.

Board

The agent-first kanban board. Agents file cards over MCP or a CLI, the gate curates, humans review and dispatch.

Core

A small control plane: identity, projects, discovery, audit. Every service publishes its docs at /agents.

Any scale. Same three services.

The runner, board, and core are the same binaries whether one person runs them on a laptop or a team runs them across a cluster. Start small, move up a tier when you outgrow it, keep your sessions.

  1. A few sessions

    Desktop

    Docker Compose and a host daemon, on the machine you already work on.

    • Windows
    • Linux
    • macOS

  2. Dozens of sessions

    All your computers

    A daemon on the desktop, the laptop, and the box under the desk. Each one dials in, and every session lands in the same list no matter where it runs.

  3. Isolated sessions

    Containers

    A throwaway container per session, with only that repo mounted and only that project's secrets injected.

  4. Hundreds of sessions

    Kubernetes

    One pod per session on any cluster: MicroK8s, k3s, kubeadm, or the one your team already runs.

Why it works this way

Choices that survived running agents on a real homelab, not a demo.

Works while you are away
Over Tailscale or any VPN, nothing exposed. Watch a session, answer its question, or dispatch a card from your phone.
Your accounts, hardware, and model
Your existing harness logins. Models on your own GPUs or any cloud provider. No proxy in the middle.
Volume without noise
Agents file hundreds of cards a day. The gate rejects duplicates and vague ones, so humans only curate.
Harness-agnostic on purpose
Harness choice is per project. A new harness is a driver, not a rewrite. No GPU required.
Agent-first docs
Every service publishes its docs at /agents, written for an agent to act on. Onboarding is a URL.
Isolation when you want it
On the host, in a throwaway container, or in a pod. Only that repo mounted, only that project's secrets.

Supported today

Harnesses

  • Claude Code
  • OpenAI Codex
  • Hermes Agent

Runtimes and infrastructure

  • tmuxhost sessions
  • Dockerlocal sandbox
  • Kubernetescluster pods
  • Postgres

Integrations

  • GitHub
  • MCPagent access to the board
  • Tailscalereach it from anywhere

More harnesses (OpenCode, OpenClaw, NemoClaw) and forges are on the way. A harness is a driver, not a rewrite.

Install

You need Docker, tmux, and at least one harness CLI installed and logged in, such as Claude Code, Codex, or Hermes. The script generates secrets on first run, builds the images, and starts the host daemon as a service. 

# desktop
git clone https://github.com/blerglab/blerg-ai.git
cd blerg-ai/install/desktop
./blerg-up.sh

# homelab or cluster
cd blerg-ai/install/k8s
cp .env.example .env    # registry, tag, domain
./deploy.sh

When it finishes, the landing page opens at localhost:8081 with the board and runner listed as tiles. Launch a session on a repo, or create a card and dispatch it, and watch it run from any device.

Read the source Full setup guide