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 875.9ms across 15,062 title embeddings via pgvector HNSW
- Show HN: We put voice agent on our website, learned retrieval isn't bottleneck srimalireddi · 21 pts · June 15, 2026 · 69% similar
- Show HN: Cost.dev (YC W21) – making agents cost-aware and cheaper to call akh · 29 pts · June 04, 2026 · 68% similar
- Show HN: Netlify for Agents bobfunk · 12 pts · April 22, 2026 · 67% similar
- Show HN: AgentSwarms – free hands-on playground to learn agentic AI, no setup rohan044 · 12 pts · April 26, 2026 · 67% similar
- Show HN: I built a sub-500ms latency voice agent from scratch nicktikhonov · 289 pts · March 02, 2026 · 67% 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