Skip to main content
Threads are good when you are present and steering the work. Tasks are for work that has a shape of its own. A task can run manually, on a schedule, after another task, or as part of a larger workflow. The gateway owns the run, so tasks can keep working in the environment where the gateway lives. That makes tasks especially useful on remote gateways. A server can run a morning research pass, check a repository, prepare a summary, or coordinate several smaller agent steps without depending on your laptop being open.

​
Start With Boring Tasks

Your first task should be simple and read-only: 
Summarize the current workspace and list any obvious setup issues. Do not modify files.
Run it manually. Read the result. Open the timeline. Check which tools were called and what the agent saw. Only after that should you add schedules, write access, dependencies, or multi-agent workflows. A task that runs by itself deserves more caution than a thread you are watching.
Task tools run on the gateway host and are not sandboxed yet. A scheduled task has the same practical access as the gateway OS user.

​
Subagents

Pioneer can create subagents automatically as part of a task workflow. You do not have to manually delegate every piece of work. A task can define the prompt, model, context policy, tool policy, result expectations, review policy, and child-thread behavior for agents that run under it. Pioneer can then break work into smaller parts and attach the results back to the parent task. This is useful when one large job needs several focused passes: gather information, inspect files, draft a result, verify it, and report back. The important part is that each agent has a clear job and a clear result contract. Subagents run in hidden child threads. The child thread gives the subagent a normal agent environment with its own timeline, tools, context, and artifacts. The parent thread still owns the workflow: it creates the task, waits for the result, reviews the candidate output, and decides what happens next.

​
Parent Review And Revisions

Attached subagent tasks do not have to become final just because the child agent stopped. When a subagent finishes a turn, Pioneer stores the output as a result candidate. The parent agent can then:
  • accept the candidate when it satisfies the task;
  • request a revision from the same subagent with concrete feedback;
  • cancel the task when the result should not be used.
When the parent requests a revision, Pioneer records the rejected candidate, sends the feedback back into the same child thread, starts a new revision turn, and waits for a new candidate. The cycle can repeat up to the configured revision limit. The default parent-agent review policy allows up to five revision rounds. This makes multi-agent work auditable. You can see the first answer, the parent feedback, the revised answer, and the final accepted candidate instead of losing rejected work in a mutated final result. Scheduled and detached work is treated differently from foreground attached delegation. Those runs should not get stuck waiting for a parent turn that is no longer active, so they can be finalized automatically according to their task policy.

​
Subagent Artifacts

Files created by subagents are still workspace artifacts when the subagent registers them. The artifact is bound to the child thread and task lineage, and the parent thread can list artifacts created anywhere in its delegated child-thread tree. If a subagent says it created a file but the file is missing from the artifacts panel, the file was probably written as an ordinary gateway file and not registered with artifact_register.

​
Where Task Work Happens

Tasks run on the gateway. If the gateway is local, task tools run locally. If the gateway is remote, they run on the remote host. This affects file paths, credentials, network access, installed commands, and side effects. Before scheduling a task, make sure you are on the gateway where you actually want the work to happen.

Scheduling Tasks

Run tasks manually or on a schedule.

Automation Workflows

Connect tasks, dependencies, and subagents.