Patch release 1.0.26: opt-in Memory v2, Cursor private worker registration via the leader, richer subagent messaging, and a fuller /feedback form.
Changelog
[new]Memory v2 (opt-in). Enable with [memory_v2] enabled = true for an isolated observation-and-topic pipeline under ~/.grok/memory-v2/. It captures completed turns asynchronously, runs event-driven Dream consolidation under a fenced lease, and never reads or migrates legacy ~/.grok/memory/. Use /memory status for content-free queue, lease, retention, and rollout diagnostics. Legacy memory (GROK_MEMORY, [memory] enabled) keeps working until you turn v2 on; v2 then takes precedence. Advanced rollout stages (off / record_only / shadow / active) and component kill switches are available for staged rollout.
[new]Cursor private worker.grok cursor-worker (start / stop / status / list) registers the leader so Cursor Cloud Agents can run against this machine. Configure via [cursor_worker] (auto_start, name, worker_dirs, max_agents, hub_url, rewrite_shell_output), or pass --cursor-worker / --cursor-worker-name / --cursor-worker-dir / --cursor-worker-max-agents on grok agent leader. Registration is hub-gated for enabled accounts. Shell completions cover the new command and flags.
[new]Subagent delivery modes.send_subagent_message can target any subagent owned by the root session (inactive agents wake on the message). For active agents, delivery is steer (default), queue, or urgent interject (ahead of pending steers; interrupts a wait on background work without stopping that work). Legacy queue: true still maps to delivery: "queue".
[changed]/feedback form. Bare /feedback opens the form in every mode, including --minimal. Write and Drafts tabs switch with Ctrl+Tab / Ctrl+Shift+Tab; Drafts support search, delete, and load-into-Write. Label rows (type/task/failure) are editable when a draft supplies them. Agent-drafted feedback lands in Drafts for review before send.
[changed]Custom rule directories.[paths] extra_rule_dirs loads every *.md directly inside listed absolute or ~/… directories as global user rules (no subdirectory scan), after home rules and independent of folder trust, .gitignore, and vendor compat cells. /import-claude can point here so Claude rules keep loading after the Claude scan is turned off.
[changed]Session on-disk artifacts. Sessions now record system_prompt.txt, prompt_context.json, and tool_definitions.json (function tools from the latest model call; MCP tools stay reachable via search_tool / use_tool).
[changed]Dashboard actions row. Arrow keys navigate the actions row when the list is focused or the dispatch box is empty; once you type (or in search mode) they edit the draft. Vim h/l still need list focus and stay inert in search mode.
Under the hood
New Cursor worker stack on the leader: registration, claims/worktrees, exec bridge, and token refresh against the Computer Hub.
Memory v2 storage, capture, consolidation/Dream, and maintenance paths, with session hooks for capture status and diagnostics.
Telemetry logging and span modules reorganized (logs, process metrics, session lifecycle, spans).
Config reference documents the full [cursor_worker] and [memory_v2] surfaces; memory.mode is gone in favor of the v2 gate and rollout controls.
paths.extra_skill_dirs remains written by /import-claude and is not yet used by skill discovery.
Upgrade notes
Existing memory setups are unchanged until you set [memory_v2] enabled = true. There is no automatic migration from legacy memory.
Prefer [memory_v2] over any older memory.mode style switch; force-disable with --no-memory or GROK_MEMORY=0 still turns both implementations off.
Cursor worker needs a build with worker support and a hub account that has the feature enabled; default is off (auto_start = false).
