[Bug]: No way to background or kill a long-running process, blocking further prompts/chats

[shawk08033]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

When a command that runs indefinitely is started (e.g., a dev server or npm run dev), there is no UI option to move the process to the background or terminate it. As a result, the input prompt becomes blocked, and users cannot submit new prompts. When this happens, there is no clear explanation presented to the user indicating why input is unavailable.

Expected behavior

When an open-ended command is running, the user should be able to:

• Run it as a background task, freeing up the chat for new prompts
• Kill the process via the UI
• If neither option is taken, receive a clear message explaining why their latest prompt cannot be submitted and what steps they can take

Actual behavior

The command runs and the "Working for 0s" status indicator shows in chat. The submit button then spins indefinitely, and no new prompts can be entered. The only way to recover is to close and reopen the application.

Impact

Blocks work completely

Version or commit

V 0.0.13

Environment

Arch Linux(Cachey OS), desktop V0.0.13, GPT-5.4 High Full Access

Logs or stack traces

Screenshots, recordings, or supporting files

Screenshot From 2026-03-22 00-34-38.png

Workaround

No response

[shawk08033]

This also occurred after restarting the desktop app to recover from a blocked chat — even with no command running, I was still unable to submit a follow-up prompt.