{"version":"2.1.281","anchor":"cloud-hosted-authbearer-async-bearer-resolvers-and-respons","canonical_anchor":"cloud-hosted-authbearer-async-bearer-resolvers-and-respons","heading":"Cloud-hosted auth\/bearer: async bearer resolvers and response observers can be registered","tier":"internal","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-hosted-authbearer-async-bearer-resolvers-and-respons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud-hosted auth\/bearer: async bearer resolvers and response observers can be registered\n\nCloud-hosted auth can now register callbacks that fetch a bearer token on demand and observe responses\n\n**Unclear.** The finding does not say who registers these callbacks or whether users can configure them.\n\n**What**\n\nA bearer token is a credential sent with each request to prove who is calling. The part of Claude Code that holds settings it manages itself can now also store two kinds of callback, which are functions it calls later:\n\n- `resolveBearerToken`, which gets a bearer token when one is needed.\n\n- `onResponse`, which is told about responses.\n\n**Why**\n\nCloud-hosted setups can supply credentials when a request is made instead of fixing them in advance, and can react to what comes back.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}