Mercury – No-code orchestration for human and agent teams
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…
What it does
In the maker’s words, at launch
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 together in one place. You draw connections between them to form agent teams. An edge between Agent A and Agent B means A can delegate work to B — B processes the request, calls its tools, and replies. Agents can delegate further down the graph. The canvas becomes a living map of how your team operates. Some details on the stack: - Delegation as a primitive: when Agent A messages Agent B, it creates a persistent task. Tasks survive across activations so multi-step work doesn't lose context. - Agent types: native Mercury agents (Anthropic SDK / Claude), plus adapters for Claude Code, Devin, Manus, OpenClaw, Gumloop, and any MCP-compatible agent. Mix them on the same canvas. - 800+ tool integrations via Composio (Gmail, Calendar, Slack, Linear, Notion, etc.) with per-agent OAuth. - Channels: agents reach humans via the web UI, iMessage, or Slack. External triggers (new email, calendar event) can wake agents and kick off workflows. - Human-in-the-loop by default: agents need approval before real-world actions. You relax controls per-agent as trust builds. We've been running Mercury on Mercury for months — 30+ agents supporting a 3-person team. Scheduling, sales ops, engineering triage, finance. The thing that surprised us most: the hard part was never getting a single agent to be smart. It was getting five of them to not duplicate work, not contradict each other, and not spam the same human with redundant questions. We've raised $1.5M from a16z, with investors from OpenAI, Cognition, and others. We're opening up alpha access — if you're interested: mercury.build One question we'd love the community's take on: where should memory live — in the orchestration layer or the agent layer? We started by managing memory at the org level, exposing it as tools or injecting it into agent context. But not all agents are created equal. Some handle memory well on their own, and we need to pick our battles. The role of the orchestration layer in memory management is one of the harder design decisions we're wrestling with, and we'd genuinely love to hear how others think about it. We put together a short walkthrough if you want to see the UX before signing up: https://youtu.be/jpKvbyjkXMU Happy to answer anything about the stack, the agent communication protocol, or the dumb mistakes we made along the way.
Does the same job
all alternatives →
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 26d ago · cactuscompute.com
Launched alongside, April 2026
the whole month →
- AG
Thought the resources for GPU arch were lacking, so here we are
Life & fun · Apr 2026 · jaso1024.com
- IB
Built a ~9M param LLM from scratch to understand how they actually work. Vanilla transformer, 60K synthetic conversations, ~130 lines of PyTorch. Trains in 5 min on a free Colab T4. The fish thinks the meaning of life is food. Fork it and swap the personality for your own character.
AI · Apr 2026 · github.com
- BC
Life & fun · Apr 2026 · sam-burns.com
- IB
With social media and now AI, its important to keep the indie web alive. There are many people who write frequently. Blogosphere tries to highlight them by fetching the recent posts from personal blogs across many categories. There are two versions: Minimal (HN-inspired, fast, static): https://text.blogosphere.app/ Non-minimal: https://blogosphere.app/ If you don't find your blog (or your favorite ones), please add them. I will review and approve it.
AI · Apr 2026 · text.blogosphere.app