Live Session app v1.1.35: Add your own variables to a command handoff
Command destinations in Send to AI can carry your own named variables, each with a default you can change before any send, and the terminal window stays open after the command finishes so you can read its output. The MCP tool also stops telling you to reconnect when your connection is still active, and gives clearer messages when it needs more permissions or the server turns its request down.
Sending a session to a command gave your script the session and folder, but anything else it needed, such as a ticket or a branch, had to be hard-coded into the command itself.
Today, we're adding handoff variables, along with a clearer message from the MCP tool when a request cannot go through.
Variables for command handoffs
A destination that runs a command now has a Variables (optional) section. Click Add variable and give it a name and a default value.
The hint under the section shows the name your command reads each variable by, with a Chief prefix in front of the name you chose. Names are upper case letters, digits and underscores, and Chief converts what you type as you type it.
Each variable shows up as its own field when you send, filled with its default, so you can change the ticket or branch for one send without editing the saved destination. A command can hold up to 20 variables.
You can clear a value before sending, so give each variable a fallback value in your command.
After the command runs, its terminal window stays open with a line showing the exit status, and closes when you press Return, so a command that finishes at once leaves its output readable.
Sending a Live Session to an AI agent covers setting up a destination.
Fixes
- The MCP tool told you to reconnect when your connection was still active in settings. It now keeps working, and when it needs more permissions or the server turns its request down, it says so in its own message.
Update to 1.1.35 and open a command destination in Send to AI to add your first variable.