nvd-claude-proxy 1.4.0

Run Claude Code (and any Anthropic SDK client) on NVIDIA NIM models via a local proxy.

nvd-claude-proxy

Run Claude Code — and any Anthropic SDK client — on enterprise-grade NVIDIA NIM models.

nvd-claude-proxy is a low-latency local HTTP proxy that translates between the Anthropic Messages API and the NVIDIA NIM (OpenAI-compatible) API. The default runtime now uses the lightweight R2 path optimized for Claude Code responsiveness.

---

🚀 Key Features

• Architectural Excellence: Fully decoupled core translation logic from the transport layer.
• Enterprise Resilience: Built-in Circuit Breakers and automated failover chains to protect against upstream outages.
• Idempotency Support: Request deduplication and safe retries via anthropic-idempotency-key across Redis, SQLite, and Memory backends.
• Scalable State: Distributed session management via Redis (with SQLite and In-Memory fallbacks).
• Official-Grade Security: Unified AuthMiddleware protecting all endpoints with global API key enforcement.
• Claude Code Optimized: Specifically tuned for Claude Code's complex tool-calling and reasoning patterns.
• Vision & Progressive Streaming: Fine-grained progressive tool streaming and real-time multimodal (image_url) parity.
• Modular Pipeline: Event-driven streaming architecture for deterministic state management.

---

🛠 Deployment & Configuration

Environment Variables

Variable	Default	Description
NVIDIA_API_KEY	(Required)	Your NVIDIA NIM API key.
PROXY_API_KEY	None	Optional key to protect the proxy itself.
STORAGE_ENGINE	sqlite	Persistence backend: redis, sqlite, or memory.
REDIS_URL	None	Required if STORAGE_ENGINE=redis (e.g., redis://localhost:6379).
PROXY_PORT	8788	Local port for the proxy.
RATE_LIMIT_RPM	0	Global rate limit (requests per minute). 0 to disable.

Quick Start

# Install the proxy
pip install nvd-claude-proxy[full]

# Export your API key
export NVIDIA_API_KEY=nvapi-...

# Start the default low-latency runtime and launch Claude Code
ncp code

Then point your Claude Code at the proxy:

export ANTHROPIC_BASE_URL=http://localhost:8788
claude

---

🏗 Architecture

The proxy uses a Chain of Responsibility pattern for streaming events: MetadataProcessor -> TextProcessor -> ToolProcessor -> SafetyProcessor -> FinalizerProcessor

This ensures that even complex interleaved reasoning and parallel tool calls are correctly reconstructed for the Anthropic SDK.

---

Official-Grade Infrastructure for the AI Era.

---

Production Claude Code + NVIDIA NIM configuration

Use this proxy as the Anthropic-compatible endpoint for Claude Code:

export NVIDIA_API_KEY=nvapi-...
export PROXY_PORT=8788
export MAX_REQUEST_BODY_MB=32
export REQUEST_TIMEOUT_SECONDS=600
export STORAGE_ENGINE=redis
export REDIS_URL=redis://127.0.0.1:6379

# Optional but strongly recommended for shared/devbox usage
export PROXY_API_KEY=replace-with-a-long-random-secret

Run the proxy:

uv run ncp run
# or: ncp run

Point Claude Code at the proxy:

export ANTHROPIC_BASE_URL=http://127.0.0.1:8788
export ANTHROPIC_AUTH_TOKEN=dummy
claude

Recommended production notes

• Prefer STORAGE_ENGINE=redis for stable rate limiting, idempotency, and multi-session behavior.
• Keep MAX_REQUEST_BODY_MB=32 to avoid pathological payloads while still supporting large Claude Code tool catalogs.
• Use the default streaming path; it emits early message_start and periodic ping events to reduce apparent latency and prevent idle timeouts.
• If tool calls appear slow or malformed upstream, start with claude-sonnet-4-6 or claude-haiku-4-5 mappings before moving to larger reasoning models.
• This proxy is translation-only: Claude Code executes tools locally; the proxy must preserve tool ordering, streamed JSON fragments, and Anthropic-compatible SSE grammar.

---

R2 low-latency mode

Version 1.3.5 adds a lightweight hosted-catalog runtime inspired by the one-file reference proxy. Use it when you care more about fast first-token latency and minimal overhead than about the full production registry/session stack.

Start R2 mode

ncp r2 --model nvidia/llama-3.3-nemotron-super-49b-v1.5
# or
nvd-claude-proxy-r2

Then point Claude Code at it:

M=nvidia/llama-3.3-nemotron-super-49b-v1.5
export ANTHROPIC_BASE_URL=http://127.0.0.1:8787
export ANTHROPIC_API_KEY=not-used
export ANTHROPIC_CUSTOM_MODEL_OPTION=$M
export ANTHROPIC_DEFAULT_HAIKU_MODEL=$M
export ANTHROPIC_DEFAULT_OPUS_MODEL=$M
export ANTHROPIC_DEFAULT_SONNET_MODEL=$M
export CLAUDE_CODE_SUBAGENT_MODEL=$M
claude

Why use R2 mode

• eager message_start for lower perceived TTFT
• 15s ping heartbeat during silent reasoning phases
• simpler tool translation path
• direct NVIDIA model IDs, no alias registry required
• less overhead than the full production runtime

---

Default runtime in 1.4.0

Starting with 1.4.0, the default commands now use the low-latency R2 runtime:

• ncp code → starts the R2 runtime and launches Claude Code
• ncp proxy → starts the R2 runtime only
• ncp r2 → explicit alias for the same default runtime
• nvd-claude-proxy → starts the R2 runtime when invoked as the package entrypoint

This change prioritizes:

• faster first-token latency
• simpler Claude Code model wiring
• lower runtime overhead
• direct NVIDIA model IDs

Use NCP_DEFAULT_MODEL to override the default hosted NVIDIA model used by ncp code and ncp proxy.

---

Streaming quality and visualization

The default runtime now emphasizes Anthropic-style streaming quality:

• SSE id: field is emitted on every event
• early message_start for lower perceived TTFT
• keepalive ping events during silent upstream gaps
• progressive message_delta usage snapshots after content-block closes
• visualization side-channel events via event: ncp_visualization

R2 streaming environment knobs

• R2_PING_INTERVAL — keepalive cadence in seconds
• R2_TEXT_DELTA_CHARS — max chunk size for text/thinking deltas
• R2_STREAM_VISUALIZATION — enable or disable visualization side-channel events
• R2_MESSAGE_DELTA_EVERY_BLOCK — emit progress usage snapshots after each content block stop

Visualization endpoint

The runtime also exposes:

GET /v1/stream/visualization

This reports the currently active visualization behavior for dashboards or debugging tools.

Stream dashboard

The low-latency runtime now ships with a beautiful live stream visualization UI.

Open:

/dashboard/stream

Features:

• glassmorphism dark UI
• live color-coded event timeline
• state graph lanes for lifecycle, content, tools, and diagnostics
• websocket-driven real-time visualization from the R2 stream side-channel
• usage progress counters and live request tracking

This UI is powered by the ncp_visualization side-channel and the websocket endpoint:

/ws/stream-visualization