Skip to main content
The recommended setup is the Nexus CLI, which writes your harness settings and restores the originals with nexus <harness> off. Use manual setup when you can’t install a CLI or need settings the Nexus CLI doesn’t write.

When to use manual setup

  • You can’t install the Nexus CLI.
  • You manage harness configs yourself, through dotfiles or a team rollout.
  • You want Nexus Auto to use Anthropic or OpenAI models without Provider Keys or the Nexus CLI.
  • You want to review every setting that changes.

What changes without the Nexus CLI

The harness calls the same Fireworks endpoints with your own API key. You take over the tasks that the Nexus CLI otherwise performs.

Before you start

  1. Create an API key in Nexus settings and export it:
  2. Back up the config file you’re about to edit.
  3. Use these endpoints: Anthropic-style clients add /v1/messages to the base URL themselves, so their base URL ends at /inference.
Use any model ID from Open Models, such as glm-latest, or auto for Nexus Auto.

Set up your harness

Follow the manual setup section for your harness: The Claude Agent SDK reads your Claude Code settings, so set up Claude Code first. Claude Desktop (Limited) has no manual setup and requires the Nexus CLI.

Use Nexus Auto with manual setup

For Nexus Auto to use an Anthropic or OpenAI model, either:
  • The harness sends an x-anthropic-api-key or x-openai-api-key header, or
  • Your account has Provider Keys.
Cursor IDE and the Copilot App can’t send extra headers, so they need Provider Keys. The harness setup builder generates a config with the headers included.