Skip to content

fix(mcp): accept TANGLE_SANDBOX_API_KEY (canonical) with TANGLE_API_KEY fallback#48

Merged
tangletools merged 1 commit into
mainfrom
fix/mcp-dual-key-name
May 24, 2026
Merged

fix(mcp): accept TANGLE_SANDBOX_API_KEY (canonical) with TANGLE_API_KEY fallback#48
tangletools merged 1 commit into
mainfrom
fix/mcp-dual-key-name

Conversation

@tangletools
Copy link
Copy Markdown
Contributor

Phase 2 wiring surfaced naming confusion. TANGLE_SANDBOX_API_KEY is now canonical; TANGLE_API_KEY accepted as fallback.

…EY fallback

Phase 2 wiring surfaced the confusion: TANGLE_API_KEY in product envs is
the ROUTER key (sk-tan-*); the MCP bin needs a SANDBOX-scope key
(sk_sb_* or orch_prod_*). The 0.20.2 rename to TANGLE_API_KEY broke the
intuition — operators reading the same env var name expected different
meaning across contexts.

TANGLE_SANDBOX_API_KEY is the canonical name. TANGLE_API_KEY accepted as
fallback (no behavior change for callers that already passed a sandbox-
scope key under TANGLE_API_KEY in 0.20.2). Top-of-file doc + error
message both updated to reference the canonical name.

215 tests pass unchanged.
@tangletools tangletools merged commit 0a1d749 into main May 24, 2026
@tangletools tangletools deleted the fix/mcp-dual-key-name branch May 24, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants