chore(env): canonicalize TANGLE_API_KEY (drop legacy TANGLE_ROUTER_*)#16
Merged
drewstone merged 1 commit intoMay 14, 2026
Merged
Conversation
TANGLE_ROUTER_API_KEY and TANGLE_ROUTER_USER_KEY removed from agent-state.env on 2026-05-14. Both legacy names pointed at the same router operator key (sk-tan-HBMRou…); the canonical going forward is TANGLE_API_KEY (router operator) + TANGLE_SANDBOX_API_KEY (sandbox-scoped, minted via tangle-admin key-for sandbox). Migration sweep across consumer repos: 56 canonical files (excluding artifact JSONs in scripts/experiments/results/). All references to TANGLE_ROUTER_API_KEY and TANGLE_ROUTER_USER_KEY in code, env templates, shell scripts, GitHub Actions workflows, and docs now read TANGLE_API_KEY. Redundant fallback chains collapsed where the sed produced consecutive identical clauses. Per the tcloud platform, API keys are single-product (router OR sandbox OR evals OR blueprint-agent), not multi-scope — one key per product surface is the canonical model. The old proliferation of router-key aliases was confusion-driven, not architectural.
Contributor
Author
🔍 Reviewing
|
| Pass | Status | ETA |
|---|---|---|
| Kimi Code K2.6 | Running | ~5-15 min |
| opencode DeepSeek v4 Pro | Running | ~5-15 min |
Agent review running. Reads the actual code. This comment updates in place.
tangletools · #16 · model: kimi-for-coding · started 2026-05-14T10:34:03Z
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renames legacy
TANGLE_ROUTER_API_KEYandTANGLE_ROUTER_USER_KEYto canonicalTANGLE_API_KEYacross this repo (env templates, shell scripts, GitHub Actions workflows, docs, code). Matchesagent-state.envafter the 2026-05-14 rename.Canonical going forward:
TANGLE_API_KEY— operator key for every Tangle product (router + sandbox + evals + blueprint-agent + agent-builder + audits). Platform now supports unscoped (multi-product) keys viatangle-admin create-key NAME --product all.Companion:
agent-state.envTANGLE_API_KEYrotated to the new unscoped operator key; GitHub Actions secretTANGLE_API_KEYset in this repo (replacing the never-set legacy name).