Get the comprehensive usage guide for agent-pool with examples and best practices. Call this FIRST when planning how to use agent-pool tools for parallel work, pipelines, or scheduling. Returns practical examples for each feature area.

Available topics: delegation, pipelines, scheduling, skills, peer-review, sessions. Omit topic to get the full guide.

Delegate a coding task to a CLI agent running in headless mode. The agent is sandboxed to cwd directory only. Use include_dirs to grant access to additional directories. Use this for parallel work: code review, testing, refactoring, analysis, or any dev task.

Returns a task_id immediately (non-blocking). Use get_task_result to check status and retrieve the result.

IMPORTANT: CLI providers can take ~15-20s before the agent begins working. Set timeout to at least 60s for simple tasks, 300s+ for complex analysis. WORKSPACE: The agent can only use file tools within cwd and include_dirs. For other paths it can use shell commands (cat, find, ls).

Delegate a read-only analysis task to a CLI agent. The agent is sandboxed to cwd directory only. Use include_dirs to grant access to additional directories. It is semantically identical to delegate_task but signals that the task is primarily for analysis. Use this for code review, architecture analysis, finding bugs, writing reports, etc.

Returns a task_id immediately (non-blocking). Use get_task_result to check status and retrieve the result.

IMPORTANT: CLI providers can take ~15-20s before the agent begins working. Set timeout to at least 60s for simple tasks, 300s+ for complex analysis. WORKSPACE: The agent can only use file tools within cwd and include_dirs. For other paths it can use shell commands (cat, find, ls).

Antigravity-backed peer consultation for architectural/technical consensus. For Codex orchestration, prefer delegate_task_readonly with resource_group: "review". Use during PLANNING phase to validate proposals before implementation. Supports iterative rounds: send proposal, get feedback, revise, resend until AGREE. The peer responds with a structured verdict: AGREE, SUGGEST_CHANGES, or DISAGREE.

Returns a task_id immediately (non-blocking). Use get_task_result to check the verdict. The peer runs without a timeout — it will work until done. Progress is visible via get_task_result.

Check the status and result of a background task started with delegate_task, delegate_task_readonly, or consult_peer. Completed results remain available until TTL cleanup, so multiple callers can retrieve the full report.

Cancel a running task and kill its process. Use when a task is stuck or no longer needed.

Close a task lifecycle and clean up tracked child processes. Running tasks are cancelled by default; completed tasks keep their result unless remove_from_memory is true.

Release a capacity slot in the cross-process slot ledger for a given admission_id. Best-effort and idempotent: an unknown or already-released admission returns released:false with ok:true. The board calls this when a workflow step closes so the slot frees immediately instead of waiting for the dead-pid sweep.

List available Antigravity CLI conversations for a project directory when the CLI exposes them. Use session_id with delegate_task to resume.

List all background tasks currently running or recently completed in the agent pool memory.

Return a compact dynamic context plan for a task. Classifies zones, recommends tool profile, and returns matching skill/workflow indexes without loading full markdown.

List global CLI skills plus skills from the active team-memory workspace//skills directory.

Return one global or active workspace skill with metadata and markdown content. Use after resolve_context returns a skill item that needs atomic loading.

Create or update an active workspace CLI skill under team-memory workspace//skills/.

Delete an active workspace CLI skill by name from team-memory workspace//skills/.

Reserved for future external skill installation. Workspace skills are managed in team-memory workspace//skills/ or through the Agent Portal UI.

Schedule a CLI agent to run on a cron schedule or as a delayed one-shot. Default provider: Codex CLI. Spawns a persistent daemon that survives IDE/CLI restarts. Results are saved in local portal project state and can be retrieved with get_scheduled_results.

Cron format: standard 5-field (minute hour day month weekday). Examples: "*/30 * * * *" (every 30 min), "0 9 * * MON-FRI" (9am weekdays), "0 */2 * * *" (every 2 hours).

List all scheduled tasks with their cron expressions, next run times, and daemon status.

Cancel a scheduled task by ID. Removes it from the schedule. The daemon will auto-exit when no schedules remain.

Get results from scheduled task executions. Returns the last 20 results, newest first.

Create a pipeline definition with sequential steps.

Start executing a pipeline.

List all pipeline definitions.

Get status of a pipeline run.

Cancel a running pipeline.

Signal that a pipeline step is complete (called BY agents running inside pipeline steps).

Return task to a previous pipeline step with feedback about missing/insufficient data.

Create a named agent group with shared runtime config. Groups are reusable presets for fractal orchestration.

List all registered agent groups with their config.

Delete a named agent resource group.

Delegate a task to a named agent group. Spawns agents with the group's shared config (runner, skill, policy). Use count to launch multiple agents in parallel (fractal orchestration).

Returns array of task_ids immediately (non-blocking). Use get_task_result to check each.

Send a message to a channel for inter-agent communication. Use this to pass structured data between pipeline steps or between any agents.

Channel conventions:

• {run_id} — broadcast to all steps in a pipeline run

• {run_id}:{step_name} — targeted to a specific step

• any string — ad-hoc channel for custom messaging

Messages are persisted to disk (survives restarts). Uses JSONL format for concurrent-write safety.

Read messages from a channel. Returns all messages in chronological order.

Channel conventions:

• {run_id} — read broadcast messages for a pipeline run

• {run_id}:{step_name} — read messages targeted to a specific step

Use clear=true to consume messages (delete after reading).

Save a local automation script to the team-memory scripts/ directory. This is useful for zero-token execution nodes.

List all locally saved automation scripts.

Track active files in local portal project state. Useful to persist file context between pipeline steps.

Remove files from the active tracking context.

Return active files tracked in the current project context.

List global workflows plus workflows from the active team-memory workspace//workflows directory.

Find workflow steps matching all tags. Returns full content for one match and a lightweight list for multiple matches.

Return markdown content and transition metadata for one workflow step node.

Get the current state of the Agent Board (tasks and delegation tree).