{"version":"2.1.318","anchor":"send-to-project-and-not-owner-reasons","canonical_anchor":"send-to-project-and-not-owner-reasons","heading":"\/send-to-project offers to turn on Remote Control and asks for a message when none was typed","tier":"notice","area":"Slash Commands","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/send-to-project-and-not-owner-reasons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### \/send-to-project offers to turn on Remote Control and asks for a message when none was typed\n\n\/send-to-project can turn Remote Control on, opens a compose dialog when no message was typed, and explains more clearly why nothing was sent\n\n**Unclear.** Whether `\/send-to-project` is available to users in this release is not clear.\n\n**What**\n\n`\/send-to-project` sends a message from your Claude Code session to a claude.ai Project. The Project reads the session through Remote Control, a feature that lets a session be reached from somewhere else. The command was reworked in several places:\n\n- Remote Control: if Remote Control is off, the command now offers to turn it on. It runs a check, switches it on, then waits for it to connect. Before, it stopped with an error. The command descriptions now say it \"offers to turn it on when it is off\", and the dialog has a \"Turn on Remote Control and send\" choice.\n\n- New outcome messages: there are four new messages for when Remote Control cannot be turned on, for the cases declined, failed, timed_out and account_changed. Before, only the cases none, withheld and unverified had messages. Each failure ends by saying nothing was sent. One example: \"Remote Control stays off, so nothing was sent: a project reads this session through it. Run \/send-to-project again to turn it on.\"\n\n- Compose dialog: when you run the command without typing a message, it opens a dialog that asks for one. The two dialog kinds are `continue_in_projects_remote_control` and `continue_in_projects_compose`. They only appear in interactive sessions. In a terminal session with no conversation, the message command asks you for the message.\n\n- Three message modes: the message can be typed after the command, typed into the field the command opened, or not given at all. Before there were only two modes. In the field mode, the instructions Claude receives include a \"The message the user typed\" section, so Claude can rewrite the message if you decline it.\n\n- Empty conversation: a new message reads \"There is no conversation above to draft a message from, so nothing was sent. Run \/send-to-project again with the message typed after it.\"\n\n- Refusal reasons: when the session is not the one in control, the refusal now gives a specific reason, such as `not_owner_remote_control` or `not_owner_relay`, instead of always saying `not_owner`. A message sent to a session that cannot be reached can now also give a specific reason, which comes from `whyNotSending`.\n\n- Project tools error: the message now reads \"No project attached to this session. Project tools are available when the session is in a claude.ai Project.\" Before, it said \"started inside a claude.ai Project\".\n\n**Why**\n\nBefore, having Remote Control off was a dead end. Now you can switch it on from inside the command. When sending fails, the messages say which step went wrong, so you know what to do next.\n\n- Area: Slash Commands\n- Names: `\/send-to-project`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}