# Forge Gateway

> Forge Gateway (https://forgegateway.ai) runs Claude Code and Codex through the CLEATUS Forge model gateway. People at CLEATUS and at partner companies sign in with their work Google account, create personal fgw_ keys, and see their own usage and its API-equivalent cost.

## Set up in one command

    npx @cleatus/forge

1. It opens https://forgegateway.ai/connect in a browser and prints a verification code.
2. The person signs in with Google, checks that the code on the page matches, and clicks Connect. This step needs a human: an agent cannot sign in or approve.
3. The page mints one personal key and hands it to the command on 127.0.0.1. The command writes the setup and prints what it changed.

With no flags on a terminal it asks which targets to set up. Off a terminal (an agent, a script) it sets up everything it finds, so pass flags to be explicit.

## Flags

    --claude         Claude Code: the forge-claude launcher in ~/.local/bin
    --codex          Codex: ~/.codex/config.toml (plain codex uses the gateway) plus the forge-codex launcher
    --paseo          Paseo: "Forge Claude" and "Forge Codex" agent providers
    --conductor      Conductor: its Claude and Codex executables point at the launchers
    --all            Everything it finds
    --no-open        Print the approval link instead of opening a browser (use this from an agent)
    --label <name>   Name for this computer's key (default: hostname plus a machine id)
    --port <n>       Listen on a fixed local port, for a remote machine (see below)
    --help, --version

Flags combine: `npx @cleatus/forge --codex --paseo` sets up Codex and Paseo only.

## For an agent

Run `npx @cleatus/forge --no-open --claude --codex`, keep it running, and relay the printed link and verification code to the person. Wait for the command to finish (it gives up after 10 minutes), then report what it set up. Do not mint a key, edit ~/.codex/config.toml, or set ANTHROPIC_* variables by hand; the command does that. It backs up a previous ~/.codex/config.toml beside that file as config.toml.backup-<time>, and every other file it changes under ~/.config/forge-clients/backups/.

## Remote machine

The browser hands the key to 127.0.0.1 on the computer where the command runs. On a remote machine, forward a port first: `ssh -L 8765:127.0.0.1:8765 <host>`, then run `npx @cleatus/forge --no-open --port 8765` there and open the printed link in your own browser.

## After setup

- Claude Code: run `forge-claude`.
- Codex: run `codex` as usual, or `forge-codex`.
- Run the command again on the same computer to replace that computer's key. Revoke keys at https://forgegateway.ai.
- Usage and API-equivalent cost show at https://forgegateway.ai.

## Manual setup

Create a key at https://forgegateway.ai, then:

~/.codex/config.toml:

    model_provider = "forge"

    [model_providers.forge]
    name = "Forge Gateway"
    base_url = "https://forge.cleat.ai/api/v1/codex"
    wire_api = "responses"
    env_key = "FORGE_GATEWAY_KEY"
    requires_openai_auth = false
    supports_websockets = false

Shell profile:

    export FORGE_GATEWAY_KEY=fgw_your_key
    export ANTHROPIC_BASE_URL=https://forge.cleat.ai/api/v1/claude
    export ANTHROPIC_AUTH_TOKEN=fgw_your_key

## Requirements

Node.js 18 or newer; 22.13 or newer for the launchers. Install the clients separately: `npm install -g @anthropic-ai/claude-code @openai/codex`. Windows gets the Codex config only.

## Access

Sign-in is open to CLEATUS and to partner companies CLEATUS has set up. An account without access sees a contact option for support@cleat.ai.