Create and connect
Version Workspace
The version workspace is the control plane for one version. Here you define runtime capabilities, presentation information, and pricing; start a local build; and ultimately publish. The remote Program files live under /oasn in the development Workspace. Do not confuse the two.
Page areas and responsibilities
| Area | What you do here | Completion signal |
|---|---|---|
| Program | View development VM/Chat entry points, select models under Models, and choose CPU/Memory under Resources | Required models and CPU/Memory are selected; the Program has been tested in the Workspace |
| Agent Card | Set the avatar, name, description, category, and MOM | All required fields pass page validation, and a first-time caller can understand the MOM |
| Pricing | Set the cost-plus gross margin and Minimum Starting Balance | The gross margin is valid, and the minimum starting balance is expressed in Credits and is at least 0 |
| Save Draft | Save the current form configuration | The page no longer shows unsaved state or field errors |
| Build With Local Agent | Generate a trusted build prompt bound to this version | The complete prompt is passed unchanged to the local AI |
| Publish | Confirm and start version publishing | The publish job succeeds; Go Online is still a separate action |
Program: declare runtime requirements first
Complete at least the following configuration before treating the version as a publish candidate:
- LLM: currently a required model capability. Select the model capabilities the Agent actually calls.
- Optional understanding capabilities: select image, video, audio, PDF, image understanding, or similar capabilities only if the Program truly processes those inputs.
- Resources: the current dialog provides only CPU and Memory, and both must be set. Size them for normal request peaks, not merely for whether the process can start.
- Plugin/MCP/A2A: these are not configured in the Resources dialog. Implement them in the Workspace as described in the Program section and validate them with real calls.
A page declaration does not prove the implementation works
After selecting models and CPU/Memory, you must still validate real business requests in the development Workspace. If the Program uses a Plugin, MCP, or A2A, separately verify its runtime, business state, and final output.
Agent Card: tell callers how to use the Agent
The current workspace lets you edit the avatar, name, description, one category, and MOM. Publish readiness requires an HTTPS avatar. Uploads support PNG, JPEG, or WebP up to 5 MiB; a 1:1 image is recommended. The MOM must be a UTF-8 Markdown file no larger than 1 MiB and must contain explicit Use when, Inputs, and Outputs sections.
A background image, tags, and website URL are not part of the current workspace flow. Do not search for controls that exist only in older documentation.
Pricing: configure only the currently public model
The current workspace uses cost-plus pricing. Gross margin must be an integer percentage from 0 to 100. Minimum Starting Balance (minimum_starting_balance_credits) is denominated in Credits and must be at least 0. A decimal gross margin may be saved in a draft, but Publish rejects it with PRICING_MAPPING_INVALID; do not rely on silent rounding. Before publishing, use representative requests to confirm that the resulting cost matches your expectation.
When to save the draft
- After creation, enter the version number and minimum runtime configuration, then click Save Draft.
- After one Workspace development iteration, complete models, resources, Card, and Pricing, then save again.
- Before publishing, reopen the page and confirm that the loaded values match your expectation. Do not treat unsaved browser state as server-side fact.
Current implementation boundaries
Available now
- Save version configuration and start publishing on the website; after success, explicitly Go Online or use Take Offline when needed.
- Copy a trusted prompt that contains the fixed Skill URL and bound IDs.
- With CLI 0.7.3, get, set, or refresh WebUI ports and use allow-listed
portaloperations for draft/model/resource configuration and publishing; mutating operations require explicit authorization and--confirm.
Not available now
- A public Workspace close button or CLI
closecommand. - A WebUI port field on the website form. Use CLI 0.7.3
version webui-ports get,set, orrefreshinstead. - A generic CLI file synchronization command. Synchronize reviewed files through the explicit staged SSH/SCP procedure.