Process

process is not a standalone task-starting tool but the management interface for exec background sessions. Once a command goes to the background, you need process to observe and intervene.

Common actions

Action	What it does
list	list running and recently finished sessions
poll	get incremental output and check if finished
log	read complete aggregated log by offset
write	write text to stdin
send-keys	send key sequences
submit	send Enter key
paste	paste text in bracketed paste mode
kill	terminate running session
clear	clean up finished sessions
remove	delete session; kills first if running

Typical flow

1. Start a job

   Use exec with background=true to start a background task.

2. Track it

   Use process list or process poll to check running status.

3. Interact if needed

   If the task is waiting for input, use write, send-keys, submit, or paste.

4. Collect or clean up

   After completion, use log for full output, then clear or remove as needed.

Example

{ "tool": "exec", "command": "npm run dev", "background": true }

Then:

{ "tool": "process", "action": "poll", "sessionId": "<id>" }

Notes

• process only manages background sessions
• foreground commands that didn't go to background cannot be handed to process
• session results include sessionId, duration, tail, exitCode, etc.

Related

• Exec is the entry point to process