Skip to content

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 16 Aug 14:00
· 57 commits to main since this release

v0.5.0 (2026-08-16)

Features

  • implement unified shell sessions (#20) (e5fca26)
  • refine transcript message styling (86db057)
  • support named session forks (a9dcdd2)
  • let agents choose git worktrees (228434f)
  • add safe session branching (#19) (3908c7b)
  • add cross-session agent messaging (#18) (9ddeb16)
  • add lightweight local browser visual checks (e6b95f0)
  • add automatic local browser visual checks (29eab8d)
  • add resilient stream reconnection (b5536bc)
  • support shell-native input clearing shortcuts (e797490)

Bug Fixes

  • hard-wrap user echo lines and keep committed rows off the wrap column (f6b015b)
  • unify command echo padding and tighten /ps output (b459161)
  • restore todoWrite immediate-update discipline in prompts (32f5b9c)
  • reduce echo padding and stop dropping one-shot /clear screen bytes (3492291)
  • install rust target for cargo xwin cross build (dee7c64)
  • harden DeepSeek stream handling (eb45732)

Unreleased

Features

  • unify foreground and background shell execution into managed sessions with automatic 10-second yielding, /ps, and /stop
  • use a bundled, hash-verified Windows Job Object supervisor for reliable process-tree cleanup on Windows x64 and arm64; normal Node.js builds do not require Rust
  • support interactive tty: true shell sessions through PTY/ConPTY with Unicode stdin, Ctrl+C, and terminal resize

Breaking Behavior Changes

  • omitting shell.timeout no longer applies a 30-second hard limit; commands keep running until their session ends or an explicit timeout is reached
  • shellOutput({ shellId }) now waits up to 5 seconds for a change by default; use block: false or yieldTimeMs: 0 for an immediate result
  • Esc stops waiting after a shell has started but does not kill it; use killShell or /stop to terminate it
  • /clear and /resume now terminate the current session's managed shells before replacing its runtime state
  • shell ids are runtime-only opaque ids and do not survive /clear, /resume, or a CLI restart

Contributors