Skip to content

1.3.2 — Steady Mercury (hotfix: /code, launch pad, /stop)

Choose a tag to compare

@hotheadhacker hotheadhacker released this 11 Oct 09:34
· 389 commits to main since this release
095a220
  • Launch pad on mercury. The default launch attaches to the daemon (ADR-024) and the attach screen had dropped the launch pad — the wordmark, provider/skills/web/budget rows and tip the main TUI opens with. It is back, fed by real runtime state, above the session picker.
  • /stop then a command. /stop aborts asynchronously; a slash command typed before the turn finished unwinding was answered "Agent is busy…". The launcher now waits for the stop to complete (up to 5 s) and runs the command normally.
  • /code works again from mercury. Since 1.3.1 the default launch attaches to the daemon, and /code typed there was forwarded to the daemon's web channel — which has no terminal to switch into — so it printed "Programming mode: Off". The attach TUI now hands the terminal to Mercury Code (/code or /code <dir>), exactly what mercury code does; the runtime keeps running in the background. /code plan|auto|off inside the attach TUI explain where to run them.