Show HN: Coral – Open-source gateway where agents write their own tools

jcs 52 points 24 comments November 16, 2026
github.com · View on Hacker News

Hi HN, I'm James, one of the co-founders of Coral. Coral is an open-source, self-hosted gateway that sits between your agents and the systems they work on. Agents call tools by writing short TypeScript programs that they can save as custom tools to reuse. You can publish custom tools for groups of agents, so your team’s library of tools adapts to your unique systems, data and use cases. Custom tools help agent performance and give more precise units of permission control. Here’s a short demo: https://www.youtube.com/watch?v=p0PKOlHLyVI We started on this while building an AI SRE. To investigate an incident, the agent had to connect the dots across an ocean of telemetry data and undocumented relationships across internal and external systems. It took broad permissions, a lot of tokens and it would start from scratch the next time. We built Coral so that the agent remembers the route. Once a task succeeds, the agent writes the steps that worked into a program and saves it as a custom tool. Next time, the agent finds that custom tool in the same search as standard provider tools (e.g. Datadog, Slack), and reuses it. It started with SRE, but we (and our early users) now use Coral for agent work across the org. For our tasks across GitHub, Linear and Slack with Opus 5.5, custom tools help agents work 29% faster, at 31% lower cost (tasks here: https://withcoral.com/docs/examples/custom-tools ). Coral builds on code mode, adding custom tools, policy controls and managed identities. Each program runs in a V8 isolate with no network access or credentials. Coral checks every tool call against workspace policy before attaching credentials and forwarding it to the provider. You can configure each provider to use the caller’s own account, so teammates can share tools without sharing API tokens. (e.g. https://withcoral.com/blog/slackbot-works-better-with-coral ) Coral is written in Rust, and you can run it as a desktop app or as a shared server. The core is Apache 2.0 and has no limits on users, agents or volume. Everything I've described here is in the OSS edition. SAML, SCIM, and org-wide governance features will be available soon under an enterprise licence. We'd love for you to try it and share your feedback. You can download it here https://withcoral.com/download . I'll be in the comments here and on Slack: https://withcoral.com/slack

Discussion Highlights (11 comments)

greenBottle

Looks good. We're evaluating it.

jurgenaut23

Will give it a go!

ocamoglu

Better and granular controls as well as task specific memory for cost and time savings sounds amazing. Looking forawrd to trying this further. Looks like this is already used in real world by your customers. Any learnings you can share for deployment?

nikolicmilena

Cool - as we give agents more autonomy and write permissions, granular controls like this will be vital. Gonna get the team to test this.

antonmry

I work for Coral but in my personal opinion, it's great how easy is to integrate Coral with my own workflow without having to make big changes to it. It makes a breed to add external services and manage agents permissions

latissi

Nice Works!

fg137

Got really confused by the name. Apparently Google has a "Coral platform" which used to ship TPUs as USB devices (although that's discontinued, and Google barely markets the Coral brand these days). If you search "Coral AI" there are tons of products/companies called by that name, and this one is not nearly at the top. Maybe something to think about.

anonyonoor

What would be great too is a library for mini apps built with agents. I find these little apps to be useful all the time, but despite usually being written in very versatile HTML that is cross-platform, these things are confined to the specific platform I used and usually the chats too. I wish there was a provider agnostic way to build and view mini apps anywhere (desktop and mobile).

jrflo

What is HN's policy on creating green accounts to inflate engagement on launch?

wavemode

vibecoded slop is bad enough, but creating a bunch of bot accounts to comment in this thread is outright malicious. flagged.

eb379

Nice! I'd love to understand if a tool requires permissions how it works across agents.

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed