edisyl task

edisyl task <pack> "<objective>" [flags]

Research a topic and curate it in, fix what the pack covers, model new data: anything that needs the pack’s agents to go do something rather than answer or record a fact. A task, run from the CLI, can itself ask and teach as child Actions.

Flags

Flag	Behavior
--fast	Run a single direct executor on a bounded objective, instead of the default coordinated fleet (planner → specialists).
--wait	Block until the Action is terminal.
--id-only	Print the bare Action id for scripting.
--cron "<expr>"	Make this a recurring scheduled task. 30-minute minimum interval.
--at <RFC3339>	Run this task once, at a future time.
--name <label>	Optional human label for a schedule.
-j, --json	Machine-readable output.

Default behavior: the coordinated fleet

By default, task runs the pack’s coordinated fleet: a planner delegates to specialists, models tables, and enriches the semantic layer so the next ask lands.

action_id=$(edisyl task "$PACK" "Model the wallet/swap tables so 'active wallets' resolves." --id-only)
edisyl action watch "$action_id"      # narrates the plan and each step as it moves
edisyl action plan <action-id>        # the board on demand
edisyl action events <action-id>      # raw event tail, for diagnosis
edisyl action get <action-id>         # summary + artifacts once terminal

Task outcomes

A task can produce a report, an artifact, an external action (when explicitly authorized), a proposed change requiring review, or new understanding, but only when explicitly requested via teach. Task completion never silently mutates pack understanding:

"Research competitor pricing and report back."       → a result only
"Research competitor pricing and teach the findings." → a result, and a teach on the same pack

Recurring tasks

Add --cron or --at to make any task a schedule. See Scheduling recurring work and schedule.