Silent Background Task Execution

Silent Background Task Execution Protocol (Async Daemon Management)

Overview

When an agent starts a long-running process (e.g., npm install, a Next.js dev server npm run dev, a Docker container build, or a full database migration), executing the command synchronously blocks the client for minutes.

Synchronous execution of long tasks causes severe failures:

1. Chat UI Freezes: The user interface becomes unresponsive while streaming intermediate stdout progress bars.
2. HTTP Gateway Timeouts (504s): Long synchronous commands exceed reverse proxy socket limits (60s to 120s), aborting the task midway.
3. Turn Inefficiency: The agent cannot perform other parallel investigations while blocked on a synchronous command.

The Silent Background Task Protocol configures asynchronous daemon execution using WaitMsBeforeAsync and IsDaemon parameters - allowing commands to run silently in the background while logging to disk.

Synchronous Blocking Execution vs. Silent Background Daemon

┌─────────────────────────────────────────────────────────────┐
│                 Process Execution Dynamics                  │
│                                                             │
│  Synchronous Blocking Execution (Anti-Pattern):             │
│  • Agent runs `npm run dev` synchronously                   │
│  • Command runs indefinitely (Dev server listening on 3000) │
│  ↳ Agent freezes permanently! Tool call never returns!      │
│  ↳ UI locks up, user forced to cancel session               │
│                                                             │
│  Silent Background Daemon Protocol (`IsDaemon: true`):      │
│  • Agent runs `npm run dev` with `WaitMsBeforeAsync: 1000`  │
│  • Sync check: Verifies server starts without crash in 1s   │
│  • Process sent to background PID daemon; yields turn       │
│  ↳ 0 UI blocking, agent can immediately run browser tests   │
└─────────────────────────────────────────────────────────────┘

The 2 Background Execution Archetypes

┌───────────────────────────────────────────────────────────────────────────┐
│ 1. FINITE BACKGROUND JOB (`IsDaemon: false`):                             │
│    • Tasks: `npm install`, `pytest`, `docker build`, `cargo build`        │
│    • Behavior: Runs in background until completion, then wakes agent      │
│                                                                           │
│ 2. STANDING SUPPORT DAEMON (`IsDaemon: true`):                            │
│    • Tasks: `npm run dev`, `python -m http.server`, `docker compose up`   │
│    • Behavior: Runs indefinitely in background; does NOT wake agent       │
└───────────────────────────────────────────────────────────────────────────┘

Tool Invocation Standards

Example 1: Launching a Dev Server Daemon (IsDaemon: true)

{
  "CommandLine": "npm run dev",
  "Cwd": "c:/Users/ASUS/Documents/Newfolder/Antigravity/Major AI Skills",
  "WaitMsBeforeAsync": 2000,
  "IsDaemon": true,
  "toolAction": "Starting local Next.js development server",
  "toolSummary": "Dev Server Launch"
}

WaitMsBeforeAsync: 2000 allows the command 2 seconds to fail immediately if port 3000 is already in use. If it stays alive, it transitions silently to background daemon.

Example 2: Launching a Long Build Process (IsDaemon: false)

{
  "CommandLine": "docker build -t app:latest .",
  "Cwd": "c:/Users/ASUS/Documents/Newfolder/Antigravity/Major AI Skills",
  "WaitMsBeforeAsync": 500,
  "IsDaemon": false,
  "toolAction": "Building Docker image in background",
  "toolSummary": "Background Container Build"
}

Runs silently in background and notifies agent upon build completion.

Benchmark Comparison

Managing dev servers and container builds across 30 engineering sessions:

Agent Operational Directive

MANDATORY: For long-running builds, test suites ($>10\text{s}$), or permanent dev servers, agents must set WaitMsBeforeAsync: 500-2000. Set IsDaemon: true for dev servers and IsDaemon: false for finite jobs.