Patch release 1.0.30: public grok cursor-worker CLI, clearer memory opt-out vs. remote v2, optional subagent messaging under a feature flag, and a tighter dashboard details header.
Changelog
[new]grok cursor-worker — Register this machine as a Cursor private worker through the leader. Subcommands: start (register or restart with new options), stop (unregister and release claims; the leader keeps running), and status / list (worker status and Cloud Agent claims). Supports --leader-socket, --debug, and --debug-file. Shell completions cover the command and the leader --cursor-worker flag.
[changed]Memory enablement — An explicit [memory] enabled = false in your TOML turns off both legacy memory and memory v2, including a v2 rollout enabled remotely. Only an explicit [memory_v2] enabled = true in the same TOML overrides that local opt-out. Process-wide disable (--no-memory / GROK_MEMORY=0) still wins first.
[changed]send_subagent_message — Off by default; enable with GROK_ACTIVE_AGENT_MESSAGES or [features] active_agent_messages. The root can still message subagents it owns. When the flag is on, a granted child also gets the tool (subagent_id: "parent" for its active parent, or a durable agent id for another local subagent; eligible completed subagents resume with the same identity). Children cannot message the root. Curated harness toolsets never receive it. Child senders are capped (4 in-flight per sender–target pair, 32 outbound per attempt); over limit returns QuotaExceeded. Delivery modes steer / queue / interject are unchanged.
[changed]Dashboard details view — Uses the session header instead of an extra title band: agent name on the left (name │ main ~/path; omitted when unnamed), cycle control ‹ n/m › and [Dashboard] on the right. ‹ / › cycle agents; Esc / Ctrl+\ / [Dashboard] return to the list. Every session with the dashboard enabled shows [Dashboard] in its header (not only sessions opened from the dashboard); disabling the dashboard removes the control.
Under the hood
Cursor private-worker claim handling and related leader wiring for the public CLI.
Subagent message-sending path and pager support for taking over a subagent view.
Agent directory support in the shell agent path.
GROK_LENGTH_SALVAGE feature flag naming cleaned up.
Client can fetch account/org profile via the user settings surface.
Upgrade notes
If you depended on send_subagent_message without a local flag, turn on GROK_ACTIVE_AGENT_MESSAGES or [features] active_agent_messages.
To keep memory off while a remote memory v2 rollout is active, set [memory] enabled = false (or enable v2 explicitly with [memory_v2] enabled = true if that is what you want).
