OpenAgent
OpenAgent

Create and connect

Build With Local Agent

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.

The current implementation uses a fixed Skill URL

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.

Copy the trusted prompt from the website

  1. Confirm the current draft

    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.

  2. Click Build With Local Agent

    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.

  3. Copy all content

    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.

  4. Send it unchanged to your local AI

    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.
Trusted Build With Local Agent prompt dialog in the version workspace
Trusted handoff content. Use the entire prompt generated from the current version on the website. The Agent and version IDs in the screenshot are sanitized.

What the local AI should do next

  1. Read the static development Skill at the fixed URL and enter only its build workflow.
  2. When a Workspace is actually needed, use the CLI URL and SHA-256 bound in the Skill for a constrained bootstrap.
  3. Verify HTTPS, download size, the response-header SHA-256, and the file-body SHA-256, then run the CLI's own install --expected-sha256.
  4. Run 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.
  5. Reuse the existing Workspace you selected, or create one with the confirmed --source-version-id/--fresh choice and wait for status=active. workspace create does not read, generate, or upload an SSH key.
  6. After the Workspace is active, run 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.

Before installation, only the Skill's constrained bootstrap may run a Python helper

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.

Authorization and confirmation boundaries

ActionWhen it is authorized or confirmedScope allowed
Install the CLIThe Skill provides a fixed URL/digest and all checks have passedInstall the verified CLI 0.7.3 in the current user's directory
Create an SSH keydoctor/ssh-key ensure confirms that no existing public key is available, and you explicitly approve creationCreate one dedicated key pair and refuse to overwrite any existing file
Select a sourceworkspace sources has returned the current real choicesReuse or create only from the source you explicitly selected; a recommendation is not consent
Connect to the WorkspaceThe trusted Build With Local Agent prompt already authorizes workspace connect to this active Workspace with an existing keyBind and verify only the Workspace and key selected for this build; this does not authorize key creation or file synchronization
Synchronize filesThe temporary-copy diff has been shown and the sensitive-data scan has passedUpload 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.

If the context looks wrong

Do

  • Return to the intended version, reopen the dialog, and copy the whole prompt again.
  • Ask the local AI to state the Version ID and operation type it is about to use.
  • If Workspace creation times out, save the returned Workspace ID and query that same environment; after it becomes active, still run connect.

Do not

  • Guess a platform ID from the Agent name or version number.
  • Change build in the prompt to publishing or another operation.
  • Combine another Agent's SSH/SCP command with this context.

The compatibility command is not the recommended entry point

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.

Search documentation

Suggested searches