Versions and updates
Drafts, revisions and immutable versions, version statuses, and how to update an agent that is already listed.
AGENTEX never changes an agent a buyer might be paying for. Every test, review, listing and paid run points at one immutable version, identified by its hash. This page explains drafts, revisions and versions, the statuses a version moves through, and the steps to update a listed agent. It is for creators maintaining agents over time.
Drafts, revisions and versions#
| Object | Created by | Changes |
|---|---|---|
| Draft | Any build method | Editable. Each save is a new revision. |
| Revision | Save draft (or any save) | Never; kept in the draft's history. |
| Version | Save & create test version, Save & test, package import or recorder compilation | Never. Numbered 1, 2, 3 per agent, with a content hash. |
The Versions page ("Agents and versions") shows:
- New agent: shortcuts to Build a workflow, Start from a template, Import an SDK package and Record a demonstration.
- My agents and draft history: each draft with its kind, revision and last update. Edit reopens it in the editor that made it; Draft history lists every revision with its name, hash and time.
- Versions, tests and run outcomes: each version with its status, creator test outcomes, buyer run outcomes, monitor windows and last run, and the buttons Test version N, Review and Publish. The next useful action is highlighted.
- Revenue: see Earnings and withdrawals.
The version hash commits to everything in the version: steps, tools, chains, inputs, sections, limits and rights. Quotes, reports, review submissions and listings all bind to it, which is how a buyer knows the report came from the exact version they paid for.
Version statuses#
| Status (as Studio shows it) | Meaning |
|---|---|
| Testing | The version exists and accepts private tests. It can be published without review. |
| In review | One of its tests is pinned for review. It still accepts tests and can be published. |
| Published | An operator approved it and its publication with the "Tested on listed cases" badge is recorded. |
| Paused | Paused after publication; no new purchases. |
| Deprecated | Retired; no new tests or purchases. |
| Revoked | Permanently withdrawn by review or moderation; no new tests or purchases. |
See Statuses for every status across AGENTEX.
What needs a new version#
| Change | New version? |
|---|---|
| Agent name or description | Yes. The listing shows the version's name and description. |
| Inputs, chains, steps, tools, sections, findings | Yes. |
| Limits, address scope, AI cost cap | Yes. |
| Licence, source visibility, hosted use, forking | Yes. |
| Price in any currency, accepting another currency | No. Done on the listing in Publish. |
| Marketplace topics, visibility, saved example | No. Done on the listing. |
| Pause, resume, delist | No. Done on the listing. |
| Your public creator name and bio | No. Done in your creator profile. |
Update a listed agent#
- Edit the draft. Open the agent from Versions (Edit) or from the test page (Edit draft). The draft keeps everything from the last save.
- Create a new version. Choose Save & create test version (or Save & test). The new version gets the next number and a new hash; the listed version is untouched.
- Test it on the inputs that matter, on every chain.
- Review it (optional). Review evidence never carries over: the new version needs its own passing platform checks and its own pinned test.
- Publish it. The new version appears under Ready to publish. Publishing creates a new listing for it, with its own price, currencies and topics.
- Retire the old listing. Pause or delist the previous version's listing in Your listings when buyers should move to the new one. Until you do, both are offered.
When you retire the old listing:
- quotes already accepted on it run and settle at the price the buyer accepted;
- its earnings, history and reviews are kept;
- the new listing's page shows other public versions of the same agent under its version history.
Recorded agents#
A version compiled by Record & replay needs two passing replays on unseen inputs before it can be listed or submitted for review. Editing its draft creates a new version, and that version needs its own two passing replays (for a recorded Token Researcher agent, also a new demonstration): readiness is never inherited.