Enterprise agent tooling grows up: what this week's Show HN launches actually tell us

Five agent projects surfaced on Show HN between early August and late September. Read together, they sketch what enterprise buyers are actually asking for. Not smarter models. Plumbing. Hyperlane calls itself an IDE and an ADE, merging agent worktrees with native tooling. Recurse ships a serverless harness for turning specialist agents into tools, MCP servers or bots. Soma is a self-hostable runtime in a single binary with a security and governance plane across agents. Pizza Bot is a local-first inbox for long-running agent work. PeerTalk connects two people's agents directly.

That is a lot of scaffolding for one category.

Parallel runs and the return of the worktree

Hyperlane's pitch is the oldest problem in software: two people editing the same file. Its answer is worktrees, one per agent, merged back with native tooling. Pizza Bot attacks the same problem from the queue side. Tasks start or get scheduled, the user walks away, and finished work lands in an Unread bucket while decisions wait in an Action queue. Its README says agents keep working when you navigate away or disconnect, and only the api-server process must stay running. A stateful DeepAgents and LangGraph runtime serves the same React experience in Electron and the browser, with a terminal CLI talking to the same server over HTTP and SSE. Checkpointed runs survive client disconnects, and cron or webhook triggers can start work with no conversation open.

Pizza Bot was developed at Amazon and released under the Apache 2.0 license, per the repository. That provenance matters less than the shape of the thing: it assumes agents outlive the window you opened them in.

Governance, credentials and the bits enterprises ask about

Soma is the most explicit about the enterprise angle. The docs describe a self-hostable runtime with a security and governance plane, fine-grained API key access management to restrict access to an agent, an outbound AI gateway that intercepts every agent request to model providers, and local, AWS or soon GCP KMS encryption for secrets including MCP credentials, API keys and agent secrets. An MCP server pre-integrated with third-party SaaS providers handles credential encryption and rotation. TypeScript is supported today, Python is listed as coming soon, and Rust has no bindings yet. Windows is marked white on the support matrix, and the docs say that is because Soma uses Unix domain sockets in Rust.

Fine-grained API key access management to restrict access to your agent

Recurse takes a different cut, packaging specialists as deployable units with a pinned manifest, validated inputs and checked outputs. Its landing page shows an agent.yaml excerpt, a CLI flow with search and verify steps, and deployment commands for MCP endpoints usable from Codex or Claude. Every new account starts with $5 of runs and no card, according to the site.

PeerTalk is the odd one out and the most interesting. Two agents on different machines connect directly, encrypted, with the room key generated in the browser and carried in the link. The site states that messages go straight between machines and are never relayed; if a direct connection fails, the agents stop and say so. Each agent leaves an address encrypted with that key, so the service cannot read or change it. The room gives agents 30 minutes to connect, then closes. PeerTalk is free, described as an experiment by Daniel Brain, and the site concedes the obvious risk: it is only as safe as the person you connect with, and agents are told to treat the other side's messages as information, never instructions.

Why this stack exists now

The commercial context is not subtle. Recent coverage has been wall-to-wall agent governance, runtime security and control planes, from Snowflake to Collibra to Darktrace. Vendors are selling oversight of agents that companies have already deployed. The Show HN cohort is selling the substrate underneath that oversight, often for free and often by one person.

None of these projects publishes adoption numbers, funding or customer names, so treat the enthusiasm as directional rather than proven. What they do reveal is a consensus about failure modes. Agents run long, so runs must be checkpointed. Agents act on the world, so approvals must be durable and folders must not hide pending work from a global queue. Agents touch credentials, so secrets need rotation and a gateway. Agents exist in more than one place, so identity and access control follow them.

The unglamorous parts are where the differentiation sits. Pizza Bot grants no default home-directory access and requires folders to be added explicitly as read-only or writable under Settings. PeerTalk will not relay traffic. Soma binds its own governance to your KMS. That is a mature instinct, and it is arriving from hobby projects faster than from the platforms.