Skip to main content

Claude Cowork

Claude Cowork sends model inference through a Tetrate Agent Router gateway in third-party inference mode. tare integrate claude-cowork writes the gateway config from the logged-in session.


Persona: Developer running Claude Cowork in Claude Desktop against an Agent Router gateway.

Estimated time: 10 minutes.

Outcomes

By the end of this guide:

  • Claude Desktop is configured for third-party inference through the Agent Router gateway.
  • A tare integrate claude-cowork apply has written the configLibrary entry and set it active, or the same values were entered in the Developer dialog by hand.
  • Cowork traffic appears in Request Logs with X-Title: Claude-Cowork and X-Provider: Tetrate AgentRouter.

Prerequisites

  1. Claude Desktop with Cowork installed from claude.ai/download.

  2. The tare CLI installed and authenticated:

    curl -fsSL https://tare.tetrate.ai/tools/install.sh | bash
    tare --version
    tare api login --base-url https://api.example.tetrate.ai

    Login can be skipped on integrate by passing --gateway-url, --api-key, and --model explicitly, but then nothing is reused from the account.

  3. A dataplane id for the gateway to route through. After tare api login, list dataplanes:

    tare integrate dataplanes

    Example output:

    DATAPLANE NAME GATEWAY URL
    acme-prod Acme Production https://acme-prod.gateway.example.com
    acme-dev Acme Dev https://acme-dev.gateway.example.com

    --dataplane takes the workspace id from the DATAPLANE column (for example acme-prod), not the display name in NAME.

  4. Claude Desktop launched at least once on the machine so the Claude-3p user-data directory exists. Without it, tare integrate reports that auto-config is unavailable.

Pro and Max subscriptions and passthrough mode are not supported for Claude Cowork

Claude Cowork through Agent Router runs in gateway mode only: the Agent Router inference key authenticates every request as Authorization: Bearer, and inference is billed through Agent Router.

Passthrough mode (keeping a Claude Max or Pro subscription as the billing path while the gateway routes and observes traffic) is supported for Claude Code via tare integrate claude-code --passthrough. It is not supported for Claude Cowork.


After tare api login, preview then apply:

tare integrate dataplanes
tare integrate claude-cowork --dry-run --dataplane <dataplane-id>
tare integrate claude-cowork --dataplane <dataplane-id> --yes

--dry-run prints the planned changes with the API key masked and writes no files.

On apply, the CLI:

  • Registers a third-party inference entry named Tetrate AgentRouter in the Claude Desktop configLibrary.
  • Sets inferenceProvider to gateway, inferenceCredentialKind to static, and writes the Agent Router inference key as inferenceGatewayApiKey.
  • Points appliedId in configLibrary/_meta.json at that entry so it becomes active on relaunch.
  • Validates the key with GET /v1/models using Authorization: Bearer <key>.

Config files are written under the Claude Desktop user-data directory:

PlatformPath
macOS~/Library/Application Support/Claude-3p/configLibrary/
Linux${XDG_CONFIG_HOME:-~/.config}/Claude-3p/configLibrary/
Windows%LOCALAPPDATA%\Claude-3p\configLibrary\

The entry file is 6167656e-7472-4000-8000-6f7574657200.json; _meta.json indexes it alongside any other saved configurations.

If Claude Desktop is running when apply runs, the CLI prints a warning. Quit Claude Desktop (Cmd+Q on macOS, File then Quit on Windows) before applying, because the app reads configLibrary only at launch.


Step 2: relaunch and continue with Gateway

After apply, quit Claude Desktop completely and reopen it. On the sign-in screen, select Continue with Gateway. The selector shows Local configuration; Anthropic account sign-in is not required for gateway inference.

Continue with Gateway from the Claude sign-in selector


Step 3: manual configuration (fallback)

Where tare integrate cannot write files, or the in-app path is preferred, configure third-party inference in Claude Desktop directly.

Enable Developer Mode

In Claude Desktop, go to Help, then Troubleshooting, then Enable Developer Mode.

Enable Developer Mode in Claude Cowork

Open third-party inference settings

Go to Developer, then Configure Third-Party Inference. Choose Gateway as the inference provider.

Open Configure Third-Party Inference from the Developer menu

Enter gateway settings

FieldValue
Gateway base URLGATEWAY URL from tare integrate dataplanes (scheme and host only, no /v1 suffix)
Gateway API keyInference key minted or reused by tare integrate claude-cowork on apply
Gateway auth schemebearer
Gateway extra headersX-Title: Claude-Cowork, X-Provider: Tetrate AgentRouter
ModelsA Claude model from the catalog (for example claude-sonnet-5), or leave empty for model discovery

Fill the Claude Cowork gateway form with Agent Router settings

Click Apply locally, then relaunch when prompted.

Run tare integrate claude-cowork --dataplane <dataplane-id> --yes to mint or reuse an inference key and print paste-ready values when auto-config cannot write files (or after declining the write prompt). Keys can also be created in the Console under API Keys; see Make an API call.


Verify

Send a prompt in Cowork. In Claude Desktop, enable Developer Mode (Help, then Troubleshooting, then Enable Developer Mode), then open Developer, Developer Console, Request Logs. Cowork requests appear as Anthropic Messages traffic with headers such as X-Title: Claude-Cowork and X-Provider: Tetrate AgentRouter.

Claude Cowork request shown in the Developer Console Request Logs


Troubleshooting

SymptomLikely causeFix
Auto-config unavailable; Claude-3p directory missingClaude Desktop never launched on this machineLaunch Claude Desktop once, then re-run tare integrate claude-cowork
Gateway option missing after applyClaude Desktop was not fully quit before relaunchQuit completely (Cmd+Q or File then Quit), reopen, select Continue with Gateway
Standard claude.ai sign-in screen instead of gatewayThird-party inference config was not readConfirm configLibrary/_meta.json has the expected appliedId; fully quit and relaunch
Validation warning after applyWrong dataplane, revoked key, or unreachable gatewayRe-run with --dry-run, confirm --dataplane id and GATEWAY URL, then re-run with --yes to mint and write a fresh key
Manual steps not printedConfirm prompt declinedRe-run with --yes to print paste-ready values including the API key