v0.88.0

Fixed

• The plan panel's Approve and Ask for changes answer the right question. The plan event now carries the id of the approval it waits on, and the panel offers its buttons only when that id matches the approval pending on the card; before, it matched by text. A plan whose approval it cannot identify shows "waiting for approval on the card" with no buttons, instead of saying it was approved. (#1233)

• Settings search finds the hooks and worktree cleanup switches. Typing "hook" or "worktree" in the Settings search now lists the lifecycle hooks, the Claude Code hook switches and the archived-worktree cleanup, and opening a result focuses its switch; before, these rows were on the General tab but the search could not find them. (#1229)

Added

• Run a conversation's commands on another machine over SSH. A saved environment can now be an SSH host: an alias from your ~/.ssh/config that you added to the allowed hosts in Settings, plus the remote folder commands run in. Commands go through your system's ssh with your agent and known_hosts, never a password or key typed into Chimera; a new or changed host key is never accepted on its own, agent and port forwarding are off, and the config cannot turn a command into a different one. A dropped connection is retried only when the client log shows the command never started, so nothing runs twice. The local file tools are off in an SSH conversation so the agent cannot edit the wrong machine; files on the host are reached through commands for now. SSH counts as running on the host for the host-exec gate and the permission modes, a turn that read outside content asks before each SSH command, and only your own screen manages hosts and environments. (#1234)

• Choose where a conversation's commands run: on this machine or in WSL. Before the first message, the Code screen offers the saved environments (Settings lists, adds and removes them; a WSL one names a distribution) and a project can have a default; after the first turn the environment is fixed, and a removed one leaves the conversation without commands rather than falling back to this machine. In WSL, run_shell and execute_code run through wsl.exe --exec bash -lc in the same folder seen as /mnt/<drive>/..., while file tools stay on this disk. WSL is not isolation: it counts as running on the host for the host-exec gate, Manual and Accept edits, and it is refused when the install is set to an isolated sandbox. The paths it can reach are read back as Windows paths by the fences that guard the audit log, the approvals queue, .env, MCP tokens and hooks, so /mnt/c/..., cd chains and -C DIR cannot get around them. Only your own screen creates, removes or chooses an environment. (#1232)

• The receipt says why a turn missed the cache, and an idle conversation sends a shorter history. A Code turn that read nothing from the prompt cache now names the cause: first turn, the cache's lifetime ran out during a pause, the system prompt or the tools changed, the model or route changed, or the route has no explicit cache; the status bar shows the last cause. When a conversation sat idle past its provider's cache lifetime (five minutes on Anthropic; nothing is assumed for other providers), the next turn sends a compacted history through the agent's own compaction, since the full history would be paid at full price anyway. Only what is sent is shortened: the stored conversation and what you see stay complete. A summary that calls a model counts toward the turn's budget and appears on the receipt, a conversation that read outside content is compacted without a model summary, and a failure here never stops the turn. CHIMERA_IDLE_COMPACTION, on by default. (#1231)

• Scheduled tasks: missed runs, history, a permission mode and a worktree per task. A task whose time passed while the app was off runs once when it is back, if the missed time is at most 7 days old, never once per missed time (catch_up: once or skip; a pause shorter than 30 minutes is not a miss). Every scheduled time is recorded with whether it ran and why not, shown per task on the Schedule screen. A task can have one of the Code screen's permission modes, never wider than Settings and never "Ignore permissions"; a mode that would ask someone refuses instead, and only your own screen sets it. A task can run in a fresh worktree, removed afterwards only when it left nothing (no changes, no ignored files, no unpushed commit), otherwise kept with its path in the history. (#1230)