Build With Local Agent is the trusted handoff point between the website and your local AI. It places the current version context in an auditable prompt so the local AI can follow the platform Skill instead of asking the developer to assemble APIs, IDs, or remote connection parameters manually.
https://oasn-ow.haimawan.com/s/oasn-sa-developer-workspace/SKILL.md. The website combines this address with the current agent_id, agent_version_id, and operation=build to form the trusted prompt. The button does not create a new dynamic short link on every click.
In the version workspace, first verify the Agent name, version number, and draft state. Do not reuse an old prompt from chat history or another browser tab.
The dialog must include the fixed Skill URL, the build operation, and the current Agent/Version IDs. If anything is missing, close the dialog and reopen it from the correct version.
Copy everything from the first line through the last. Do not copy only the Skill URL, and do not replace the IDs with names, version labels, or values found on another page.
The local AI should treat this prompt as the authorized context for this build and read the Skill before acting. Because the prompt already binds the IDs, the AI should not ask you to enter the Agent ID or Version ID again.
install --expected-sha256.doctor and workspace sources --version-id <agent_version_id>. Show you the actual existing-Workspace, restorable-version, and fresh choices; a recommended source is not automatic authorization.--source-version-id/--fresh choice and wait for status=active. workspace create does not read, generate, or upload an SSH key.workspace connect with an existing key to bind its fingerprint and perform the real BatchMode SSH probe. Only when ssh_binding_status=bound and ssh_verified=true may the returned SSH/SCP information be used; file synchronization still requires separate explicit authorization.Do not let the local AI switch to curl, wget, raw platform HTTP, or a custom sign-in script. Only when the current AI has no local terminal/Python capability should you manually download the fixed file named by the Skill in a browser, while preserving the same digest verification.
| Action | When it is authorized or confirmed | Scope allowed |
|---|---|---|
| Install the CLI | The Skill provides a fixed URL/digest and all checks have passed | Install the verified CLI 0.7.3 in the current user's directory |
| Create an SSH key | doctor/ssh-key ensure confirms that no existing public key is available, and you explicitly approve creation | Create one dedicated key pair and refuse to overwrite any existing file |
| Select a source | workspace sources has returned the current real choices | Reuse or create only from the source you explicitly selected; a recommendation is not consent |
| Connect to the Workspace | The trusted Build With Local Agent prompt already authorizes workspace connect to this active Workspace with an existing key | Bind and verify only the Workspace and key selected for this build; this does not authorize key creation or file synchronization |
| Synchronize files | The temporary-copy diff has been shown and the sensitive-data scan has passed | Upload first to this run's /oasn/.oasn-staging/<run-id>/, verify it, and apply it only to the explicit target |
“Give this prompt to your local AI” is not authorization to overwrite original local files, connect to arbitrary hosts, upload an entire directory, or expand the work to another Agent/version. Every action with an external effect must remain minimally scoped.
build in the prompt to publishing or another operation.The CLI still provides oasn-sa-dev skill-link create --version-id <id> for compatibility, but the current website flow already supplies a trusted prompt containing the fixed Skill URL and bound IDs. In a new development flow, do not run the compatibility command first, and do not treat an older document's “generate a 24-hour short link every time” description as the current button behavior.
Continue: Install and use the development CLI.