Codevisor

Run coding agents on another machine or build a client on the Codevisor Server API.

Codevisor Server owns projects, worktrees, workspaces, coding-agent sessions, extensions, files, event logs, and terminals on one machine. Codevisor's native clients use the same HTTP, SSE, and WebSocket API documented here.

Experimental API

The /v1 API is public for experimentation, but its compatibility policy is not finalized. Pin the server release you test against and read release notes before upgrading.

Start here

Quickstart

Install a Linux server, pair it, and make your first request.

Authentication

Understand localhost trust and remote bearer tokens.

API concepts

Learn resources, errors, cursors, and idempotent actions.

API reference

Browse the documented HTTP and streaming contract.

Default endpoint

A standalone server listens on 127.0.0.1:49361 unless configured otherwise. The Linux installer binds to 0.0.0.0:49361, enables token authentication, and can install a systemd service.

curl http://127.0.0.1:49361/v1/health

GET /v1/health and GET /v1/discovery are intentionally tokenless. Every other documented route requires a bearer token when called remotely.

Public and internal routes

GET /v1/openapi.json is the allowlist for the documented client API. It includes server, authentication, projects, workspaces, harnesses, plugins, MCP, skills, sessions, files, events, and terminals.

Some first-party transports are intentionally absent: plugin proxy traffic, MCP OAuth callbacks, the MCP gateway, browser-extension sockets and assets, cloud relay routes, and browser automation helpers. A third-party client should not depend on those routes unless a guide explicitly describes the integration.

Overview