Meridian

Quick start · Try Antigravity · Desktop · Documentation · Discord

Meridian connects coding clients to Claude and Antigravity using your subscription. Run Pi, OpenCode or another supported client against a local API, and manage providers, requests and usage from a browser or the optional Mac app.

Claude requests run through Anthropic’s Agent SDK. Antigravity requests run through Google’s official, signed-in agy CLI. Account permissions, model availability and subscription limits still apply.

Claude	Antigravity
Released · Claude Agent SDK	Preview · v1.74.0+ · Official agy CLI
Persistent sessions, prompt caching and multiple account profiles	Streaming, client tools, conversation reuse and saved-answer recovery
Client compatibility and setup	Pi and OpenCode setup
Headless macOS, Linux and Windows	Authenticated acceptance on macOS arm64; Linux/Windows verification unfinished

Quick start

For the released Claude backend, install Node.js 22+, then:

npm install -g @rynfar/meridian
claude login
meridian

Open http://127.0.0.1:3456. For OpenCode V1, run meridian setup and restart OpenCode. For Pi and other clients, follow the client setup guide. See configuration for API-key protection and Windows setup, or deployment for Docker and Nix.

Try Antigravity

Antigravity is included in Meridian 1.74.0 and later as a preview. The verified setup uses agy 1.2.7, Pi 0.72.1 or OpenCode V1 1.18.31, and macOS on Apple Silicon. Other versions need their own verification.

Install Node.js 22+ and the official Antigravity CLI. Run agy to sign in with your subscription account and disable paid overage credits in its settings. Then install Meridian:

npm install -g @rynfar/meridian@1.74.0

MERIDIAN_BACKEND=antigravity \
MERIDIAN_AGY_ALLOW_TOOL_BRIDGE=1 \
MERIDIAN_AGY_STATE_PATH="$HOME/.local/state/meridian/antigravity.sqlite" \
MERIDIAN_PORT=3457 \
meridian

Open http://127.0.0.1:3457/providers and use Connect Pi / OpenCode, or follow the CLI setup instructions. For a source build, follow the development guide. The tool bridge lets the client execute tools with its own permissions. The SQLite path enables saved state across service restarts; it does not guarantee recovery of an unfinished action.

What works

• The coding loop: incremental text, client tools, parallel tool batches, approvals, questions, cancellation and client-owned plugins/delegation.
• Model and output selection: available model/effort variants, forced tools and validated structured output.
• Client APIs: Anthropic Messages, OpenAI Chat Completions and a documented Responses subset.
• Attachments: images and public HTTPS image URLs; documents, speech and video through local conversion. These are not native media APIs.
• Continuity: warm conversation reuse, eligible completed-session restoration, history replay and bounded recovery of saved answers and tool IDs.
• Provider management: web and macOS setup, separate quota/status displays, shared navigation and activity. Native browser/subagent access requires separate explicit grants.

What is unfinished