The bridge layer
CODENCER

The bridge between AI planners
and coding executors.

Open-source bridge. Local-first execution. Durable run record across any planner and any executor.

v0.2.0-beta · Apache 2.0 · ★ 2 · CI green · last release 2 days ago

What Codencer is

Bridge, not brain. State, not chat.

Codencer is an open-source orchestration bridge that lets any AI planner — ChatGPT, Claude, Gemini, a human lead — dispatch real work to any AI coding executor — Codex, Claude Code, Antigravity, OpenClaw, Qwen — and produces a durable, auditable record of what happened.

We are not a coding agent. We do not run inference. We do not host the LLM. We sit between the planner and the executor as state, contract, and audit trail. Planning stays where it works best. Execution stays near the code. Codencer holds the part that doesn't exist anywhere else: the durable record across a heterogeneous fleet.

PlannerChatGPTClaudeGeminihuman
Codencerrunsstepsattemptsartifactsvalidationsgates
ExecutorCodexClaude CodeAntigravityOpenClawQwen
Bridge, not brain. State, not chat.
What this is, what this isn't

The neutral cross-vendor bridge
is still missing.

Vendors are deepening their own stacks — ChatGPT to Codex, Claude Desktop to Claude Code, Cursor to Cursor. Codencer is the bridge across all of them.

ProductPlannerExecutorCross-vendorDurable recordLocal execSelf-host
Codenceranyany
ChatGPT → CodexOpenAIOpenAIchat only
Claude → CCAnthropicAnthropictool calls onlypartial
Cursor self-hostedCursorCursorpartial
Copilot cloudGitHubGitHubpartial
DIY MCP glueanyanypartialyou build itvariesvaries

Vendors are deepening their own stacks. The neutral cross-vendor bridge is still missing.

How it works

Three roles. Two contracts. One record.

01

Plan in any chat

ChatGPT, Claude, Gemini, a human lead. The planner sends a structured TaskSpec to Codencer.

02

Local executor runs

Codencer dispatches the step to Codex, Claude Code, Antigravity, Qwen, or OpenClaw. Code stays on your machine.

03

Validations + gates close the run

Artifacts captured, validations run, gates evaluated, ResultSpec returned. The planner reads the result.

What exists today

v0.2.0-beta on GitHub.

  • Five beta tracks verifiedlocal daemon + CLI · self-host relay + connector · self-host cloud · planner-clients · provider connectors
  • Executor adapters liveCodex · Claude Code · Antigravity · Qwen — plus OpenClaw experimental
  • Durable state modelruns · steps · attempts · artifacts · validations · gates — SQLite-backed, worktree-isolated
  • Cross-platform CI greenmacOS · Windows · WSL/Linux at the v0.2.0-beta tag
  • Documentation discipline5,200+ lines across 30+ docs — every claim labeled proven, partial, compatibility-only, or deferred
  • Hardened by daily useThe founder runs Codencer every day across Mac, Windows, WSL/Linux, and remote VPS
Get involved

Three ways to start.

01

Install the OSS


v0.2.0-beta is public on GitHub. Apache 2.0. Self-host on any platform.

02

The hosted version


Self-host today. A hosted Codencer launches July 2026 — one email when it opens, nothing before, nothing after.

03

Read the docs


5,200+ lines covering every executor adapter, the state model, and the truth model.