Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Vet OpenBot before you install it

Written November 2, 2026

OpenBot runs coding agents with full access and no per-action approval, under a noncommercial licence. Check the repository and licence before installing.

What OpenBot is

OpenBot is a local-first desktop workspace for persistent AI teammates. The repository describes it as running the local Codex App Server and Claude Code, plus Grok CLI, OpenCode, Gemini, Cursor CLI, and Cline CLI through ACP, the Agent Client Protocol. Every agent gets its own workspace and conversation, with local queues, file transfers, an embedded browser, and agent-to-agent messaging in one desktop app. OpenBot runs on macOS 13 or newer on Apple silicon or Intel, Windows 10 or newer on x64 systems, and x64 or arm64 Linux as an AppImage, according to the install section of the repository.

Read the permission warning first

The repository carries a warning at the top: OpenBot is a development preview, and agents currently run with danger-full-access and approvalPolicy: never. They can read and modify files, run commands, use the network, and control the embedded browser without per-action confirmations after an explicit first-launch consent. The repository tells the reader to run only agents and tasks they trust, to keep backups, and to review the security section before use. That security section states the position plainly: full local access is an explicit current product decision, not a security boundary.

Each agent starts in its own workspace under ~/OpenBot/Agents/ and receives ~/OpenBot/Shared. The repository states that routine command and filesystem work in both locations runs without OpenBot adding another permission boundary, and that these modes also permit host access outside those directories when the provider and operating system allow it. So the workspace folders order the work; they do not fence the agent in. Before installing, decide whether that is acceptable for the machine and the files involved. A sensible first run is one agent, on a throwaway folder, with backups already in place — and no credentials, live project, or file you cannot afford to lose in reach.

Check the licence before you use it

OpenBot is copyright 2026 Synthetify Labs, and the licence section of the repository states it is licensed under the PolyForm Noncommercial License 1.0.0. The code may be used, modified, and distributed for permitted noncommercial purposes. Commercial use requires a separate licence from the copyright owner, bought in Settings → Billing (Starter for one user, or Team for two to ten users) or by contacting the address named in the repository. Versions up to and including 0.1.11 remain available under Apache-2.0. The repository names no commercial licence prices, so check the current terms in Settings → Billing or with the copyright owner before relying on a price. If the work is commercial, settle the licence first: the noncommercial licence does not cover it.

Check the install route for your machine

For most readers, the desktop route is the one to check. Download the release package for the platform from GitHub Releases. On macOS, drag the app to Applications. On Windows, run the installer. On Linux, make the AppImage executable with chmod +x. The repository notes that Windows releases are signed by Synthetify Labs, that older releases are not code-signed, and that SmartScreen can still warn about a new release — check the release checksum or GitHub build attestation before running the installer. On Ubuntu 23.10 or newer and on Debian 13, an AppArmor profile must be installed or OpenBot exits during launch, and the repository warns against starting OpenBot with --no-sandbox, which removes the boundary between a renderer and the rest of the computer.

Other routes exist for other setups: an always-on server install, a Docker container, and a Nix flake. The server install runs a script piped to a root shell followed by a sign-in command, on Ubuntu 24.04 or 26.04. Read that install script before running it as root, and use the desktop package if the always-on server is not what is needed. OpenBot uses the existing local CLI login for each provider and states that it does not copy provider credentials; Grok keys and per-session bearer tokens are never persisted or logged. Each provider's own terms still apply to the sign-in.

Check you have the right OpenBot

More than one project uses the name OpenBot. Before downloading anything, check that the repository is nightly-labs/openbot, that the copyright holder is Synthetify Labs, and that the licence is PolyForm Noncommercial 1.0.0 — the three marks that identify the desktop app described on this page. A different vendor, CopilotKit, has its own product under a similar name and its own pricing page for its own platform. The two are not the same install, the same licence, or the same permission model. If the page in front of you does not show the nightly-labs repository, stop and check which project it is.

Decide

Install OpenBot if the permission model is acceptable and the licence fits the use, or a commercial licence has been bought. Check that at least one provider CLI is already signed in, backups are in place, and the first run can stay on throwaway work. Do not install it if per-action approval or a sandbox boundary is required. The same applies to commercial use without a separate licence. The repository states full access as the product decision, not as a boundary, and the licence section draws the commercial line. Either decision is a good outcome from these checks: the checks exist so the install, when it happens, is a deliberate one.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Vet a skill before installing it · Check agent key files on your machine · Run a builder and reviewer pair in the background