Image: GitHub
Why it mattersAn agent that keeps writing the same code every session wastes tokens. A saved tool is one call instead, with the same permission check as a vendor tool.
An agent that uses a company's tools starts every session with no memory of the last one. It writes the same TypeScript glue code again and again. Coral is a gateway that keeps the code that worked. The agent calls it the next time in one step, with the same permission check as a vendor tool.
The project is Apache 2.0 on GitHub. The repository had 5,000 stars on 16 November. A Show HN post for the project sat at 46 points on Hacker News earlier that day. The company behind it is withcoral. The README describes the gateway as "execution rails for agents".
What it does
Coral sits between the agent and the systems that hold a company's data. The agent writes a short TypeScript program. The program runs in a fresh V8 isolate with no network and no credentials. Coral checks the call against a policy, adds the credentials, and sends the call on. The policy tag is Allow, Ask or Block, set per provider tool and per custom tool. Every approval is logged.
The number Coral publishes
The README reports the test in one sentence: 34 tasks on GitHub, Linear and Slack, run with Opus 5.5. Custom tools cut tokens by 37 percent. They cut cost by 31 percent. They cut time by 29 percent. These are Coral's own numbers. The post does not say the baseline, the task descriptions or the method. Read them as Coral's figures for its own change.
Agents saving their own tools
A custom tool in Coral is not written by a person. The agent writes it as a TypeScript program. If the program finishes and passes a check, Coral offers to save it. The next agent to need the same job calls the saved tool. This is the step that cuts the tokens: the model does not plan the code again, read the docs again or try the wrong path again.
How it changes the shape of the work
A policy stays with the gateway, not the agent. The same rule then holds for every agent that connects. A custom tool is a line in the catalogue. It sits next to the vendor tools, so the agent cannot tell them apart. An audit log carries every allow, ask and block. The company Coral says it is ISO/IEC 27001:2022 certified.
Coral is one of several projects that lets an agent keep what it learned in a session. The gateway shape is less common. Most alternatives are a memory file or a prompt. A gateway catches tool calls. The rule then covers the agent, the tools it writes and the tools the company already uses.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.