{"version":"2.1.317","anchor":"session-owner-hold-check-before-creating-the-api-client","canonical_anchor":"session-owner-hold-check-before-creating-the-api-client","heading":"API connection can be refused while another owner holds the session","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/session-owner-hold-check-before-creating-the-api-client","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### API connection can be refused while another owner holds the session\n\nWithout an API key, Claude Code now refuses to connect to the API with a session_owner error while a session-owner hold is in place\n\n**Unclear.** What puts a session-owner hold in place is not shown, so it is unclear when this error would appear.\n\n**What**\n\nWhen you are not using an API key, Claude Code now checks one more thing before it sets up its connection to the API. If a session-owner hold is in place, it stops with an error whose reason is `session_owner`. This sits alongside the existing check for subscribers, which was the only check that could stop it before.\n\n**Why**\n\nThis could block requests to the API in a session that another owner is holding.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: yes"}