Goal System

Goals are persistent objectives that survive across sessions. They give your agent long-term direction and can trigger automatic continuation runs with budget tracking.

Goal Lifecycle

A goal moves through these states: set (active objective), paused, resumed, done (completed), or cancelled. Goal state is durable -- restarting the server preserves it.

CLI Commands

# Set a new goal
jaw goal set "Migrate the auth module to JWT tokens"

# Check goal status
jaw goal status

# Pause the current goal
jaw goal pause

# Resume a paused goal
jaw goal resume

# Mark goal as done (this is an API call, not a CLI command)
jaw goal done

# Cancel the goal
jaw goal cancel

# Reset goal state
jaw goal reset

Slash Commands

Command	Description
`/goal set <objective>`	Set a new goal objective
`/goal status`	Show current goal state
`/goal run start`	Start a bounded auto-continuation run with budget tracking
`/goal run stop`	Stop the current goal run
`/goal pause`	Pause the goal
`/goal resume`	Resume a paused goal
`/goal done`	Mark the goal as completed
`/goal cancel`	Cancel the goal
`/goal clear`	Clear goal state
`/goal reset`	Full reset

Goal Run (Auto-Continuation)

The /goal run start command begins a bounded auto-continuation session. The agent works toward the goal objective, automatically continuing after each response until the goal is marked done or the run is stopped.

Budget enforcement is currently tracking-only. The system tracks run duration and continuation count but does not yet enforce hard budget limits.

Goal Mode Rules

Goal is the supreme rule. When a goal is active, it supersedes PABCD phase gates. The agent self-advances through all phases without waiting for user approval.
Completion audit. Before /goal done, the agent must perform a requirement-by-requirement verification. Uncertain or indirect evidence is treated as "not achieved."
Blocked audit. The agent can only declare "blocked" after the same blocking condition repeats for 3 consecutive goal turns. Hard/slow/uncertain work is never a valid reason to block.
Documentation. Progress is documented in jawdev style (devlog/_plan/ with decade numbering) at each milestone.

API Endpoints

Method	Path	Description
GET	`/api/goal`	Get current goal state
GET	`/api/goal/history`	Get goal history
POST	`/api/goal`	Set, update, complete, cancel, pause, or resume a goal
GET	`/api/goal-run`	Get current goal-run state
GET	`/api/goal-run/preflight`	Preflight check before starting a run
POST	`/api/goal-run`	Start, pause, resume, or stop a goal run

WebSocket Events

Goal lifecycle changes emit WebSocket events that the Web UI consumes:

goal_done -- goal completed
goal_cancel -- goal cancelled
goal_continuation -- auto-continuation triggered
goal_continuation_failed -- continuation attempt failed
goal_continuation_limit -- continuation budget reached

Goal + PABCD Integration

Goals work alongside PABCD orchestration. You can set a goal and then use PABCD phases to break it down. Goal continuation is allowed during active PABCD phases, so the agent can keep working on goal-driven tasks within the orchestration framework.

Try it:

이 목표 설정해줘
목표 완료 처리해줘
목표 상태 보여줘

PABCD Skills