Prerelease 0.149.0-alpha.7 on the 0.149.0 alpha line — small internal follow-ups for exec/TUI event handling, collaboration signaling, and configuration/requirements modeling.
Changelog
[new] Exec can process session events into JSONL-oriented output, making machine-readable run logs easier to consume downstream.
[new] The TUI keeps thread-related events in a dedicated path so timeline updates stay consistent as the session progresses.
[new] Collaboration sessions emit a clear end-of-wait signal when a collab wait completes.
[changed] Hook configuration distinguishes command-style and prompt-style handlers more cleanly.
[changed] Config and policy requirement models (including Guardian-related settings, managed hooks, and related TOML shapes) were extended to carry a fuller set of constraints.
[changed] Skills-related responses now cover migration/write flows more explicitly.
[changed] Thread fork responses and tool “request user input” payloads were reshaped for clearer client handling.
[changed] Filesystem helper payloads (for example create-directory / canonicalize-style responses) were tightened.
[removed] The delete_to_line_end event path is no longer part of the event set.
[removed] Several older app/task listing and background-terminal thread payload shapes were dropped in favor of the updated models.
Under the hood
Exec gained a dedicated JSONL event-processor path; the TUI added focused thread-event handling.
Remote code-mode session command-driver code was removed as that connection path was simplified.