fusionkit
Tools

Claude Code

Run Claude Code backed by a fused model panel.

fusionkit claude launches Claude Code with the fused panel as its model backend. Claude Code speaks the Anthropic Messages dialect to the local gateway and treats fusion-panel as a normal model.

cd your-git-repo
fusionkit claude

Anything after the tool name is forwarded to Claude Code:

fusionkit claude --budget 5 -- --permission-mode plan

Prerequisites

  • The claude binary on your PATH. Install it from the Claude Code docs.
  • Fusion v4 and RouteKit router config. Provider credential environment names live only in .routekit/router.yaml.

fusionkit doctor verifies both before you launch.

How the wiring works

The launcher does not write any Claude Code configuration. It sets three environment variables on the spawned process:

ANTHROPIC_BASE_URL=<gateway-url>       # Claude appends /v1/messages
ANTHROPIC_AUTH_TOKEN=fusionkit-local   # or the gateway token when one is set
CLAUDE_CODE_ENABLE_GATEWAY_MODEL_DISCOVERY=1

Your own Claude Code login and settings are untouched. The same variables are printed by fusionkit serve if you want to wire Claude Code to a running gateway by hand.

The model picker

With gateway model discovery on, Claude Code's /model picker is populated from the gateway's model list: the default fused model and every other named ensemble. Claude-compatible aliases are generated by the neutral RouteKit tool launcher.

Sub-agents

By default the launcher passes a session-scoped --agents payload that defines one Claude sub-agent per named ensemble, so the Task tool can delegate to any ensemble out of the box. Nothing is written into your .claude/ directory. If you pass your own --agents, your definition wins. Pass --no-subagents to skip auto-provisioning entirely.

Caveats

  • Direct and single-model mode belongs to RouteKit; FusionKit has no --direct.