Alternatives
Products that do what The Tony Protocol does
Run your sub-agents like a North Jersey crime family
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9DA
I've been running Claude agents for various automation tasks — monitoring crypto news, syncing Todoist, running health checks — and I kept hitting the same problem: there's no clean way to deploy an agent that just runs on a schedule without a human babysitting it. Every agent framework I looked at was built around chat interfaces or one-shot workflows. I wanted something closer to cron for AI agents — define a task, give it a schedule, let it run forever. So I built Ductwork. You define tasks as simple JSON files — a prompt, a schedule, optional memory and skills — and ductwork handles…
Mar 2026 · github.com
- 10
Recently I've been running more and more agents in parallel however I noticed that they have no task context of what the other agents are doing even when a lot of work is interconnected It's like taking Slack away from a team. Agents duplicate work, make conflicting changes, and step on each others' toes simply because they can't talk to each other. Concord is an MCP + CLI that lets coding agents claim work, see what other agents are doing, and message each other live.
10d ago · github.com
- 11OS
We built an open-source library of 125 GTM (go-to-market) skills that plug into AI coding agents like Claude Code, Codex, and Cursor. With these skills an AI agent can automatically: - Find ICP leads from conference speakers, LinkedIn activity, or job boards - Generate personalized cold email sequences - Monitor competitor blogs, pricing pages, and hiring signals - Generate programmatic SEO pages from keyword lists - Track where your brand appears in ChatGPT, Perplexity, and Claude answers --- How skills work Each skill is a structured markdown file containing instructions, scripts, and tool…
Mar 2026 · github.com
- 12AR
Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…
May 2026 · agents-cli.sh
- 13SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 14
Hi HN, I saw one friction point when working as part of a team that uses coding agents extensively - there is nothing to enable coordination between agent used by people in a team. Many times my agent would ask me to decide upon something with a fellow teammate, for which I have to serve as the network layer. So I built Parley where agents can connect to the hub over MCP with their own team-scoped token. An agent addresses a teammate's agent by name and ask questions/handover tasks. Agents can also use file claims to signal what files they are working on, to highlight overlapping work.…
26d ago · parley.weldra.dev
- 151P
A few weeks ago I posted about GoodToGo https://news.ycombinator.com/item?id=46656759 - a tool that gives AI agents a deterministic answer to "is this PR ready to merge?" Several people asked about the larger orchestration system I mentioned. This is that system. I got tired of being a project manager for Claude Code. It writes code fine, but shipping production code is seven or eight jobs — research, planning, design review, implementation, code review, security audit, PR creation, CI babysitting. I was doing all the coordination myself. The agent typed fast. I was still the…
Feb 2026 · github.com
- 16MA
This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…
2025 · github.com
- 17
- 18CM
I built an MCP server that connects coding agents (Claude Code, Cursor, OpenCode, Codex) to a collaborative workspace where your team and other AI models can review what the agent is planning. The problem: When Claude Code creates an implementation plan, it lives in your terminal session. Nobody else sees it until it becomes a PR. If you want GPT to check the architecture or a teammate to flag issues, you're copy-pasting between windows. This MCP server fixes that. When your agent creates a plan, it gets shared as a collaborative thread in CoChat. Engineers comment on it, other AI models…
Feb 2026 · github.com
- 19MN
Hey HN, I'm Naveen, one of three co-founders building Mercury (mercury.build). We spent the last year in deploying AI agents for teams in large enterprises. The agents themselves worked fine. The problem was managing them. You've got Claude Code in a terminal, a research agent in a browser tab, a Slack bot somewhere else, a scheduling assistant in yet another window. It's chaotic. There's no single place to see what's running, who's doing what, or how things connect. As the number of agents grows, this gets unmanageable fast. Mercury is a canvas where you bring your agents and humans…
Apr 2026 · mercury.build
- 20RA
Hey HN, I built SuperHQ, an app that lets you run coding agents in local sandboxes (powered by Shuru). No custom UI wrapping the agents, they run as CLI/TUI like they were designed to. It just provides you the tools most of us (okay, maybe just me?) needed for running multiple coding agents in parallel without worrying about breaking your system or work environment. Each agent runs in its own microVM. You mount your projects in, writes go to a tmpfs overlay so your host is never touched, and you get a unified diff view to accept or discard changes. API keys never enter the sandbox, they…
Apr 2026 · superhq.ai
- 21AP
I've been working on this internal project initially both to learn more Vibe-Coding but also to help our teams and projects to use AI more efficiently. As more people used it, it grew to support multiple teams/projects to analyze their Claude Code conversation and optimize them over time (understanding how to write better conversation with Claude Code and share knowledge between them) With time we added support for multiple Claude account management and monitor usage/rate limit. This is a simple project but has proved to be quite useful for our company. We have reached 5000+…
2025 · github.com
- 22LT
Running multiple coding agents could make user losing track of what they were doing. Once subagents start spawning other subagents, basic questions get hard to answer: what is running right now, what tool did it just call, did the child agent actually do what the parent asked. Lazyagent is a terminal TUI that collects events from Claude Code, Codex, and OpenCode and shows them in one place. It groups sessions from different runtimes by working directory, so Claude and Codex runs on the same repo appear under the same project. From there you can: - Filter events by type: tool calls, user…
Apr 2026 · github.com
- 23PP
We built a protocol that gives AI agents an address, plus discovery/trust/payments between agents. Agents install it themselves with one line (see on pilotprotocol.network) - about 250k have, exchanging ~2B packets/day, mostly without their owners’ knowledge. The interesting part for HN is probably the App Store model: publishers list tools, and agents autonomously discover and install them (30k installs in the first two weeks). Happy to answer anything about the architecture, trust model, or the weird stuff agents do on the network.
Jul 2026
- 24PA
Hey HN, I'm Mo. I've been building Paseo, an open source environment for running Claude Code, Codex, and OpenCode across desktop, mobile, web, and CLI. It started last September as a push-to-talk voice interface for Claude Code. I wanted to talk to an agent while going on walks. Then I wanted to see what it was doing. Then text it when I couldn't talk. Then review diffs, run multiple agents, and manage work across machines. After a lot of iteration, it turned into a broader environment. The basic model is: - A daemon runs on your machine (MacBook, desktop, VPS, etc.). - Clients connect to it…
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →