Omnigent: A Meta-Harness to Combine, Control and Share Your Agents
fanzeyi
12 points
3 comments
June 13, 2026
Related Discussions
Found 5 related stories in 125.0ms across 10,416 title embeddings via pgvector HNSW
- Meko: The Data Infrastructure for Agents That Work and Learn Together harisund1990 · 14 pts · May 07, 2026 · 61% similar
- Agent-harness-kit scaffolding for multi-agent workflows (MCP, provider-agnostic) enmanuelmag · 76 pts · May 07, 2026 · 60% similar
- Is Grep All You Need? How Agent Harnesses Reshape Agentic Search Anon84 · 138 pts · June 09, 2026 · 57% similar
- Show HN: Agent Orchestrator, a local-first Harness Engineering control plane gpgkd906 · 12 pts · March 29, 2026 · 56% similar
- Show HN: Airbyte Agents – context for agents across multiple data sources mtricot · 109 pts · May 05, 2026 · 56% similar
Discussion Highlights (2 comments)
dpbrinkm
I can see this being useful if only for the fact I can search all my conversations with my 50 different agents on different providers easier. I spend so much time looking through my cc/codex session or the desktop app or Hermes agent or antigravity session (back when I used that). Hopefully having a layer above will abstract that away. If I understand it correctly the meta harness will help me scan across all sessions and not have to drop into individual ones.
saj1th
Been exploring loop engineering. Addy Osmani has a good post on it: https://addyosmani.com/blog/loop-engineering/ The hard part of loop engineering IMO is the machinery around it, and omnigent sits above pi, claude, codex, etc. and wraps each in a uniform api. The things it adds are exactly that machinery. - Parallel git worktrees so concurrent agents don't step on each other. - Approval and cost policies enforced at the harness layer rather than living in a prompt the agent can talk its way around. - A maker/checker split where the reviewer can run on a different vendor than the writer, which is a more honest check than a second pass from the same model with the same blind spots.