Background CMD with handle/poll: CMD&: and :bg-output <id>
#8
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Inspired by Claude Code's
run_in_backgroundBash flag and Monitor tool.What: New marker
CMD&: <command>instead ofCMD:. Behavior:forkpty(lands in Phase 1 anyway), records a small in-memory entry:{id, cmd, started_at, log_path, status}.[bg:<id> started].:bg-listshows running/done jobs.:bg-output <id>(or broker-issued, future) reads the log.[bg:<id> exited 0, 1.4MB out, 12s wall].Why: Builds, long network calls, file watches. Without this, a slow CMD: blocks the entire turn.
Where it lands: Phase 1 (pairs with PTY/forkpty work). Touches
executor.lua+repl.luameta + needs minorcontext.luaintegration.Source: https://code.claude.com/docs/en/overview (Schedule / background; analogous to Claude Code's run_in_background)