Alternatives
Products that do what Repowire does
Peer-to-peer mesh for AI coding agents
- 1
- 2
- 3
- 4
- 5
- 6
Open-source unified interface for agent harnesses
22d ago · harnessrouter.ai
- 7
- 8
- 9
Deep Work Plan▲114Models matter. Context matters more. Give your agent a plan.
Jun 2026 · deepworkplan.com
- 10
- 11
- 12PA
Hey HN. http://peerd.ai is an AI agent harness that lives entirely in your browser as a web extension. You don’t have to install a separate “AI browser”. You don’t have to bolt on or run some external process or manage a clunky mcp integration. It’s just a fully contained web extension, written in no build vanilla JS with minimal non-browser dependencies, using your own provider keys, and Apache 2. This isn’t just a fun hack. While it has largely been a solo side project, I genuinely believe the browser and the web could be the most natural platform for AI agents to operate safely,…
Jun 2026 · github.com
- 13
- 14
- 15
- 16RA
Hi HN, We're excited to share repo2vec: a simple-to-use, modular library enabling you to chat with any public or private codebase. It's like Github Copilot but with the most up-to-date information about your repo. We made this because sometimes you just want to learn how a codebase works and how to integrate it, without spending hours sifting through the code itself. We tried to make it dead-simple to use. With two scripts, you can index and get a functional interface for your repo. Every generated response shows where in the code the context for the answer was pulled from. We also made it…
2024 · github.com
- 172C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 18WB
At Metabase, we built an AI agent called Repro-Bot that reads our GitHub issues and attempts to reproduce reported bugs automatically. It started as a hackathon project and is now part of our daily workflow, so we wrote about it and open-sourced the code as an example for others. How have similar tools been working for you? What has worked well and what has not?
Apr 2026 · metabase.com
- 19
- 20MC
Hello HN, we're Jeet and Husain from Modulus (https://modulus.so) - a desktop app that lets you run multiple coding agents with shared project memory. We built it to solve two problems we kept running into: - Cross-repo context is broken. When working across multiple repositories, agents don't understand dependencies between them. Even if we open two repos in separate Cursor windows, we still have to manually explain the backend API schema while making changes in the frontend repo. - Agents lose context. Switching between coding agents often means losing context and repeating the…
Mar 2026 · modulus.so
- 21
Helping Agents and Human Orchesterators read the same notes.
Mar 2026
- 22OA
We were both genuinely impressed by Claude Code after it helped each of us fix nasty CI problems overnight. Doing those fixes manually would have taken days. After that experience, we each found ourselves struggling through Ctrl+Tab through multiple Claude Code windows in our terminals. While we enjoyed having agents working for us in parallel, context switching and cycling through each terminal tab was a real pain. So we thought: Can we design a TUI dashboard that manages a large swarm of agents in one place? Even better, can agents manage agents hierarchically, like how companies work?…
May 2026 · omar.tech
- 23
- 24DS
Hi HN! Today me and qianli_cs want to share a new open-source project we've been working on called Durable Swarm. It's a drop-in replacement for OpenAI’s Swarm that augments it with durable execution to make your agentic workflows resilient to failures, so that if they are interrupted or restarted, they automatically resume from their last completed steps. https://github.com/dbos-inc/durable-swarm We believe that as multi-agent workflows become more common, longer-running, and more interactive, it's important to make them reliable. If an agent spends hours waiting for…
2024 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →