Operations and native support

This chapter covers operational surfaces that sit around the main local agent runtime: debug logs, telemetry/traffic policy, updater/doctor and safe-mode recovery paths, crash/error reporting, the embedded enterprise gateway server, cloud/hosted review signals, and native media helpers. The directory retains its historical 05-hosted-agent-ops route for link stability; the reader-facing title reflects the chapter’s broader actual scope.

Read this chapter when the question is: how does Claude Code report, diagnose, update, or support host/native capabilities around a session?

Source-anchor policy

This page is a chapter guide. Linked implementation pages carry concrete cli.renamed.js or Bun-graph anchors.

Semantic alias	Minified anchor	Scope
Ops chapter	N/A — navigation page	Groups diagnostics, telemetry, update, gateway service, crash/debug logs, hosted review signals, and native media modules.
Ops implementation pages	See linked source-anchor tables	Concrete anchors live in destination pages.

Ops map

flowchart TD
    Runtime[Claude Code runtime] --> Debug[Debug logs]
    Runtime --> Telemetry[Telemetry / traffic gates]
    Runtime --> Update[Doctor / native updater]
    Runtime --> Gateway[Enterprise auth / inference / policy gateway]
    Runtime --> Hosted[Hosted review and remote ops]
    Runtime --> Media[Image/audio native modules]
    Debug --> Support[diagnosis]
    Telemetry --> Support
    Update --> Support
    Media --> Attachments[media/input support]

Primary reading order

Order	Page	Ops question answered
1	Diagnostics and debug logs	Which debug flags/writers, user-triggered /debug evidence flow, hidden /heapdump, startup marks, stall diagnostics, and crash/error surfaces exist?
2	Telemetry and tracing	Which traffic gates, telemetry sinks, tengu_* signal families, OTEL config, and trace export paths exist?
3	Feature gates reference	Which GrowthBook, tengu_*, env, policy, settings, and CLI gates switch runtime behavior?
4	Updater and doctor	How do doctor, update/upgrade, install, native auto-updater state, and hosted preflights work?
5	Safe mode and recovery	How does configuration isolation suppress user/project customizations while preserving managed policy, auth, built-ins, and permissions?
6	Environment variables reference	Which auth, provider, debug, telemetry, feature, MCP, plugin, agent, remote, UI, and update env vars are visible?
7	Enterprise gateway server	How does claude gateway --config join OIDC, Postgres, inference routing, managed settings, spend controls, OTLP relay, and network hardening?
8	Media native modules	Which non-cli.js graph modules are embedded, and how are image/audio native helpers loaded?
9	Audio capture and voice mode	How does /voice use local audio capture, recorder fallbacks, a transcription stream, and transcript injection?
10	Audio capture native module	Which Rust crates (cpal/alsa), ALSA PCM surface, and N-API exports ship inside audio-capture.node?
11	Image processor native module	Which Rust crates / N-API exports / defensive limits ship inside image-processor.node, and how is it wired into the sharp()-shaped JS facade?
12	Operations and native-support architecture	How do debug, telemetry, gateway, updater, doctor, and native helpers sit around the runtime without owning the local agent loop?

Handoffs

• Custom prompt and agent-row status-line execution is documented in Status line runtime and command protocol.
• Remote Control/session tokens are documented in Sessions, persistence, and remote.
• Remote-runner HTTPS egress, synchronized files, /uploads, and staged MCP lanes are documented in Remote-environment egress and file staging.
• Agents and hosted review command surfaces are documented in Agents and automation.
• Terminal accessibility rendering is documented in Accessibility and screen-reader mode.
• Protocol boundaries for voice streams and remote/provider transports are documented in Runtime communication protocols.

Navigation

• Start here
• Full table of contents