OpenAgent

Appearance

Getting Started ​

OpenAgent can be used as the complete standalone product or embedded as a library. Current Python releases are server/CLI v1.1.0-beta.45, Core beta22, connector SDK/runner 0.1.8 and Host Tools 1.0.0b6: 114 official connectors plus Custom MCP, including 90 token profiles with two reads each. Desktop App v1.1.0-beta.22 is public, with an actual Linux x64 marketplace trial against server45. See downloads and qualification status for the independently recorded installation, provider, packaging and GUI boundaries.

Desktop app ​

Loading latest release…

Choose the installer for your operating system and CPU, launch OpenAgent, and connect it to an existing standalone server. App22 has six qualified native targets and 36 verified assets; both macOS builds are signed and notarized. Its Linux x64 App22/server45 marketplace trial loaded 114 official connectors and 30 registry results in one grid, verified 45 shared SVGs and 12 bundled marks, and captured ten reviewed screenshots. Postman token setup stayed blank and was cancelled; one Exa local control cycle completed. No provider call, model turn or new OAuth grant occurred. Google and Microsoft common enrollment remained off. Historical App21/server44 receipts and images retain their original versions. Hosted Electron used --no-sandbox; this does not establish sandbox security or Mac/Windows marketplace GUI. The app registers dashboard and local-computer capabilities only for its authenticated device turns; Telegram, scheduled work and other clients do not inherit them.

Standalone server and CLI ​

Loading latest release…
Loading latest release…

The beta server and CLI are Python 3.11+ wheels. The interpreter must include venv and ensurepip; some Linux distributions package these separately (for example python3-venv on Debian). The public installation was qualified on CPython 3.11.14/Linux x64. Use the normal public installer rather than assembling a partial wheel set:

bash
# Standalone server
curl -fsSL https://openagent.uno/install.sh | sh -s -- --server

# CLI
curl -fsSL https://openagent.uno/install.sh | sh -s -- --cli

# Download and verify every first-party wheel without installing
curl -fsSL https://openagent.uno/install.sh | sh -s -- --check

The installer checks first-party wheels against the four pinned manifests below, creates its isolated virtual environment and refuses to overwrite an unrelated command. Server installation also acquires and verifies the SDK-pinned native connector runner; users do not need a Go compiler. --check verifies the wheelhouse without installing dependencies or acquiring the native runner. Installing server and CLI uses the same default installation root. The historical beta43 public-installer receipt records its successful combined installation and dependency checks with default HOME/TMPDIR and without a source overlay. The current installer pins beta51/SDK0.1.12; its public-source installation trial passed separate server/CLI installs, dependency checks, ORM and the 114-plus-Custom catalog without a HOME override or source overlay. The receipt tracks canonical website byte verification separately. Installed beta51 qualification passed 241 tests and 15 React source groups. Neither boundary claims native App GUI acceptance or Windows/macOS server execution.

Pinned release manifestSHA-256
Product beta515d2538252f99cb4208da3dc25aa219261203af9ed866b0d66ac1d2bf64e7de7d
Core beta 22291be9e298c1035ae88079b849620e9a8a04e03f43dd9180f86ebe6e79f4876d
Tools beta 420b583195ac624c8f46a3c484eb596a5545dc514d60cbe7ed12e7b6f4da48228
Connector SDK 0.1.124b864472df3cbfd01131b0c152d94da81ff6f3f161e976bbbe4c768c56fb87c9

The product manifest also binds the unchanged Host Tools B6 wheel/bundles. Embedding products or custom packagers should follow the operator acquisition contract, including native runner acquisition, instead of treating a bare Framework pip install as equivalent to the standalone installer.

Commands are linked into ~/.local/bin by default; make that directory available on your PATH. Use installer --prefix /your/bin for another command directory and add that directory to PATH. OPENAGENT_INSTALL_ROOT can select an owned installation root; it does not change your home or identity profile.

Start a standalone agent from any folder:

bash
openagent init ./my-agent
openagent serve ./my-agent

The folder contains the product configuration, SQLite state, vault and logs. On first run the standalone identity package bootstraps the configured network and prints an invite ticket. Connect the CLI with that verified ticket:

bash
openagent-cli connect oa1abc123...

Embed Core in another product ​

Products install only the Core packages and modules they select. The host owns authentication, authorization, credentials, infrastructure and deployment:

python
profile = RuntimeProfile(modules={
    "sessions": ModuleConfig(surfaces={"service", "agent_tools", "host_api"}),
    "vault": ModuleConfig(surfaces={"service", "agent_tools"}),
    "mcp": ModuleConfig(
        surfaces={"service", "host_api"},
        options={"catalog_mode": "managed"},
    ),
})

runtime = Runtime(settings=settings, services=services, profile=profile)
await runtime.start()

An embedding host can follow this model: it builds its own worker image from pinned packages and owns its pods, sandbox, volumes and identity adapters. It does not download or patch the standalone OpenAgent repository at runtime.

Next steps ​