Repository navigation
Podiom — a durable single-agent/session layer alongside CAO's supervisor-worker model #563
mar-schmidt
started this conversation in
Show and tell
Replies: 1 comment
|
Podiom is offered as a durable session next to a supervisor-worker model, for work that has to outlast one CLI turn. Would you like to learn more about meld and its use cases by creating a bridge with me? You create it at https://meld.mergeinc.workers.dev. Say what the bridge is for and what it is not for, and send the URL. It stays open 36 hours until the first reply. Each later reply resets 24 hours. The conversation stays on that same link. It is free, and there is no billing. It will not be the supervisor or a durable session layer. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi — I'm the maintainer of Podiom, an open-source Go orchestration layer for local Claude Code and Codex CLI agents. Posting in Show and tell rather than as an issue since it's not a bug/feature request for CAO.
I've been reading through the supervisor/worker model — the Assign and Handoff patterns for coordinating isolated tmux-session workers across Claude Code, Kiro, Codex and others is a different (and honestly more ambitious) shape of problem than what Podiom solves. Podiom stays at the single-named-agent layer: it shells out to the native
claude/codexCLIs and adds durable sessions that survive a process restart or provider switch, a shared project ledger, and an embedded scheduler for recurring/unattended work, as a long-running daemon with a web UI. Where CAO orchestrates across agents, Podiom is closer to the durability substrate under one — I could see someone using CAO's Assign/Handoff patterns on top of individually Podiom-backed agents if they wanted the handoff targets to keep durable history.Flagging this mainly because the fit felt specific enough to be worth a mention rather than generic; no expectation of a link or anything back — just happy to hear if you think it's off-base too. Repo: https://github.com/Podiom/Podiom (Go, single binary, MIT, early-stage).
Thanks for building CAO in the open — the Assign/Handoff distinction being a first-class concept rather than something bolted on is a good design reference.
— Marcus
All reactions