Deployment

Ship Claude Code into CI, headless scripts, org-wide policy, and LLM gateways.

Move Claude Code beyond your local terminal: managed org settings, headless --bare mode for scripted CI, LLM gateway routing for cost tracking, and GitHub Enterprise Server setup.

All deployment questions (4)

How do I connect Claude Code to our self-hosted GitHub Enterprise Server?

An admin connects your GHES instance once via a guided GitHub App manifest flow. After that, developers start sessions with claude --remote in any GHES checkout. Plugin marketplaces on GHES require full git URLs instead of the owner/repo shorthand that only resolves github.com.
How do I push Claude Code policy to my whole org when we do not have an MDM?

Use Claude for Teams or Enterprise server-managed settings to deliver JSON policy from claude.ai to every developer's session at startup, without deploying files to devices. Configure permissions, hooks, and autoMode from one place.
How do I route Claude Code through our LiteLLM proxy for cost tracking and audit?

Set ANTHROPIC_BASE_URL to your LiteLLM endpoint, choose between unified Anthropic format and pass-through provider endpoints, configure authentication with ANTHROPIC_AUTH_TOKEN or apiKeyHelper, and avoid the compromised LiteLLM PyPI versions 1.82.7 and 1.82.8.
How do I run Claude Code from a script without it picking up my local hooks and MCP servers?

Add --bare to claude -p to skip all auto-discovered context (hooks, skills, plugins, MCP, CLAUDE.md, auto-memory). Pass only the flags you explicitly need. --bare is the reproducible mode for CI: the same call produces the same behavior on every runner.