Repo and docs research
Split broad read-only investigation into evidence-backed worker packets.
AGENTFANOUT
Provider-agnostic fanout for safer multi-agent work.
AgentFanout is a portable orchestration skill and deterministic advisory router for teams building agent runtimes that need bounded workers, validation, and main-session control.
WHAT_IS_AGENTFANOUT
AgentFanout is an advisory router, not a worker dispatcher.
AgentFanout classifies work, applies hard safety gates, shapes compact worker packets, and tells a host runtime when fanout is worth the overhead. The host runtime still launches workers through its own mechanism.
Bounded worker packets
Workers receive scoped tasks instead of full private context or session authority.
Deterministic routing
The router returns advisory JSON for provider choice, fanout size, validation, and dispatch requirements.
Main-session control
Secrets, private tools, git state, destructive actions, and final synthesis stay in the main session.
USE_CASES
Built for agent runtimes that need controlled parallelism.
Review and validation
Route independent checks to validators before the main session integrates the result.
Provider-aware routing
Use Codex, Claude, MiniMax, local LLMs, or future adapters without making one provider the orchestration core.
QUICKSTART
Install as a portable skill and run the router directly.
AgentFanout is currently v0.1.1. It is published as an MIT-licensed public repository with CI, security policy, release notes, and a documented public release gate.
$ cp -R AgentFanout "$HOME/.pai/skills/AgentFanout"
$ python3 scripts/route.py "review twenty independent modules"
$ python3 tests/run_tests.py
RELATED_TOPICS
AgentFanout search context.
FAQ
Clear boundaries for searchers and agents.
Does AgentFanout launch workers?
No. AgentFanout provides routing policy, worker packet shaping, safety gates, and validation requirements. The host runtime launches workers.
Which providers does AgentFanout support?
AgentFanout is provider-agnostic and includes adapter guidance for Codex, Claude, MiniMax, local LLMs, and future runtimes.
What stays main-session only?
Private tools, credentials, git state, destructive operations, and final synthesis remain controlled by the main session.
Where is the source code?
The public source is maintained on GitHub at SynapseGrid-Labs/AgentFanout with release notes, security policy, and contribution guidance.