Claude Code

developerz.ai is a thin orchestrator — it does not write code. It triages the issue and, when it qualifies, hands off to Claude Code running on your own box. Claude Code writes the fix and opens the PR; the maintainer agent watches CI and review and merges when the gates pass.

Trigger a handoff

Set handoff.mode: webhook in .maintainer.yml and point it at a dashboard webhook wired to your Claude Code runner:

# yaml-language-server: $schema=https://developerz.ai/schemas/maintainer.v1.json
version: 1

handoff:
  mode: webhook
  webhook_ref: claude-code-hook
  ask_reporter_first: true

A qualified bug or feature fires a signed issue.handoff event; your runner picks it up and dispatches Claude Code. See the .maintainer.yml reference for every handoff field.

BYOK — your key, your bill

Claude Code runs on your Anthropic key. developerz.ai never proxies or resells tokens — your provider invoice shows exactly what the agent spent. Swap models any time without touching your policy. See the BYOK doc.

Native tools over MCP

Claude Code can connect straight to our MCP server at mcp.developerz.ai and use the maintainer tools natively — dispatch tasks, check fleet status, re-run a review — from inside the editor. Add the server to .claude/settings.json with a PAT; the Quickstart has the exact config. MCP is the integration surface; the full tool list is in the MCP verb reference.

Full audit trail

Every maintainer decision — and every MCP tool call Claude Code makes against mcp.developerz.ai — is written to the append-only audit log, reachable from each webhook event's audit_url. The bot always discloses that it is an automated agent, and defers to any other review bot on the PR (no bot-on-bot loops). If it isn't logged, it didn't happen — see the security doc.