@assemblyline-agents/orgo

Official Assembly Line connection plugin for isolated Orgo cloud desktops. It wraps Orgo's documented REST API in a reviewed SDK connection so the agent receives screenshots as image content and never receives the API's VNC password fields. The bridge follows the screenshot resource URL returned by Orgo, downloads the bounded image with host-only API authorization, and preserves its actual media type instead of treating the URL as encoded image bytes.

Setup

Create an Orgo API key, store it through the selected secret provider, then add the plugin:

assembly-line add orgo agent

The selected plugin enables all reviewed Orgo tools. Gate high-impact actions explicitly:

capabilities:
  orgo:
    connections:
      orgo:
        approval:
          delete_computer: always
          execute_bash: always
          execute_python: always

Use disable under the same connection to hide an operation. Orgo computers are persistent cloud resources and may continue billing until stopped or deleted. Use dedicated workspaces, configure auto-stop where appropriate, and review the authority granted to unattended workloads.

Set ORGO_API_BASE_URL only for a developer-controlled Orgo-compatible endpoint. It is non-secret connection configuration. ORGO_API_KEY is a connection credential resolved just in time and delivered only to the trusted Orgo connection or credential sink.

orgo__capture_file exports one exact desktop path into a private, run-scoped asset descriptor. The bytes stay host-side and may be consumed by another trusted connection in the same run; the model receives only the opaque asset ID, filename, media type, size, and digest.

For a login value stored in 1Password, focus the target field and call the connection tool with identifiers and intent only:

{
  "source_connection": "onepassword",
  "reference": "op://Charlie/PeerComps/password",
  "target": { "computer_id": "charlie-browser" },
  "purpose": "Sign in to PeerComps"
}

orgo__credential_fill resolves and types the value entirely host-side and returns only { "status": "filled" }. Continue with ordinary screenshot, click, and keyboard tools after authentication.