/send-to-project reports unavailable Claude Projects early and gains a Remote Control offer dialog

What

/send-to-project is the command that sends work to a Claude Project. This release changes what it does when a new project cannot be made, and adds a new question it can put to the user.

• Up-front check: it now checks whether Claude Projects is available before listing projects. Before, a projects-unavailable message came only after the listing step.
• Existing projects instead: when the account cannot create a new project, Claude is told to send to one of the user's own projects, with the message "A new Claude Project can't be created for your Claude account".
• Named outcomes: the channel list reads create_refusal_reason and create_refusal_message, and the command reports projects_unavailable instead of the generic send_failed when the server refuses new projects. A new_project_unavailable outcome is also added.
• Remote Control offer: a new dialog kind, send_to_project_remote_control_offer, is added to the dialogs that need the user's input. Its description is "choose: turn on Remote Control and send, or not now". Only a caller of type sdk_host (a program that runs Claude Code through its SDK, the kit for building on top of Claude Code) can answer it, the same rule two existing dialog kinds follow. What triggers this dialog was not seen.

Why

When your account cannot make new projects, you get a specific reason sooner instead of a generic failure, and Claude is pointed at a project you already have. The Remote Control offer can only be answered by sdk_host callers, so it is not something the plain terminal answers.