Show HN: A lightweight way to make agents talk without paying for API usage
juanpabloaj
23 points
5 comments
April 20, 2026
Related Discussions
Found 5 related stories in 73.4ms across 5,012 title embeddings via pgvector HNSW
- Show HN: I built a sub-500ms latency voice agent from scratch nicktikhonov · 289 pts · March 02, 2026 · 67% similar
- Show HN: I put an AI agent on a $7/month VPS with IRC as its transport layer j0rg3 · 174 pts · March 26, 2026 · 65% similar
- Show HN: Real-time observability for coding agents vtemian · 14 pts · March 17, 2026 · 63% similar
- Show HN: Hyper – A stupidly non-corporate voice AI app for IRL conversations shainvs · 16 pts · March 11, 2026 · 62% similar
- Show HN: Agent Action Protocol (AAP) – MCP got us started, but is insufficient hank2000 · 11 pts · March 03, 2026 · 61% similar
Discussion Highlights (4 comments)
swingboy
I put together a skill to do this with OpenCode and the GitHub Copilot provider. Works pretty well.
pitched
I’ve been keeping them open in tmux and using either send_keys or paste buffer for communication. Using print mode and always resume last means you can’t have parallel systems going.
scalefirst
Have you seen https://www.roborev.io/ from Wes McKinney?
dragonfax
Claude Code (subscription) has Agent Teams built in. Teams of Agents communicate with local files that they use as inboxes and task list. Has tmux and iTerm 2 integration. https://code.claude.com/docs/en/agent-teams They can rack up some extra tokens if you leave agents going idle. Because they loop, checking for new messages for them. This fellow reverse-engineered exactly how it works and then abstracted the pattern into an MCP server that any Harness/agent can use. https://github.com/cs50victor/claude-code-teams-mcp