Repository navigation
Long-running work: finish notifications and background commands #51
Description
Problem
- Users walk away from slow requests. Local models are slow, so users switch to something else during long requests and don't know when one finishes or needs approval.
- Long-running processes block the model. It can't start a dev server or a test watcher and keep working, because
bashwaits for the command to end, or times out.
Proposal
- Notifications: a desktop notification when a request that took longer than N seconds finishes, or when it waits for approval.
- It uses
notify-sendon Linux andosascripton macOS, with the terminal bell as a fallback. - Settings:
notify = on | offand the time threshold. - Good first issue.
- It uses
- Background commands:
bashwithbackground: truestarts a process and returns an id.bash_output(id)reads its new output andbash_stop(id)stops it.- Background processes are stopped when the session ends and listed in
/jobs.
Acceptance criteria
- A notification after long requests and approval prompts, on Linux and macOS
- Background commands with output and stop; cleaned up at session end
- Tests and docs
Activity
nasser1941 commentedon Oct 6, 2026
Shipped in 0.20.0 (#85): background commands (
bashwithbackground: true,bash_output,bash_stop,/jobs) and desktop notifications (notify,notify_after). See Background commands and Notifications.Tested with Qwen3.6 35B through Ollama, also from the PyPI build:
bash(…, background=true),curl,bash_outputandbash_stop. The port was closed afterwards.&: a command that starts something with&no longer hangs until its timeout. What it left running is stopped, and the model is pointed to background commands.dbus-monitor: "lcode is done", with the request and how long it took. The macOS path (osascript) is covered by tests but not run on a Mac.