minion-orchestrator
Best for Multi-step agent workflowsWorks with GitHub
⌘source
- author
@garrytan- repo
- garrytan/gbrain
- language
- TypeScript
★9.1kstars
1kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Postgres-backed durable job queue for agent tasks
- ·Structured progress tracking and session transcripts
- ·Mid-flight agent steering via inbox messages
- ·Pause, resume, or cancel jobs at any time
- ·Parent-child task DAGs with failure policies
- ·Replaces in-memory spawning with observable orchestration
Use Cases
- →Spawning subagents for multi-step research or analysis
- →Running parallel tasks like fan-out research across multiple topics
- →Managing long-running background agents that need progress monitoring
- →Steering running agents when new information or direction emerges
- →Pausing and resuming agent work during system maintenance or priority shifts
Best for
- ✓Multi-step agent workflows
- ✓Parallel task execution
- ✓Production agent systems
Not ideal for
- !Single tool calls under 30 seconds
FAQs
name
minion-orchestrator
description
Manage background agents via Minions job queue. Use when: spawning subagents,
checking agent progress, steering running agents, pausing/resuming work,
parallel task execution, fan-out research. Replaces sessions_spawn for
durable, observable, steerable agents.
version:1.0.0
triggers:["spawn agent","background task","run in background","check on agent","agent progress","what's running","steer agent","change direction","tell the agent","pause agent","stop agent","resume agent","parallel tasks","fan out","do these in parallel"]
tools:["submit_job","get_job","list_jobs","cancel_job","pause_job","resume_job","replay_job","send_job_message","get_job_progress","get_job_stats"]
mutating:true
Minion Orchestrator
Contract
Minions is a Postgres-native job queue for durable, observable agent orchestration. Every background agent task goes through Minions. No in-memory subagent spawning.
Guarantees:
- Jobs survive gateway restart (Postgres-backed)
- Every job has structured progress, token accounting, and session transcripts
- Running agents can be steered mid-flight via inbox messages
- Jobs can be paused, resumed, or cancelled at any time
- Parent-child DAGs with configurable failure policies
When to Use Minions vs Inline Work
| Condition | Action |
|---|---|
| Single tool call, < 30s | Do it inline |
| Multi-step, any duration | Submit as Minion job |
| Parallel work (2+ streams) | Submit N Minion jobs with shared parent |
| Needs to survive restart | Submit as Minion job |
| User wants progress updates | Submit as Minion job with progress tracking |
| Research / bulk operation | Submit as Minion job, always |
| File imports, bulk embeds | Submit as Minion job |
Rule of thumb: If it takes more than 3 tool calls, use a Minion.
Phase 1: Submit
$install
1-click copynpx skills add garrytan/gbrain --skill minion-orchestratorSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.