{"version":"2.1.248","anchor":"project-and-agent-dispatch-still-need-an-endpoint-your-accou","canonical_anchor":"project-and-agent-dispatch-still-need-an-endpoint-your-accou","heading":"Project and agent dispatch still need an endpoint your account may not have","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/project-and-agent-dispatch-still-need-an-endpoint-your-accou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Project and agent dispatch still need an endpoint your account may not have\n\nCloud sessions with --project or a specific agent are refused if your account lacks the newer endpoint.\n\n**What**\n\nCreating a cloud session with `--project`, a session group, or a specific agent id requires the newer session-create endpoint. If your account is on the older one, creation is refused outright with a message naming the reason, `project_not_enabled` or `agent_not_enabled`, and no session is started.\n\n**Details**\n\n- The newer endpoint is chosen when no environment variables were passed and an async check passes, or when the request came from ultrareview or ultraplan and a separate gate passes; otherwise the older endpoint.\n- The ultrareview\/ultraplan branch is decided remotely; what it falls back to is not visible in this build.\n\n**Evidence**\n\n`Dispatching into a Kindling project requires the new session-create endpoint, which isn't enabled for your account yet \u2014 no session was created.`\n\n- Area: Cloud Sessions\n- Names: `--project`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}