ワンクリックで
background-work
Use when starting, inspecting, rerunning, following up, or cancelling durable background commands or subagents.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when starting, inspecting, rerunning, following up, or cancelling durable background commands or subagents.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when deciding between follow-up queues, scheduled callbacks, automation-owned attention, wakeups, and async follow-up surfaces.
Use when a task benefits from JavaScript orchestration, explicit phases, structured progress logs, parallel fanout, or multiple daemon-backed subagents coordinated through the workflow tool.
Use when designing, creating, editing, building, validating, installing, or debugging Neon Pilot extensions, application pages, contributions to existing applications, or complete first-class applications from the bundled desktop app. This skill is self-contained and must be used without a Neon Pilot source checkout.
Use when working with the built-in desktop Workbench Browser, browser comments, browser snapshots, CDP actions, screenshots, or the browser versus agent-browser boundary.
Use the unified Neon Pilot CLI/control plane for self-administration, delegated agent control, conversations, workspace/sidebar state, runs, automations, extensions, settings, and extension-contributed administration surfaces.
Use when installing, inspecting, or explaining Codex and Claude Code style agent plugins in Neon Pilot.
| name | background-work |
| description | Use when starting, inspecting, rerunning, following up, or cancelling durable background commands or subagents. |
| metadata | {"id":"runs","title":"Background Work","summary":"Built-in guidance for detached background commands, subagents, inspection, and follow-up behavior.","status":"active"} |
| tools | ["bash","background_bash","subagent","the unified conversation deferred-resume admin command"] |
Use intent-shaped tools. For waiting/resuming this conversation later, use the unified conversation deferred-resume admin command; do not run sleep in bash.
| Tool | Use case |
|---|---|
bash | Shell commands; set background: true for durable background commands. |
background_bash | Lifecycle tool for background command records. |
subagent | A delegated agent task that should run durably outside the current turn. |
scheduled_task | A persistent automation with a cron/time trigger and delivery policy. |
| the unified conversation deferred-resume admin command | Continue this same conversation later. |
Completion delivery is the normal “wake me when this finishes” path. If a background command/subagent uses deliverResultToConversation: true, do not also schedule a the unified conversation deferred-resume admin command merely to check whether it finished. Only schedule a separate wakeup for a distinct time-based action that should happen regardless of completion timing, and include a clear reason.
For Neon Pilot administration from shell, prefer the CLI equivalents:
neon-pilot background-commands list --json
neon-pilot background-commands start --command "pnpm test" --cwd /repo --json
neon-pilot background-commands logs <run-id> --tail 200 --json
neon-pilot background-commands cancel <run-id> --json
Start a detached command with bash:
{
"command": "npm test",
"background": true,
"taskSlug": "tests",
"cwd": "/path/to/repo"
}
Use get, logs, rerun, and cancel for lifecycle management.
Start delegated agent work:
{
"action": "start",
"taskSlug": "review-diff",
"prompt": "Review the current diff and summarize the risks.",
"cwd": "/path/to/repo"
}
Use follow_up to continue a stopped subagent and get, logs, rerun, and cancel for lifecycle management. Do not use background_bash on subagent IDs.
The product UI should say Background commands and Subagents. Treat “run” as the durable storage record only.