Use eb1 with Omnigent

Omnigent is an open-source coding agent that supports custom gateways in its own configuration file. Registering Keiro there runs Omnigent's agents on the public eb1 models. There is nothing to install from Keiro, and no fork or local proxy is involved.

On this page 1 of 7

Before you configure#

  1. Install Omnigent with curl -fsSL https://omnigent.ai/install.sh | sh. Omnigent's install page lists what it needs (Python 3.12 or newer, Node.js 22 with npm, and tmux) and other ways to install it.
  2. Open API keys.
  3. Create a dedicated key for this Omnigent installation.
  4. Keep the newly revealed secret available in your password manager until setup is complete.

A dedicated key lets you inspect and revoke Omnigent traffic independently from production application traffic.

Configure#

Omnigent reads providers from ~/.omnigent/config.yaml. The commands below add the Keiro entry. They are safe to run again. If the file already has a keiro entry, they say so and change nothing. If it has other providers but no keiro entry, they print a message, change nothing, and you add the entry by hand as described below.

Run in the terminal Shell
(
  umask 077
  KEIRO_BASE_URL=https://api.keirolabs.ai/v1
  mkdir -p ~/.omnigent
  if grep -q '^  keiro:' ~/.omnigent/config.yaml 2>/dev/null; then
    echo "config.yaml already has a keiro entry; nothing was changed."
  elif grep -q '^providers:' ~/.omnigent/config.yaml 2>/dev/null; then
    echo "config.yaml has other providers; add the keiro entry by hand." >&2
  else
    cat >> ~/.omnigent/config.yaml <<EOF
providers:
  keiro:
    kind: gateway
    default: true
    anthropic:
      base_url: ${KEIRO_BASE_URL%/v1}
      api_key: <api-key>
      models:
        default: eb1-preview
    openai:
      base_url: ${KEIRO_BASE_URL}
      wire_api: responses
      api_key: <api-key>
      models:
        default: eb1-preview
EOF
  fi
  chmod 600 ~/.omnigent/config.yaml
)

The parentheses run the commands in a subshell, so umask 077 does not stay set in your shell. It makes a new file owner-only from the moment it exists; chmod 600 covers a file that existed before.

If the commands printed the message about other providers, open ~/.omnigent/config.yaml and copy the entry by hand: put the lines from keiro: to the last default: eb1-preview under your existing providers: line, indented by two spaces, as in the block above.

Open ~/.omnigent/config.yaml in your editor and replace both <api-key> values with the key you created. Do not paste the key into a terminal command, which would save it in shell history.

With this setup, the key is stored in this file as plain text. Unlike the Codex and Claude Code setups, the key is not in a keychain or in a file of its own. Use a dedicated key for Omnigent, keep the file owner-only, and revoke that key in the console if the machine is shared or lost.

default: true makes Keiro the default provider for both families in the entry. New Omnigent sessions for Claude Code, Codex, and Pi then use Keiro unless you choose another provider. To keep your current default, delete the default: true line. You can change the default later with omni setup.

The two family entries are deliberate and differ in one detail each:

  • The anthropic family takes the API root without the /v1 suffix. Omnigent appends request paths itself, so a base URL that already ends in /v1 produces 404s on this family.
  • The openai family takes the /v1 base URL and requires wire_api: responses. Without it, Omnigent's codex integration cannot talk to Keiro.

Each family needs its own models.default; eb1-preview is the recommended default for both.

Check the setup. This command prints 0 once you have replaced both <api-key> values:

Run in the terminal Shell
grep -c '<api-key>' ~/.omnigent/config.yaml

Then list Omnigent's providers. The keiro gateway appears under Claude, Codex, and Pi:

Run in the terminal Shell
omni config list

A 401 error in a session means the file still holds <api-key> or a wrong key.

Models#

Omnigent enumerates models from GET /v1/models with the configured key, so its model picker lists the public eb1 models:

  • eb1-preview
  • eb1-frontier-preview
  • eb1-fast-preview
  • eb1-efficient-preview

These four public model IDs are the whole catalog. See Models for what each one is for.

Authentication#

The api_key value is sent as Authorization: Bearer, the same credential form as every other public endpoint. See API auth. A 401 means the configured key is missing, invalid, or revoked.

Requests from Omnigent appear in Keiro Usage and Logs like other API traffic.

Managed Sandbox limitation#

Managed "Omnigent on Databricks" Sandbox hosts pin their own endpoints and cannot use custom gateway entries like the one above. This setup applies to Omnigent running on your own machine.

Rotate the Omnigent key#

  1. Create a replacement dedicated key in the console.
  2. Update both api_key values in ~/.omnigent/config.yaml.
  3. Start Omnigent and verify a harmless request.
  4. Delete the old key in the console.

Search Keiro docs

Start typing to search pages and sections.

Start typing to search pages and sections.

Documentation

Console