Billing, artifact, MCP and subagent call sites also take credentials explicitly now.
What's wrong with this entry?
The explicit credential value also reaches billing and org REST helpers (tax rate, prepaid credits, overage spend limit, admin requests and eligibility, referral eligibility, plugin ratings), design consent and grants, artifact publish/read-back/watch, MCP connect and reconnect, model listing, bug reports, subagent and workflow launches, the OAuth refresh loop, and the tool-use context itself.
- Also covers project docs read/write/create, plugin install, teleport environment selection, grove policy opt-in, OAuth account switch, history prefetch and session title updates.
- The org-memory credential minter now refuses a second, different store: handing one in after the fact logs that the later one is ignored.
- A startup composition path for the policy-limits client reports which of four adoption outcomes occurred, including late composition.
- Invisible in the common case; the point is that a session can act on a credential set other than the process-global one.
{ auth: "teleport-org", timeout: 5000, credentials: n }, credentials, tengu_policy_limits_late_composition, org-memory-discovery: a credentials store was already handed in; the later one is ignored
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth