AutoJev
Download

Integration · Agents

Connect custom agents and any BYOK client

Not every tool is on AutoJev’s built-in list. Add your own agent executable — AutoJev recognizes Kilo, OpenCode, OpenClaw, Hermes, Grok and Kimi layouts automatically — or copy ready-made connection parameters into any client that accepts a custom API endpoint.

  • Add any local executable as an agent
  • Templates: Kilo, OpenCode, OpenClaw, Hermes, Grok, Kimi
  • Env, JSON and cURL snippets for BYOK clients
  • Client name tags requests in logs
Download AutoJevStar on GitHub

Route every request to the right model.

Connect an agent
Codex
Claude Code
Gemini CLI

AutoJev

autojev/quality
openrouter/anthropic/claude-sonnet
deepseek/deepseek-chat
ollama/qwen3:14b

Providers

4

Models

12

Routes

5

Agents

3

Requests today

1,284

Tokens today

18.6M

Two ways to connect something new

Custom agents are for command-line agents you run locally. You tell AutoJev where the executable lives; if it matches a known configuration layout, AutoJev can connect it with one click and restore it later, exactly like a built-in agent.

Connection parameters are for everything else: editors, scripts, SDKs, chat apps or any tool with a “custom base URL” or BYOK setting. AutoJev shows the base URL, a placeholder key and the model or route ID, with snippets you can copy.

Add a custom agent

Open Agents and click Add agent. The Add local agent dialog asks for:

  1. 1

    Name and icon

    Give the agent a name and, optionally, a PNG, JPEG or WebP image under 2 MB as its icon.

  2. 2

    Executable path

    The path to the binary, for example /path/to/agent. AutoJev runs it directly, never through a shell.

  3. 3

    Configuration file path (optional)

    Leave blank to use the default path for a recognized template, or point to a specific file. The file extension must match the template.

  4. 4

    Launch arguments

    One argument per line. Use {prompt} where the message should go; otherwise it is appended as the last argument.

  5. 5

    Test, save, connect

    Test connection runs the executable with its current configuration (it may consume quota and does not inject gateway settings). Save, then select a model or route in the agent list and click Connect.

Templates AutoJev recognizes

Templates are matched by executable name, or by config file name for Kilo, OpenCode and OpenClaw. Unknown clients stay manually configured — AutoJev never guesses a schema from a file extension alone.

TemplateDefault config pathFormat
Kilo~/.config/kilo/kilo.jsonc (or kilo.json)OpenCode-style provider, JSON/JSONC
OpenCode~/.config/opencode/opencode.jsonJSON/JSONC
OpenClaw~/.openclaw/openclaw.jsonJSON
Hermes~/.hermes/config.yamlYAML, Chat Completions only
Grok~/.grok/config.tomlTOML
Kimi~/.kimi/config.tomlTOML

Custom agents connect over Chat Completions with the selected default model or route; they do not get a multi-model catalog. The placeholder key is autojev-local-<agent id>, so requests are labeled per agent.

Connection parameters for any BYOK client

Click “Connect other clients manually” on the Agents page to open Connection parameters. Pick the API protocol (OpenAI compatible or Anthropic), a model or route, and optionally a client name. AutoJev shows three values — base URL, API key and model — and copyable snippets as environment variables, JSON or cURL.

The key is a placeholder: AutoJev does not check it. Its suffix names the client in Logs and Usage, so “My App” becomes autojev-local-my-app (letters, digits, - and _ are kept). For the Anthropic protocol the base URL has no /v1, because Anthropic clients append /v1/messages themselves.

Environment variable snippets

What Connection parameters produce for a client named “my-app” and the route autojev/fast.

env
# Connection parameters → OpenAI compatible → Environment variables OPENAI_BASE_URL=http://127.0.0.1:9527/v1 OPENAI_API_KEY=autojev-local-my-app # Connection parameters → Anthropic → Environment variables ANTHROPIC_BASE_URL=http://127.0.0.1:9527 ANTHROPIC_API_KEY=autojev-local-my-app ANTHROPIC_MODEL=autojev/fast

Test with cURL

The OpenAI-compatible cURL snippet sends a minimal chat request through the gateway.

cURL
curl http://127.0.0.1:9527/v1/chat/completions \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer autojev-local-my-app' \ -d '{"model":"autojev/fast","messages":[{"role":"user","content":"Hello"}]}'

Restore works the same way

Disconnecting a custom agent, “Stop and restore configurations” and quitting from the tray all restore its config file while keeping non-conflicting edits you made later. Disconnect a custom agent before editing its settings.

Frequently asked questions

Can I use AutoJev with Kilo?

Yes. Add Kilo as a custom agent; AutoJev recognizes the kilo executable or a kilo.json(c) file and writes an OpenCode-style provider pointing at the gateway.

What if my agent isn’t a recognized template?

You can still add it to launch and test it, but AutoJev will not edit its config. Use Connection parameters and paste the base URL, key and model into the agent’s own settings.

Which base URL should a BYOK client use?

http://127.0.0.1:9527/v1 for OpenAI-compatible clients, and http://127.0.0.1:9527 for Anthropic clients. The gateway also accepts POST /v1/responses.

Does the API key need to be real?

No. AutoJev does not authenticate local requests; the autojev-local-<name> key only labels requests. Your real provider keys stay in AutoJev.

What model ID do I put in a client?

A route as autojev/<route-id> (for example autojev/fast) or a single model as <provider>/<model_id>. Connection parameters fills it in for you.

Can I connect Cursor CLI?

AutoJev detects Cursor CLI but cannot connect it, because Cursor CLI does not expose a documented custom model endpoint setting.

Keep exploring

FeaturesOne-click agent setupConnect Codex, Claude Code, Gemini CLI, OpenCode and more. AutoJev edits each native config, backs it up and restores it.IntegrationsOpenCodeAdd AutoJev as an OpenCode provider in one click: every selected model and route appears under the autojev provider.IntegrationsOpenClawAutoJev registers itself as an OpenClaw model provider and sets the primary model, so OpenClaw can use any model you route.FeaturesUsage & request logsTokens, latency and estimated cost for every request, broken down by agent, model and provider. Metadata only, stored locally.

Updated 2026-10-14

Give every agent the right model.

Install AutoJev, add the providers you already pay for, and connect your agents in one click. Everything stays on your machine.

Download AutoJevStar on GitHub

Free & open source · macOS · Windows · Linux