Approved agent catalog
Store YAML agents in Git, run them through a shared server, and let admins enforce baseline GitHub/cost policies.
Team Workflows
Shared sessions, Polly, Debby, mobile handoff, agent catalogs, and practical enterprise scenarios.
documented workflow examples inferred
Omnigent is most interesting when a team stops treating agents as isolated terminals and starts treating them as shared, governable sessions.
Pair programming and handoff
A shared session can grant VIEW or EDIT. VIEW lets teammates watch. EDIT lets them co-drive the session, which means their messages execute on the host machine. The docs explicitly warn to share EDIT only with trusted people or move the work to a cloud sandbox. Source: pair programming.
Mobile and desktop access are not side features. They are part of the same session model: start in a terminal, monitor from the browser, approve from a phone, and receive desktop notifications when an agent needs attention. Sources: terminal, mobile, desktop.
Built-in multi-AI agents
- Polly is a multi-agent coding orchestrator: she plans, delegates to coding sub-agents in parallel worktrees, routes diffs to reviewers from different vendors, and leaves merging to the user. Source: README Polly section.
- Debby is a two-headed brainstorming partner with one Claude head and one GPT head;
/debatelets the heads critique each other before converging. Source: README Debby section.
Useful organization patterns
Cross-vendor review
Use Polly-style delegation so the model that writes a diff is not the same vendor reviewing it.
Sandbox templates
Define docs-only, repo-write, and no-network OS profiles so unattended work has explicit boundaries.
These patterns are inferred from documented YAML agents, policies, sub-agents, and collaboration features. Sources: custom agents, MCP & tools, built-in policies.