Product Roadmap

What we've shipped and where we're headed. Tap any item for detail.

15
Shipped
9
Planned
v1.11.1
Latest release
Shipped Planned Now

63% of the current roadmap is already shipped.

Q3 2026

Clickable File Path Links

UX

OSC 8 hyperlinks in tool results — click a file path to open it in your editor.

Diff Approval UX

UX

Unified-diff preview with accept / reject / edit-before-apply on every file write. Cluster-B research finding made visible: review is the bottleneck, not generation.

User owns the blast radiusspec 030
Q4 2026

Internal Git Tools — Plumbing

Tools

First-party git tools (status, log, diff, commit, branch, push, rebase, worktree) with explicit permission gating on destructive operations and token-efficient shaped output for small-context models.

User owns the blast radiusspec 031

Small-Model Hardening

Providers

Empirically-tuned edit formats, tool-call fallback prompts, and context compaction defaults for the small open-weight class. Benchmark-driven; results persisted in the capabilities registry.

Small-model usefulnessspec 032

GitHub Forge Tools

Tools

PRs, issues, releases, and CI-status checks as first-party tools. Permission-gated merges. GitHub first; GitLab and Bitbucket follow on demand.

User owns the blast radiusspec 034

Structured Project Memory

Core

Source-controlled, agent-readable project memory with a typed schema for requirements / design / decisions / glossary. AGENTS.md interop included. Memory lives in your repo, not in someone else's cloud.

Executable specificationsspec 035

VS Code Companion

Ecosystem

A thin VS Code extension that launches copair CLI sessions from the editor, passes file context, and surfaces session history. Not an in-editor agent — the CLI remains canonical. Distribution play for the VS Code marketplace audience.

Harness over modelspec 037

Parallel Subagents

Core

Spawn multiple agents in isolated git worktrees, coordinated by a single review surface. Permission inheritance prevents escalation; review gates defend against autonomy maximalism.

Harness over modelspec 036

JetBrains Companion

Ecosystem

A thin JetBrains-platform plugin covering the full IntelliJ IDE family (IDEA, PyCharm, WebStorm, GoLand, Rider, etc.) with the same shape as the VS Code companion: launch CLI sessions, pass file context, session-history sidebar. Single plugin across the whole IDE family.

Harness over modelspec 038
Today — July 2026
v1.11.0

Headless Mode

Core

Run copair non-interactively — a prompt in, a structured JSON result out, no TTY. A binary exit-code contract, a versioned result document and JSONL event stream (both shipped as committed JSON Schema), and config-driven harness toggles for one-at-a-time ablation. The foundation for automated runs and reproducible small-model benchmarking.

Harness over modelspec 047
v1.10.0

Model Capabilities Registry

Providers

A single getCapabilities() contract resolves tier, context window, max output, native tool-call quality, and preferred format for any model — generic logic + sparse shipped data + per-model config overrides, with zero per-model code. Unknown models are declared explicitly (strict, with a clear error) instead of silently guessed; ≤22B models engage the small-model harness. Bundles harness hardening — a result-aware loop guard, tool-call format-error repair, and tool-aware output overflow — plus --explain-model for debugging.

Small-model usefulnessspec 029
v1.8.0

Small-Model Harness

Providers

Built-in tier classifier auto-engages a tuned harness for small open-weight models: ask_user / task_complete tools, max-turn cap, per-turn format reminders. Covers 250+ model families across 22 providers. Empirical per-model tuning + benchmark shipping under spec 032; the harness is operational, not yet battle-tested.

Small-model usefulnessspec 028

Multi-Step Workflows

Core

YAML-defined workflows with sequential and conditional steps, input parameters, loop/retry logic, and progress tracking. Engine validation in progress under spec 033.

v1.4.0

MCP Server Support

Ecosystem

Connect to Model Context Protocol servers for extended capabilities and external tool integration.

Homebrew Distribution

Ecosystem

Install Copair via Homebrew for seamless macOS and Linux setup with automatic updates.

Custom Tool Plugins

Ecosystem

Extensible tool system allowing users to create and share custom tools for domain-specific workflows.

v1.2.0

Ink Terminal UI

UX

Rich terminal rendering with markdown formatting, syntax highlighting, and git diff display.

v1.1.0

Project Init & Knowledge Base

Core

Trust-first project initialisation, per-project config in .copair/, and a structured COPAIR_KNOWLEDGE.md codebase index injected at session start.

Git Workflow Integration

Tools

Automatic branch creation, meaningful commit messages, and diff review built into the agent loop.

Context Persistence

Core

Session history and context are preserved across conversations, enabling long-running workflows.

v1.0.0

Custom Slash Commands

Core

User-defined commands with prompt templates, variable interpolation, and chaining for automating repetitive tasks.

OpenAI-Compatible Endpoints

Providers

Connect to any OpenAI-compatible API: Ollama, vLLM, LM Studio, llama.cpp, and more.

Built-in Developer Tools

Tools

8 tools out of the box: Read, Write, Edit, Grep, Glob, Bash, Git, and WebSearch.

Multi-Provider Support

Providers

Switch between Claude, GPT, Gemini, and local models within the same session using the /model command.

Copair is built and maintained by one indie developer. Quarter estimates assume solo-dev pace and may slip when real life intrudes — we ship when it's right, not when the calendar says we promised.

What makes copair different

Three shipped capabilities you won't find together on any other open-source coding agent. Closest peers named honestly; parity gaps surfaced below.

  1. 01

    A permission system that actually says no

    shipped v1.x

    Structured ask / auto / deny with allowlists. The cross-repo guard is enforced in the tool resolver, not the system prompt — no model can talk its way around it.

    Closest peer: Cline's per-step approval is the closest peer, but it's IDE-bounded and instruction-based. Codex CLI ships OS-level sandboxing, which is adjacent. Copair's guard is structured, terminal-native, and code-enforced.

  2. 02

    Declarative YAML workflows

    shipped v1.8.0

    Author multi-step pipelines with conditional jumps, loops, and on-max-iterations recovery handlers. Check them into your repo alongside your code.

    Honest caveat: Engine validation is in progress under spec 033 — known unknowns exist. Three engine bugs were caught and fixed post-launch in spec 028 Phase C; more are likely.

    Closest peer: Plandex auto-generates plans; Cline's Plan/Act and OpenCode's Plan/Build are agent personalities you toggle. Copair is the only one where you author a YAML pipeline and version-control it.

  3. 03

    Single signed binary install

    shipped v1.6.0

    `brew install copair` works. SEA binaries for macOS, Linux, and Windows. SLSA v1 provenance on every npm release. No Python, no Node toolchain at runtime, no VS Code dependency.

    Closest peer: Codex CLI is also a single-file binary (Rust) but is OpenAI-locked in practice. Aider needs Python; Cline / Roo Code / Continue need VS Code; OpenCode runs a daemon. Copair is the only fully model-agnostic agent with this distribution profile.

Where copair still trails

  • Diff-approval UX Cline (per-step approval) and Plandex (cumulative diff sandbox) are ahead. Closes in spec 030.
  • Subagent orchestration Codex CLI (first-party subagents) and Roo Code (multi-mode agents) are ahead. Closes in spec 036.

Last updated July 1, 2026