{
  "id": 6320513,
  "title": "kagent 0.10 Ships Audience-Bound Agent Tokens, Off By Default",
  "url": "https://urgent.news/2026/09/08/kagent-0-10-ships-audience-bound-agent-tokens-off-by-default",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-08T19:56:58.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/webofmike/kagent-010-ships-audience-bound-agent-tokens-off-by-default-40ig"
  },
  "original_language": "en",
  "account": "kagent version 0.10.0 has been released, introducing two environment variables, KAGENT_STS_RESOURCE and KAGENT_STS_AUDIENCE, to control the backend scope of an agent's credential. Both variables default to empty. A demonstration harness shows how different configurations affect the token's scope and authentication. By setting KAGENT_STS_RESOURCE to a specific backend URL, the token is valid only for that backend, preventing accidental access to other backends. Leaving the variables empty results in an unscoped token, granting access to all backends that trust the STS. The fix is now configurable, allowing users to explicitly specify the target resource in the exchange and receive a token scoped to that resource, avoiding the confused deputy problem.",
  "summary": "Originally published at webofmike.com on 2026-09-08. The demo repo and every command in it were run before publishing. kagent v0.10.0 went GA on September 4 . Buried in a long release list is a pair of environment variables that decide whether an agent's credential works at one backend or all of them: KAGENT_STS_RESOURCE and KAGENT_STS_AUDIENCE . Both default to empty. I built a three-container…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}