Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getpioneer.dev/llms.txt

Use this file to discover all available pages before exploring further.

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, 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.

​
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.