background

Start, monitor, and stop background processes with job_id polling.

9|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/lmorchard/decafclaw --skill background
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: background
Source: https://github.com/lmorchard/decafclaw/tree/main/src/decafclaw/skills/background
Command: npx skills add https://github.com/lmorchard/decafclaw --skill background

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run long-running background processes without blocking conversations. It starts, monitors, and stops tasks and returns a job_id you can poll for output.

Core Features & Use Cases

  • Start a background job with an immediate job_id.
  • Poll status and output via the status function.
  • Stop a background job safely with termination signals.
  • List all background jobs in the current conversation.
  • Safe lifecycle: per-conversation scope, 10-minute max lifetime, 500-line buffers.

Quick Start

Start a background process with a shell command and monitor its status using the returned job_id.

Frequently Asked Questions about background

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run long-running shell commands without blocking the chat conversation?

To run shell commands without blocking the conversation, you can start a background process that executes asynchronously and returns a job_id immediately for polling output. This enables continuous collaboration while dev servers, file watchers, or builds run in the background.

How do I monitor and stop a background process started in a chat session?

To monitor and stop a background process, you poll its status and output using the returned job_id, and issue a stop command that safely terminates the job via SIGTERM and SIGKILL signals. This ensures safe lifecycle management for your asynchronous tasks.

What are the lifetime and buffer limitations for asynchronous background jobs?

Asynchronous background jobs have a maximum lifetime of 10 minutes and maintain a 500-line output buffer. Background jobs are scoped per-conversation, meaning they do not persist beyond the current session and are safely terminated when limits are reached.

Can I use background process management for dev servers and file watchers?

Yes, background process management applies directly to running dev servers, file watchers, and builds within a single chat. You can start these long-running tasks asynchronously, monitor their output via polling, and stop them safely without blocking your workflow.

How does asynchronous job management handle safe process termination?

Asynchronous job management handles safe process termination by issuing SIGTERM followed by SIGKILL signals to stop background jobs. This ensures that long-running shell commands and dev servers are cleanly terminated when the 10-minute lifetime limit is exceeded or a manual stop is requested.