Menu
Use when you have a goal to work toward across multiple turns, or when the user asks you to own a task and keep going without waiting for input.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 starting, inspecting, rerunning, following up, or cancelling durable background commands or subagents.
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.
| name | goal-mode |
| description | Use when you have a goal to work toward across multiple turns, or when the user asks you to own a task and keep going without waiting for input. |
| metadata | {"id":"goal-mode","title":"Goal Mode","summary":"Set one objective and let the system automatically continue until it is met.","status":"active"} |
| tools | ["goal"] |
Use this skill when you have a sustained objective that may span multiple turns.
Goal mode is a single active objective. The system injects the current objective into continuation turns and automatically schedules another turn while the goal is active.
goal(objective: "...") — enable goal mode or replace the active objective.goal(status: "pause") — pause the active objective without losing it.goal(status: "resume") — resume a paused objective.goal(status: "complete") — disable goal mode when the objective is met.The system automatically schedules a visible goal-continuation block after each turn while the goal is active, then uses it to trigger the next turn.
goal with an objective while goal mode is active replaces the objective and keeps goal mode running.conversation deferred resume, then call goal with status: "pause". Include instructions in the deferred resume prompt to call goal with status: "resume" when work should continue.goal { status: "complete" } only when the objective is actually achieved.If goal-mode turns produce no tool calls for two consecutive turns, goal mode is disabled with stopReason: "no progress" so it cannot spin forever. Starting, updating, or completing a goal resets this.
Queued continuations are cancelled or ignored when the goal changes or completes, and duplicate completion calls are treated as no-ops. Completing a goal does not abort the current turn; it prevents the agent-end scheduler from queuing another continuation. Turn-end events only update progress counters, so tool-heavy runs cannot stack stale continuations before completion. Goal mode should end quietly once the objective is complete.