OpenVibe.Codes · the open coding-agent harness · alpha

Code with any agent

One open harness for Claude Code, Codex, OpenCode, Command Code, Aider, the DeepSeek API and models you host yourself: send a coding task to the agent that fits it, hand it over when one gets stuck, and keep the whole run in one place. Then point it at OpenVibe itself.

Open source (AGPL-3.0). Version 0.3.1 runs on your machine with the agents and keys you already have, from your terminal or started from this site in any browser; the list below says exactly what works.

# an example run: one agent hits its limit, the next one finishes
$ openvibe-codes run "add a test for the date parser"
run run_20261008… · ~/my-project
▶ codex · session 0199…
! You have hit your usage limit.
⇢ handing over from codex: You have hit your usage limit.
▶ claude-code · session 4f2e…
  → Read src/date.js
  → Edit test/date.test.js
Added test/date.test.js: three cases, all pass.
✔ done (48 s · $0.0400 · 31k in / 1.2k out)

The agents

8 harnesses in the catalog, each with the models it runs. Routing picks one by what the task needs first, then by cost.

How a task finds its agent

  1. Describe the taskOne of edit, review, long, resume, plus anything it must have: a capability, a runtime, a ceiling on cost.
  2. Hard limits firstAn agent that lacks a required capability is out, whatever it costs. Each refusal says why.
  3. Then the cheapest fitAlready-paid capacity and free allowances first, then price per token, through the same placement engine every OpenVibe service uses.
  4. Hand-offsWhen an agent fails, hits its usage limit or goes quiet, the task moves to the next one with a note: the task, the files touched and the state of the tree.

Start in a minute

The harness runs on your machine with the agent CLIs and keys you already have. The router is public: ask it which agent fits a task, no key needed.

Install and run
npm install -g https://codeload.github.com/OpenVibers/OpenVibe.Codes/tar.gz/refs/tags/v0.3.1
openvibe-codes agents                 # which agents this machine can run
cd my-project
openvibe-codes run "add a test for the date parser"
openvibe-codes run --permission read "where is the session cookie set?"
openvibe-codes runs                   # every run, kept to show or resume
Ask the router (public API)
curl -s https://openvibe.codes/api/v1/harnesses/route \
  -H 'Content-Type: application/json' -d '{ "task": "review" }'
# → { "selected": "claude-code:claude-code-sonnet",
#     "reasons": [ "no marginal cost (already-paid capacity or a free allowance)", … ],
#     "candidates": [ … every agent, with why it was or was not picked ] }

OpenVibe Git

52 repositories on OpenVibe's own code forge at git.openvibe.codes: browse, clone over HTTPS and sign in with your OpenVibe account, in the network's theme. The repositories are mirrored from GitHub every hour; GitHub stays the home of each one until it moves here.

git clone https://git.openvibe.codes/OpenVibers/OpenVibe.Codes.git

All OpenVibers repositories · Sign in with OpenVibe

Improve OpenVibe

OpenVibe is built in the open, 38 services and their shared libraries, every one on GitHub. Pick a repository, describe the change, and send a pull request; the harness's job is to make that one step.

Start contributing Read the guide

What works today

PieceState
The harness on your machine (openvibe-codes)Live, 0.3.1: runs a task on any of the seven agents with your CLIs and keys, streams one event format, keeps every run to show or resume.
Hand-offs between agentsLive: a failed, rate-limited or silent agent hands the task to the next one with a note on what was done.
Run on your machine: start a task in any browser, your phone included; your own computer runs itLive: add your machine on openvibe.bot/machines (one command), then watch the task live here and get the patch, a branch or a pull request. It runs only on your own machines, in the Node's job sandbox.
The agent catalogLive: every harness and model with its capabilities, prices and limits.
GET /api/v1/harnesses, POST /api/v1/harnesses/routeLive: public, no key needed; per-address and per-caller limits.
Improve OpenVibe: a repository, a change on a branch with its test, a pull request that CI checks and a maintainer reviewsLive: by hand, or with the harness doing the change on your machine.
OpenVibe Git: OpenVibe's own code forgeLive: every public OpenVibe repository, mirrored from GitHub hourly, with OpenVibe sign-in and HTTPS cloning. GitHub stays canonical until a repository moves here.

Questions people ask

What is OpenVibe.Codes?

An open harness for coding agents: it runs Claude Code, Codex, OpenCode, Command Code and DeepSeek-backed agents on your tasks, with hand-offs between them and a review by a second model.

Can it run on my own machine?

Yes. With OpenVibe.Run and the OpenVibe node on your computer, a task can run on your own hardware instead of a server.

Where is the code?

On GitHub under OpenVibers, open source like the rest of OpenVibe, with read mirrors on OpenVibe Git at git.openvibe.codes.

Does it cost anything?

The harness is free and open source. Each agent runs with your own CLI and keys, so you pay its provider as you already do; the router prefers capacity you have already paid for and free allowances.

What happens when an agent gets stuck?

A failed, rate-limited or silent agent is stopped and the task goes to the next one with a note: the task, why the last agent stopped, the files it changed and the state of the tree.

What is OpenVibe Git?

OpenVibe's own code forge at git.openvibe.codes, where you sign in with your OpenVibe account. It holds every public OpenVibe repository, mirrored from GitHub every hour.

Part of OpenVibe

One account across every OpenVibe site. Related places to go next:

Building an app instead?

Projects, keys, grants and the API docs of every OpenVibe service live on OpenVibe.Services.