Settings Menu Adds Queue Option to Interrupt Conversations Anytime
When you see your assistant heading in the wrong direction during a long task, you can now speak up and stop it directly.
You can find the Queued Messages option in the /config menu. Keeping the default Queue buffers follow-up messages until the current turn ends, while switching to Send Immediately interrupts the assistant right away. This preference can also be written directly to the global configuration file settings.json, fixing an issue where writing this setting previously got ignored by the system:
{"queuedMessages": "send-immediately"}
FEATURE
Remote Control Now Supported in Linux Containers, Starting in Background Without systemd User Service Manager
When you want to connect and operate inside a lightweight Docker environment, you previously hit a wall because the underlying system lacked an automated hosting mechanism.
When running remote-control start on Linux machines without a systemd user service manager (a program that manages background services for a user account), the daemon now starts directly as a background process, warning that the process will not restart on crash or launch on boot. You can enter remote-control status anytime to check its process ID (PID), and enter remote-control stop whenever you need to shut it down.
FEATURE
Long Conversations Load Faster, and Histories with Missing Steps No Longer Overwrite Old Progress
When you resume a heavy, long-running session or reconnect to your history after a crash, the entire workflow is noticeably smoother and safer.
When restarting conversations with thousands of steps, the command-line interface no longer pre-scans step-by-step, significantly speeding up load times. If history was missing steps due to crashes or interrupted writes, resuming will no longer hide the latest content, nor will new messages accidentally overwrite old records. Auto-generated conversation titles now also factor in images and files attached to the first message, giving concrete titles to requests that only include screenshots or files.
FEATURE
Login Error Prompts Include Appeal Links When Accounts Are Blocked for Violations
Starting your morning only to find yourself locked out, with a screen stating your account has been suspended for violating the Terms of Service, often leaves you wondering where to turn. Previously, encountering a blocked account only showed a generic failure message with no clear contact point; now, login failure error messages directly include an appeal link, letting you click the URL immediately to submit an explanation.
FEATURE
`--json-schema` Strictly Validated at Startup, Failing Immediately If Root Level Is Not an Object
When you pass a schema to a command, the system now intercepts formatting errors or missing files right at startup.
The --json-schema parameter no longer silently treats plain text, bare type names (such as string), or non-existent schema files as string types. Supplying any of these invalid inputs, or a schema whose root level is not an object ("type": "object"), now causes the program to output an error message at startup and exit immediately with exit code 1.
BUGFIX
Prompt Input Eliminates Cursor Drift, Keeping Emojis and Complex Characters Intact Across Line Wraps
When entering special characters in the terminal or working across multiplexed windows, cursor positioning and text wrapping now align precisely.
Inspecting Pipe Devices and Corrupted Media No Longer Hangs, Intercepting Early with Clear Prompts
When the assistant attempts to read special system files or incomplete audiovisual recordings, conversations no longer get trapped in endless waiting or error states.
Previously, if the assistant tried to inspect special files such as pipes, sockets, or device files, the process easily hung completely. Inspecting incompletely recorded MP4, MOV, or M4A media files also threw INVALID_ARGUMENT errors that blocked the conversation from continuing. When encountering either type of file, the system now intercepts before reading and provides a clear prompt.
Original changelog
Original changelogSettings Menu Adds Queue Option to Interrupt Conversations Anytime
Added the `Queued Messages` option to `/config`: keep the default `Queue` to hold follow-up messages until the current turn ends, or choose `Send Immediately` to interrupt the agent with them; it can also be set with `"queuedMessages": "send-immediately"` in `settings.json`, which was previously ignored
Original changelogRemote Control Now Supported in Linux Containers, Starting in Background Without systemd User Service Manager
Improved `remote-control start` on Linux machines without a systemd user service manager, such as most containers: instead of failing, it now starts the daemon as a background process and warns that it will not restart after a crash or start at boot; `remote-control status` shows its PID and `remote-control stop` shuts it down
Original changelogLong Conversations Load Faster, and Histories with Missing Steps No Longer Overwrite Old Progress
Improved loading long conversations: resuming a conversation with thousands of steps is noticeably faster because the CLI no longer scans every step up front
Improved automatically generated conversation titles to take images and files attached to your first message into account, so screenshot- or file-driven requests get specific titles and messages with only attachments get a title too
Fixed resuming a conversation whose history had a missing step, for example after a crash or an interrupted write, hiding the most recent steps and letting new messages overwrite them
Original changelogLogin Error Prompts Include Appeal Links When Accounts Are Blocked for Violations
Improved the sign-in error shown to accounts blocked for a Terms of Service violation, which now includes a link to submit an appeal
Original changelog`--json-schema` Strictly Validated at Startup, Failing Immediately If Root Level Is Not an Object
Changed `--json-schema` to reject plain text, bare type names such as `string`, and missing schema files instead of silently treating them as a string schema; these inputs, and any schema whose root is not `"type": "object"`, now fail at startup with an error and exit code `1`
Original changelogPrompt Input Eliminates Cursor Drift, Keeping Emojis and Complex Characters Intact Across Line Wraps
Original changelogInspecting Pipe Devices and Corrupted Media No Longer Hangs, Intercepting Early with Clear Prompts
Fixed the agent hanging when it tried to view a pipe, socket, or device file, and a conversation getting stuck with `INVALID_ARGUMENT` errors after the agent viewed a truncated MP4, MOV, or M4A recording; both are now rejected up front with a clear message