foxctl-orchestrate

Orchestrate durable multi-agent workflows with lifecycle control and session persistence.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-orchestrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: foxctl-orchestrate
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-orchestrate
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-orchestrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you coordinate multi-step AI work without losing state, by tracking tasks and sessions while routing messages between long-lived agents.

Core Features & Use Cases

  • Durable task + session tracking: Keep work organized as tasks progress and restore prior context in later runs.
  • Mailbox/inbox coordination: Route overseer and agent communication through inbox-style message flows for human-in-the-loop control.
  • Agent spawn/query/kill orchestration: Create persistent daemon agents, ask them for results, and manage their lifecycle within a room or workflow.

Quick Start

Run foxctl-orchestrate to spawn an overseer and coordinate sub-agent research and responses for a sustained code review workflow with durable context.

Frequently Asked Questions about foxctl-orchestrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multi-agent workflows without losing context?▼

Multi-agent workflows are coordinated through durable session tracking and mailbox inboxes, routing messages between persistent agents to restore and preserve state across multi-step execution.

How do I spawn persistent agents for long-running tasks?▼

Spawn persistent agents by using lifecycle control operations to create daemon agents, query them for results, and manage their execution within a specific room or workflow over time.

What is mailbox-based message routing for agent coordination?▼

Mailbox-based message routing directs overseer and agent communication through inbox-style message flows, enabling human-in-the-loop control and coordination over complex multi-agent development work.

Does multi-agent orchestration require specific agent lifecycle support?▼

Yes, it requires support for agent lifecycle control, including spawn, ask, list, and kill operations, alongside mailbox operations and session persistence for deterministic task execution.

Can I restore prior session context in later runs of a task?▼

Yes, durable task and session tracking keeps work organized as tasks progress and restores prior context in later runs, allowing sustained workflows to resume without losing state.

When should I use durable multi-agent orchestration for development work?▼

Use durable multi-agent orchestration for sustained code review workflows, spawning persistent research and coder agents, and managing room coordination across multi-step execution over time.