Skip to main content

overcode

A TUI supervisor for managing multiple coding agents (Claude Code, opencode, opencode2, Codex, Grok, Hermes) in tmux.

Launch autonomous coding agents, monitor their progress in real-time, track costs and activity, and coordinate work across your projects—all from a single dashboard.

Why overcode?

Running multiple coding agents is powerful, but managing them gets chaotic fast. Overcode solves this by giving you:

  • Unified visibility - See all agents at a glance: what they're working on, whether they need input, and how much they're costing you
  • Native tmux integration - A split layout with your dashboard on top and the focused agent's live terminal below—full speed, full color, full scrollback
  • Smart orchestration - An optional supervisor daemon can approve prompts and keep agents moving without constant attention
  • Multi-machine monitoring - Sister integration aggregates agents from multiple machines into one view
  • Session persistence - Agents run in tmux, surviving terminal disconnects. Pick up where you left off

Screenshot

Tmux split layout — Monitor all agents in the top pane. The bottom pane shows the selected agent's live terminal. Navigate with j/k and the bottom pane follows. Press Tab to switch focus between panes.

Overcode v0.3.0 tmux split layout

Quick Start

Try it instantly with uvx:

uvx overcode monitor

This opens the standalone dashboard. Press n to create your first agent.

For the full tmux-native experience (recommended):

pip install overcode
overcode tmux

This creates a split layout: the overcode dashboard on top, the focused agent's live terminal on the bottom. Navigate agents with j/k — the bottom pane follows automatically. Press Tab to toggle focus between panes.

Requirements: Python 3.12+, tmux, and an agent CLI — Claude Code, opencode (v1, or the opencode2 2.0 preview), Codex CLI, Grok Build, or Hermes Agent

See the Getting Started Guide for a complete walkthrough.

Features

Tmux Split Layout (overcode tmux)

The recommended way to use overcode. Creates a two-pane layout in tmux:

  • Top pane: Compact agent dashboard with live status
  • Bottom pane: The focused agent's native terminal — no emulation, real tmux
  • j/k navigates agents, bottom pane follows
  • Tab toggles focus between dashboard and terminal
  • Option+J/K navigates agents from the terminal pane
  • PageUp/Down and mouse scroll work in the bottom pane

Real-time Dashboard

The TUI displays all agents with live status updates, showing:

  • Current activity and AI-generated summaries
  • Status indicators (running/waiting/stalled)
  • Cost and token usage per agent
  • Git repo and branch information
  • Timeline showing status history

Agent Management

  • Launch agents with custom prompts and permission settings
  • Send instructions directly from the dashboard
  • Standing orders - persistent instructions that guide agent behavior
  • Agent hierarchy - parent/child delegation with follow mode and reporting
  • Cost budgets - per-agent spending limits with automatic enforcement
  • Sleep mode - pause agents and exclude them from stats

Supervisor Daemon

An optional Claude-powered orchestrator that:

  • Monitors agents for prompts requiring approval
  • Automatically handles routine confirmations
  • Follows per-agent standing orders
  • Tracks interventions and steering decisions

Wrappers

Run agents in custom environments — containers, VMs, or any setup your project needs:

  • Devcontainer wrapper - Launch agents inside Docker containers with a single flag
  • Auto-install - Bundled wrappers install themselves on first use
  • Customisable - Write your own wrapper script or modify the bundled ones
  • Set per-agent (--wrapper devcontainer) or as default in config

See the Wrappers Guide for setup and customisation.

Agent Backends

Overcode is not Claude-Code-only. It supports six agent CLIs today: Claude Code, opencode, the opencode2 2.0 preview, Codex, Grok, and Hermes. Launch a non-default one with overcode launch -n my-agent --backend opencode (or opencode2 / codex / grok / hermes) and it appears in the same dashboard with live hook-grade status, previews, AI summaries, send-instruction, restart, kill, resume, and token/cost/context columns (fork where the CLI has one — opencode2's preview TUI has no --fork, Hermes only branches in-session). Backends declare their capabilities, so the Claude-only subsystems — skills, the sandbox badge, the subscription-usage widget, agent teams — are hidden rather than shown as misleading zeros. A backend badge column appears only when your fleet actually mixes backends, so a Claude-only setup looks exactly as it did. See the Backends Guide for the full support matrix, flag mapping, and current limitations.

Sister Integration

Aggregate agents from multiple machines into one dashboard:

  • Configure sister machines in ~/.overcode/config.yaml
  • Remote agents appear alongside local ones
  • In tmux split mode, selecting a sister agent auto-zooms the dashboard with a preview pane

Analytics & Export

  • Web dashboard - mobile-friendly monitoring from any device
  • Historical analytics - browse session history with charts
  • Parquet export - analyze data in Jupyter notebooks
  • Presence tracking - correlate activity with your availability

TUI Controls

Key Action
j/k or ↑/↓ Navigate agents
Tab Toggle dashboard/terminal focus (tmux split)
Enter Approve/send Enter to agent
i or : Send instruction
n Create new agent
x Kill agent (double-press)
b Jump to next agent needing attention
h or ? Show all shortcuts
q Quit (or detach in tmux split)

See the TUI Guide for all keyboard shortcuts.

Documentation

Testing

Unit tests run on the host (make test-unit). End-to-end tests run inside a disposable Docker container so daemons, tmux servers and (mock or real) Claude processes can never leak onto your machine:

make e2e         # workflow + visual tiers (mock Claude, no credentials)
make e2e-real    # real-LLM smoke tier (needs CLAUDE_CODE_OAUTH_TOKEN)
make e2e-shell   # debug shell inside the test container

See docs/design/e2e-devcontainer-testing.md for the architecture, coverage matrix, and CI setup.

License

MIT

Metadata

Release files for overcode 0.5.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for overcode 0.5.3
File Size Uploaded Provenance Actions
overcode-0.5.3.tar.gz 667.6 kB With provenance Details for overcode-0.5.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for overcode 0.5.3
File Interpreter ABI Platform Actions
overcode-0.5.3-py3-none-any.whl Python 3 none any Details for overcode-0.5.3-py3-none-any.whl

Total release size: 1.4 MB

Release files / overcode-0.5.3.tar.gz

Download URL overcode-0.5.3.tar.gz
Size 667.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b7d865a4d701dc3867f523aabfd021cf0a3e22df82903ae7d49d10f3f4eef0ef
BLAKE2b-256 checksum
How to use checksums
130a6a099fef5644bf76613bb0277208b8c718c704bb886dd4da9f67d080b781
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

Release files / overcode-0.5.3-py3-none-any.whl

Download URL overcode-0.5.3-py3-none-any.whl
Size 739.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e29b0d3c48bc737457688efadde9dda07cac13c2d33c52fd0a0736f7633eaee4
BLAKE2b-256 checksum
How to use checksums
26a7437f0d75ccb0e08138bec765ca97537e9946f5a82c6203bb8dde08714552
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

Security for overcode 0.5.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for overcode-0.5.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.5.3 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page