unohee

3 ms·

1. 1.▲
   by unohee 7mo ago

   OpenSwarm isolates context at the agent level — each worker is spawned via Claude Code’s -p flag, so there’s no shared conversation history between agents. The only shared state is written artifacts and a global work memory layer (CLAUDE.md
2. 2.▲
   by unohee 7mo ago

   For the collaboration between two different models — I’d love to explore that. Expanding model compatibility to broader providers (Codex, Aider, and other API models) is already on my roadmap. I’m planning to add a reviewer feature that sup
3. 3.▲
   by unohee 7mo ago

   For the current build, OpenSwarm uses max retry count with an escalation scheme: the first worker starts with Haiku, and if the tester/reviewer blocks enough times, it escalates to Sonnet. Each pipeline step updates Linear's updat
4. 4.▲
   by unohee 7mo ago

   Kind of. My point is that agent orchestrators become actually useful when the framework is specific about what's safe to delegate to machines — things that reduce friction in CI/CD operations, not agents that shoot iMessages, clic
5. 5.▲
   by unohee 7mo ago

   The worker-reviewer pipeline typically runs 1–2 self-revision iterations. In my experience, agents handle most tasks fine, but they tend to miss quality gates — docstrings, minor business logic edge cases, that kind of thing. The reviewer c
6. 6.▲
   Show HN: OpenSwarm – Multi‑Agent Claude CLI Orchestrator for Linear/GitHub(github.com)

   34 points by unohee 7mo ago|17 comments