craig-cli 0.13.4 → 0.14.0

package/README.md

@@ -141,14 +141,12 @@ craig task new --workspace <workspace-id> [--runner codex|cursor|claude] "<task>
 craig task list
 craig task list --repo <repo-id>
 craig task show <task-id>
-craig task attach <task-id>
-craig task focus <task-id>
 craig task open <task-id>
 craig task logs <task-id>
 craig task diff <task-id>
 craig task check <task-id>
 craig task commit <task-id>
-craig task create-child --parent <task-id> --repo <repo-id> [--runner codex|cursor|claude] \
+craig task create-child --parent <task-id> [--repo <repo-id> | --workspace <workspace-id>] [--runner codex|cursor|claude] \
   [--idempotency-key <key>] "<task>" --json
 craig task children [<task-id>] --json
 craig task cancel-tree [<task-id>] --json
@@ -211,11 +209,15 @@ Optional workspace-local config at `.craig/config.json`:
 
 Feature previews are experimental, workspace-local, and off by default. They can also be toggled from Options > Feature Previews in the TUI.
 
+### Cursor workspace trust
+
+Cursor may ask separately whether to trust each Craig-managed worktree or project task bundle. To establish trust once at their common parent, open `~/.craig` in Cursor and approve its workspace trust prompt. Trust only that directory if you are comfortable allowing Cursor agents to work throughout Craig's local task state. Craig does not pass Cursor's `--trust` flag or otherwise weaken the runner's safety settings. For narrower project-only testing, opening `~/.craig/task_bundles` limits the trusted parent to project bundles but does not cover repo worktrees under `~/.craig/worktrees`.
+
 An interactive Craig launched from inside an agent session will not implicitly attach to that agent's live workspace. Pass `--workspace-root <live-root>` to confirm that attachment, or create and pass a different directory for an isolated blank workspace. A client also refuses to replace a live PTY daemon that uses an incompatible protocol; exit the other Craig instance before restarting explicitly.
 
-Event commands, new prompt dispatch creation, child-task creation, and fury validation/planning require the `agentOrchestration` preview. Preview-enabled agent PTYs receive an opaque workspace-local capability token scoped to their own task, the stable delegation command families, an expiry, and bounded child/depth/concurrency/prompt limits; only a non-authorizing reference is stored on the task. Fury operations reuse that scoped token according to each command's preview and recovery policy without persisting preview-only command families into the base capability record, so stable Craig can still read the workspace after preview use. `task children` and idempotent `task cancel-tree` remain available when the preview is disabled so existing lineage can be inspected and safely stopped. Craig may still maintain durable semantic events internally for stable daemon services such as pull request synchronization. Disabling the preview stops new dispatch and child creation but leaves command inspection, waiting, cancellation, and safe reconciliation available for existing durable work. Prompt delivery defaults to `when-ready`; `immediate` explicitly interrupts a busy target.
+Event commands, new prompt dispatch creation, child-task creation, and fury validation/planning require the `agentOrchestration` preview. Preview-enabled agent PTYs receive an opaque workspace-local capability token scoped to their own task, the stable delegation command families, an expiry, and bounded child/depth/concurrency/prompt limits; only a non-authorizing reference is stored on the task. Fury operations reuse that scoped token according to each command's preview and recovery policy without persisting preview-only command families into the base capability record, so stable Craig can still read the workspace after preview use. `task create-child` inherits the parent target when neither `--repo` nor `--workspace` is supplied: project parents create project children, while repo parents create children in the same repo. An explicit repo child of a project task stays owned by that project workspace, so it does not require a separate standalone repo workspace. `task children` and idempotent `task cancel-tree` remain available when the preview is disabled so existing lineage can be inspected and safely stopped. Craig may still maintain durable semantic events internally for stable daemon services such as pull request synchronization. Disabling the preview stops new dispatch and child creation but leaves command inspection, waiting, cancellation, and safe reconciliation available for existing durable work. Prompt delivery defaults to `when-ready`; `immediate` explicitly interrupts a busy target. Craig sends a dispatched prompt and its submit key as separate terminal input events so the submit key cannot be consumed as part of the bracketed paste. A delegated child starts in a daemon-owned agent session immediately and selecting that child in the TUI attaches to the same process.
 
-Fury definitions are strict, versioned YAML DAGs stored under `.craig/fury/`. `fury validate` checks the schema, limits, templates, references, dependencies, output schemas, and human-review checkpoints without mutating runtime state. `fury plan` resolves declared inputs, binds the graph to a planning task, persists an immutable content-hashed plan, and requests human sign-off.
+Fury definitions are strict, versioned YAML DAGs stored under `.craig/fury/`. A `create_child` step can specify `repo`, specify `workspace`, or use an empty mapping (`create_child: {}`) to inherit its planning parent's target. `fury validate` checks the schema, limits, templates, references, dependencies, output schemas, and human-review checkpoints without mutating runtime state. `fury plan` resolves declared inputs, binds the graph to a planning task, persists an immutable content-hashed plan, and requests human sign-off.
 
 Only a human can `fury approve` the exact plan hash. `fury run` accepts only an approved plan id, creates at most one run for that approval, and schedules every new task as a direct child of the planning task; graph dependencies never create visual grandchildren. Every agent step must explicitly call `fury step complete` or `fury step fail`; terminal silence is never success. Declared outputs are JSON-schema validated before dependents can run. Human-review steps remain blocked until an attributable human approval, while request-changes routes durable feedback to the declared task and requires an explicit resubmission. The sidebar shows one flat Fury attention row when plan or review approvals are waiting. The heartbeat reconciles interrupted dispatch, deadlines, missing agent sessions, and pending work. Retries, conditions, fan-out, and recursive Fury runs remain deferred.