anyray-connect weekly downloads statistics

anyray-connect

The on-ramp. A small, dependency-free Node CLI that points a developer's local coding tools at the Anyray gateway through supported application config and the developer's personal gateway key. The gateway stays the brain (routing, spend store, content encryption, optimizer) — this only does capture/onboarding.

The Anyray gateway you target may itself front an existing gateway (LiteLLM, OpenRouter, Portkey, homegrown) via the anyray-upstream provider — that's configured server-side on the gateway, with no client-side difference to connect.

An npx run first copies its published runtime into a versioned directory under ~/.anyray/bin. Hooks, MCP registrations, and login services point at that durable copy instead of npm's disposable _npx cache.

Personal gateway keys (enrollment)

Every gateway /v1 request requires a personal gateway key (ark_...). Enroll before a real apply:

1. An org admin uses the console's Users page to create a passwordless enrollment link, or shares the org's SSO enrollment command. 2. The developer enrolls while connecting:

Enrollment mints a personal key and binds its verified user/team to spend attribution. The key lands in owner-only local state and the supported tool credential stores; it is never printed in full. Tools talk directly to a current gateway. A separate scheduled heartbeat signs a fresh, purpose-bound device proof and extends that same raw key before expiry, so running tools do not need a credential rewrite. The heartbeat never returns a replacement key.

Existing refresh-enabled Connect profiles continue routing directly after an update. If the heartbeat route is unavailable, Connect reports a gateway version or routing problem without treating the enrollment certificate as invalid.

A dry run never consumes an enrollment link or writes configuration; without an existing key it reports the selected installs that would be configured after enrollment.

Already have a key? Set ANYRAY_CLIENT_KEY in the environment. It must be a minted ark_... key; the old anyray-placeholder value cannot authenticate.

How the key is sent depends on the auth mode:

• Org API mode: the personal key is the Authorization bearer; the gateway selects the server-held provider credential after authenticating the developer. • --subscription: the tool's seat OAuth token keeps the Authorization header, and the personal key rides the x-anyray-api-key header instead so the gateway can still identify the dev.

Automatic coverage matrix

“Automatic” has two different meanings here: route means the request takes a supported path through the gateway and can be optimized; visibility means content-free usage arrives through the request path or an official vendor reporting API. A visibility connector does not pretend that closed first-party traffic was routed.

| Tool | Route setup | Spend visibility | Boundary |

| Claude Code | Automatic — writes the supported env block in ~/.claude/settings.json. | Automatic — API-key and Anthropic seat traffic is attributed on the gateway path. | Seat OAuth passes through unchanged; provider routing applies only to API-key traffic. | | Codex app / CLI / IDE | Automatic — all three share ~/.codex/config.toml; Connect makes the anyray provider the default without replacing foreign config. | Automatic — API-key and ChatGPT-seat traffic is attributed on the gateway path. | Retrieval is automatic. Source-side tool-output trim remains unavailable: Codex's blocking PostToolUse response rejects an already-completed tool promise in code mode, which can make a successful side effect look failed. Connect removes its retired hook rather than risk duplicate execution. Hosted tools and Codex cloud/web tasks also stay outside local hooks. | | Cursor | Automatic for native Team Claude/Opus context hooks by default: Connect leaves inference and either password or SSO-backed Team sign-in inside Cursor, then installs user-level Shell/MCP hooks plus the retrieval MCP server. The separate OpenAI BYOK custom-model lane requires explicit --org; its exact custom-endpoint cells have a reversible backup and queue while Cursor is open. | Hook savings are content-free. BYOK requests that Cursor sends to the custom endpoint are visible on the gateway path. Native inference has no gateway trace. Cursor's docs conflict on Team Admin API availability, so test an admin:* key against /teams/filtered-usage-events; Anyray can import native usage only when that call succeeds. | No Anthropic key is added in native mode. On macOS/Linux, recognized simple test/search Shell commands run through an exit-code-preserving output reducer; object-valued MCP results use updated_mcp_tool_output. Windows keeps MCP handling but skips Shell rewriting. Read/Write, complex Shell, native prompts/responses, and cloud agents remain outside this user-level seam. The opt-in BYOK lane needs public TLS and an upstream API key; its exact Agent wire behavior varies by Cursor release and it cannot consume the Cursor Team entitlement. | | OpenCode | Automatic for direct API providers and its Copilot provider. | Automatic for those routed lanes. | Restart OpenCode afterward. Built-in ChatGPT OAuth exposes no endpoint override; use Codex for that seat. | | VS Code Copilot Chat | Automatic on VS Code 1.121+ — Connect installs and configures an explicit Anyray chat provider through VS Code's supported language-model-provider API. | Automatic for gateway API-key mode. Copilot-seat/native automatic reporting requires Copilot Business or Enterprise plus the official GitHub connector; the current Anyray connector does not cover Individual plans. | The developer selects an “Anyray · …” chat model. Native Copilot Chat and inline completions remain GitHub traffic. VS Code profiles scope extensions: Connect installs into every profile registered at apply time (config is shared); a profile created later needs a re-run or the official Apply Extension to all Profiles action. | | JetBrains AI Assistant |…