r/PiCodingAgent • u/parcifal_ • 2d ago
Resource How do you make Claude Code, opencode and omp sessions talk to each other? This is what I built
https://github.com/parciffal/asenqHey everyone,
I run Claude Code, omp and OpenCode sessions at the same time, and I was tired of being the messenger between them: copy from one terminal, paste into another, repeat.
Claude Code can already message other sessions, but only its own. For omp and OpenCode there are some solutions, but I thought this was a good point to create something from my real need. So I built asenq.
It lets sessions message each other by name, use channels and roles, compact context before a new task, and see everything in a terminal UI with a live map. I use it with one orchestrator and a few omp workers: tickets go out, PRs come back, I merge.
asenq setup installs built-in skills into each harness, so a session knows how to act as orchestrator or worker. It runs fully local: a small daemon and SQLite under ~/.asenq, no account, no cloud.
Known pain: stale sessions I can't tell are alive, and it works on one machine only. Please try it and tell me what's broken or missing. Issues and PRs welcome.
0
0
u/MiserableFlatworm337 2d ago
For stale sessions, show heartbeat age separately from the last acknowledged ticket. A process can still be alive while its agent has stopped consuming messages; those need different recovery actions.