ao-orchestrator
PulseGate's liveness check found it on 5 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 4 Sep 2026. How this is checked
ao-orchestrator attaches to an existing coding agent to monitor its activity, restart it, verify its work, and determine which changes may be committed. It is distributed as an MIT-licensed Python package for developers working with coding agents.
Inferred · not functionally tested
Overview
5 featuresPurpose: Managing and validating coding-agent work before changes are committed.
Inferred · not functionally tested
Audience: developers using coding agents
Inferred · not functionally tested
Functions: agents, monitoring, workflow_automation
Inferred · not functionally tested
Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
ao-orchestrator sits in PulseGate's Agent monitoring & governance category. Inferred · not functionally tested: It focuses on managing and validating coding-agent work before changes are committed. Inferred · not functionally tested: It is built as an open-source project for developers using coding agents. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: ao-orchestrator is available on the command line, and it can be self-hosted.
It is developed by Hakki Sagdic, and it first shipped in 2026. Development happens publicly on GitHub with 53 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are agent monitoring, agent restart, and work verification. Basis unknown · not verified: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Agent monitoring
- Agent restart
- Work verification
- Commit approval
- Coding-agent attachment
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
2What PulseGate has recorded for this listing
- Indexed4 Sep · 14:19 UTCao-orchestrator seen via PyPI Bulk EnumeratorSource: PyPI Bulk Enumerator · Open
Frequently asked questions about ao-orchestrator
- What does ao-orchestrator do?
- Inferred · not functionally tested: Ao-orchestrator focuses on managing and validating coding-agent work before changes are committed. It is catalogued under Agent monitoring & governance on PulseGate.
- Who should use ao-orchestrator?
- Inferred · not functionally tested: ao-orchestrator is an open-source project built for developers using coding agents.
- Is ao-orchestrator free?
- Basis unknown · not verified: Yes — ao-orchestrator is open source under the MIT license and free to use.
- What platforms does ao-orchestrator run on?
- Basis unknown · not verified: ao-orchestrator runs on the command line. It can also be self-hosted.
- Is ao-orchestrator still maintained?
- PulseGate's liveness check found it on 5 Oct 2026. Its GitHub repository shows 53 commits in the last 90 days.
- What projects are similar to ao-orchestrator?
- Similar projects tracked by PulseGate include joe-orchestrator, ai-agent-orchestrator, and agent-orchard.joe-orchestratorai-agent-orchestratoragent-orchard
- Who develops ao-orchestrator?
- ao-orchestrator is developed by Hakki Sagdic.
- When did ao-orchestrator launch?
- ao-orchestrator first shipped in 2026.
Similar projects
Closest matches by what these projects do