Create and connect
Create an Agent and Draft
The website is the management entry point for Agents, versions, and publish status. This section covers only “sign in → create an Agent → open the first draft.” It does not write any Program files locally or in a remote Workspace.
1. Sign in to the website
1.1 Open the sign-in page
Visit the OpenAgent sign-in page. The current website provides Google and Apple sign-in options.
1.2 Use the account that will maintain the Agent long term
The Agent, drafts, publish records, and online status all belong to the current Owner. Do not switch to a different account for a temporary test, or your later CLI session may be unable to access this version.
1.3 Confirm that you return to the website
After authorization, you should return to the website in a signed-in state. If the authorization page reports an error or the callback does not finish, restart sign-in from the website. Never give an OAuth code, Cookie, or Token to your local AI, documentation, or command line.
The website session and CLI session do not share credentials
The first time the CLI needs platform permission, it opens a browser for a separate secure sign-in. Do not extract browser credentials for the CLI. The CLI performs the loopback, state, PKCE, and one-time code checks itself.
2. Create the Agent and its first draft
2.1 Open Developer
From the website, open Developer and then My OpenAgents. This page lists Agents owned by the current account, not every public Agent.
2.2 Click Create
The current implementation creates the Agent and its first draft version in one operation, then navigates directly to the version workspace. You do not need to create an empty Agent and then create a version separately.
2.3 Confirm what you are editing
Verify that the browser address is /developer/agents/<agentId>/versions/<versionId> and that the workspace shows draft status. The IDs in the URL are only for identifying context; do not edit them manually.
3. Set the version number
Version labels use a strict three-part numeric format:
| Example | Valid? | Reason |
|---|---|---|
0.1.0 | Valid | Three parts, each containing one digit |
12.3.45 | Valid | Three parts, each containing one or two digits |
v1.0.0 | Invalid | A v prefix is not allowed |
1.0 | Invalid | The third part is missing |
100.0.0 | Invalid | The first part exceeds two digits |
1.0.0-beta | Invalid | The current format does not accept suffixes |
For a first experiment, use 0.1.0. The version number distinguishes deliverables; it is not the same as agent_version_id, which is the unique ID assigned by the platform.
4. Identify the Agent and version context
- Agent ID: shown in Agent details and identifies the Agent as a whole.
- Version ID: included in the canonical version workspace URL and identifies this draft.
- Preferred handoff: click Build With Local Agent and copy the entire trusted prompt. It is already bound to both IDs, so you normally do not need to copy them manually.
Created the Agent under the wrong account?
Stop the build immediately, switch to the correct Owner, and create it again. Do not continue by guessing IDs, editing the URL, or reusing another account's CLI session. The platform enforces Owner permissions.
Completion criteria for the creation stage
- The new Agent appears under My OpenAgents.
- The browser is open on that Agent's first draft version workspace.
- The version number follows
N.N.N, with one or two digits in each part. - The next build will use the complete Build With Local Agent prompt generated on this page.
Continue: Understand the version workspace.