abi. Agent Studio Guide
This is the guide shown inside the app, published unchanged. It is generated from the app's own Help text, so when that changes, this page changes with it. It describes what the product does and, deliberately, what it does not.
The Studio takes a process off your Clone and turns it into an automation you can actually run, in four stages: review what could change, realign it, design it, then build it. Included in abi. Pro and abi. Max and metered in credits.
The four stages
- 1. Review. abi. reads a process from your map and proposes optimisations, each with what it would save and how confident it is. You accept or reject each one. This is the metered step, at 25 credits a run
- 2. Realign. The accepted changes are applied to a target version of the process, so you can see the intended shape against today's
- 3. Design. A lane canvas for laying out the steps, constrained so it can only produce something buildable
- 4. Build. Export to n8n or Make, with a guide for wiring it up in your own account
What the Studio does not do
This matters more than anything else in this guide.
- It designs and exports. It does not run your automation and it does not monitor it. Every export is stamped as not monitored by abi.
- Every export carries a rollback step, because an automation nobody can undo is a liability rather than a saving
- An exported agent appears on the Clone as a ghost until you mark it deployed, so the map never claims something is running that is not
Reverse import
If you already run automations, the Studio reads an n8n or Make workflow and draws it onto the Clone. That turns the map from a model of the manual work into a model of everything, including what is already automated.
Target chains going stale
A target chain is promoted to observed once it matches what is really happening. If the underlying map then changes, the chain is marked stale rather than quietly left looking current.
Governance is not optional here
Every workflow you export is registered on abi. Governance as an agent, with no owner and no controls until you give it some. That is deliberate: the register should know about an agent from the moment it exists, not from the moment somebody remembers to add it.