Feature · Agent setup

Connect Claude Code, Codex and other agents to any model in one click

AutoJev detects the coding agents on your machine, writes the gateway settings into each one's native config file, and puts the original back when you disconnect. No hand-edited TOML, no lost settings.

Edits each agent's native config
Backup on connect, restore on disconnect
Pick several models and routes per agent
Reconnects automatically on next launch

Download AutoJev Star on GitHub

Agents

+ Agent

CodexResponses

~/.codex/config.toml

Connected

Claude CodeMessages

~/.claude/settings.json

Connected

Gemini CLIGemini

~/.gemini/settings.json

Connected

OpenCodeChat

~/.config/opencode/opencode.json

Connect

The problem with wiring agents by hand

Every coding agent stores its model endpoint differently. Codex wants a provider table in config.toml. Claude Code reads ANTHROPIC_BASE_URL from settings.json. Gemini CLI splits settings across a JSON file and a .env. Switching models means editing each one, remembering what you changed, and undoing it later.

AutoJev turns that into a toggle. Open Agents, select the models or routes an agent should see, and click Connect. AutoJev writes the minimum set of fields to point the agent at http://127.0.0.1:9527, records what it injected, and keeps a byte-for-byte backup of the original file.

Supported agents and what AutoJev edits

Paths are defaults; supported environment overrides take precedence. Detection alone never changes a file — only Connect does.

Agent	Config file	Protocol to AutoJev
Codex	~/.codex/config.toml (+ ~/.codex/autojev-models.json)	OpenAI Responses
Claude Code	~/.claude/settings.json	Anthropic Messages
Gemini CLI	~/.gemini/settings.json + .env	Gemini bridge
OpenCode	~/.config/opencode/opencode.json(c)	Chat or Messages
Hermes	~/.hermes/config.yaml	Chat Completions
OpenClaw	~/.openclaw/openclaw.json	Chat or Messages
Kimi Code CLI	~/.kimi-code/config.toml (or ~/.kimi/config.toml)	Chat or Messages
Grok Build	~/.grok/config.toml	Chat or Messages
OMP (oh-my-pi)	~/.omp/agent/models.yml + config.yml	Chat or Messages
Cursor CLI	~/.cursor/cli-config.json	Detection only

Cursor CLI does not expose a documented custom model endpoint setting, so AutoJev only detects it and does not route its requests.

What a Codex connection looks like

For Codex, AutoJev adds an autojev provider that speaks the Responses API and a model catalog so your routes appear in Codex's model picker. Trimmed for readability:

~/.codex/config.toml

model = "autojev/fast"
model_provider = "autojev"
model_catalog_json = "~/.codex/autojev-models.json"
 
[model_providers.autojev]
name = "AutoJev"
base_url = "http://127.0.0.1:9527/v1"
wire_api = "responses"

And a Claude Code connection

Claude Code gets its base URL and model through the env block in settings.json. Your other settings stay where they are.

~/.claude/settings.json (excerpt)

{
  "model": "autojev/quality",
  "env": {
    "ANTHROPIC_BASE_URL": "http://127.0.0.1:9527",
    "ANTHROPIC_AUTH_TOKEN": "autojev-local-claude",
    "ANTHROPIC_MODEL": "autojev/quality"
  }
}

Built to leave your config the way it was

Backup on connect

The original file is backed up once, before the first change, and kept across repeated connections. Files that did not exist are removed again on restore.

Restore that respects your edits

On disconnect, AutoJev reverts only the fields it injected and you haven't changed since. Later, non-conflicting edits you made while connected are kept.

Several models per agent

Select multiple models and routes for one agent; where the client supports a model picker, they all show up. Batch-update every connected agent at once.

Safe stop and quit

"Stop and restore configurations" and "Quit AutoJev (restore agents)" put configs back before the gateway shuts down. On next launch, agents reconnect according to your saved preferences.

Connect an agent in under a minute

1
Open the Agents page
AutoJev lists detected agents with their config paths and connection status.
2
Choose models or routes
Select one or more entries such as autojev/fast and autojev/quality. The first becomes the default.
3
Click Connect
AutoJev validates the config, backs it up and writes the gateway settings. Restart a running agent if it caches its config in memory.
4
Disconnect any time
Disconnecting restores the original configuration. Manually disconnected agents stay disconnected on the next launch.

Using an agent that isn't listed?

Add it as a custom agent: point AutoJev at the executable, add launch arguments and an optional config path. Templates are recognised for Kilo, OpenCode, OpenClaw, Hermes, Grok and Kimi. For any other BYOK client, the Connection parameters dialog gives you a base URL, placeholder key and copyable env, JSON or cURL snippets.

Frequently asked questions

How do I connect Claude Code to a non-Anthropic model?

Add the provider and model in AutoJev, then connect Claude Code from the Agents page. AutoJev sets ANTHROPIC_BASE_URL and ANTHROPIC_MODEL in ~/.claude/settings.json and converts Claude Code's Messages requests to whatever API the upstream model speaks.

Can Codex use models that only support Chat Completions?

Yes. Codex talks to AutoJev over the Responses API, and AutoJev translates requests, tool calls and streaming events to and from Chat Completions or Anthropic Messages as needed.

Will AutoJev overwrite my existing agent settings?

It only writes the fields needed to reach the gateway and keeps a backup of the original file. On restore it reverts just those fields, preserving later edits that don't conflict. Comments in TOML, YAML or JSON5 may be reformatted while connected; an untouched file is restored to its original bytes.

What happens if I quit AutoJev while agents are connected?

Quitting from the tray restores agent configurations first, so your agents go back to their original providers. On the next launch AutoJev reconnects them according to your saved preferences.

Does AutoJev support Cursor?

Cursor CLI is detected but not connected, because it has no documented setting for a custom model endpoint.