Ashlr cover: Ash, the Ashlr mascot, giving a thumbs up, with the headline How AI agents ship code without breaking things.

How Ashlr runs on agents, part 2 of 3Engineering

How Ashlr runs on AI agents, part 2: how agents ship code

By Ashlr.AIField notePublished Oct 17, 20265 min read

Agents can write code all night. The hard part is making sure bad code never reaches your users. These are the rules our agents follow to ship.

The field note

Letting an agent write code is easy. Letting it ship code is a trust problem. Our engineering team is mostly agents, and they work overnight without anyone watching. So the rules matter more than the model.

Rule one: nothing merges without green checks. Every change goes through a pull request. The automated tests and checks have to pass. If they fail, the change waits.

Rule two: one pull request at a time. Agents do not pile changes on top of each other. Each one lands, gets verified, and only then does the next start. It is slower on paper and faster in practice, because problems stay small and easy to trace.

Browse all stories

Ashlr cover: a falling bar chart labeled tokens per tool call, with the headline Same agent. Fewer tokens.

Field noteEngineering

ashlr-plugin: same agent, fewer tokens

Oct 17, 2026

Rule three: no admin override. Our repositories have branch protection, and agents are not allowed to use admin rights to skip it. Recently the Engineering Orchestrator approved a change to one repository's protection rules so that a single combined check, called CI Gate, is the required one. It made a backup first. That change fixed a stuck documentation-only pull request without anyone bypassing anything.

Overnight runs follow the same rules. In one recent batch, the team merged a group of pull requests with green checks and no admin bypass across Phantom Secrets and several other repositories. Each agent leaves a record of what changed and why.

What agents do not do: publish packages. Releasing to npm or crates.io needs credentials the agents do not have, and posting publicly on social media is off limits. The agents prepare a release. Mason decides when it goes out. This is on purpose.

Ash, the mascot, is also the name of one of our agents. Part 3 explains.

What it means for your work

For builders

Write your own merge rules before you let an agent push anything. At minimum: tests must pass, one change at a time, and no one, human or agent, bypasses protection. Keep release credentials away from the agent.

For business

Speed from agents is only valuable if quality holds. Ask your engineering lead three questions. What has to pass before code ships? Can anyone bypass it? Who owns the decision to release? Good answers are boring and specific.

Put it to work

Open one of your repositories' settings and check whether admins can bypass branch protection. If they can, decide if that is what you want when agents are pushing code.

Explore the projects

Ashlr tools connected to this story. Review their source and setup requirements.

Phantom

Work with eligible coding-agent accounts and local models in one workbench; review fleet proposals under signed authority.

Visit website View source

Phantom Secrets

Delegate supported API work through scoped placeholders and a local proxy, keeping real keys out of agent context.

Visit website View source

Go to the source

Source material behind this field note. Our practical implications are Ashlr’s interpretation.

Phantom Secrets pull requests (opens in a new tab)
Ashlr.AIOct 17, 2026
Phantom on GitHub (opens in a new tab)
Ashlr.AIOct 17, 2026

Field notes explain an engineering or business practice. They are not reports of a new event. Cover artwork is illustrative.

Editorial approach Suggest a correction

4 min read

Coding agents burn most of their budget reading files and search results. ashlr-plugin gives them tools that return less, without losing what matters.

Ashlr cover: a ring of provider dots, with the headline Set up ten services with one prompt.

Field noteEngineering

Ashlr Stack: set up your backend services with one prompt

Oct 17, 20264 min read

Starting a project means an hour of clicking through dashboards and pasting keys. Stack does that setup from your terminal or your AI agent.

Ashlr cover: a falling bar chart, with the headline We dropped our own headline number.

Ashlr releaseEngineering

ashlr-plugin 1.36.5 drops its own headline number

Oct 16, 20263 min read

ashlr-plugin 1.36.5 replaces its 57 percent savings headline with per-call figures and fixes extra overhead on tiny edits. This is an Ashlr release.