GitHubGitHub RepoNeeds Review

nightly-labs/openbot

OpenBot gives coding agents persistent local workspaces, queues, browser control, and shared delegation. Its preview runs agents with full file, command, network, and browser access after first-launch consent.

GitHub

Open Source Open Markdown Open JSON

Source Summary

OpenBot supports Codex, Claude, Grok, OpenCode, Gemini, Cursor, and Cline, with independent workspaces, persistent queues, context monitoring, and agent-to-agent collaboration. Agents currently run with **danger-full-access** and **approvalPolicy: never** after explicit first-launch consent. For builders coordinating multiple coding agents, it offers a desktop workspace with task ownership, delegation, shared history, and pause or reassign controls. Treat each agent as having broad access to its workspace and machine capabilities. OpenBot is a development preview and local-first, not offline-only: providers and visited pages use the network. Computer Use is optional, and remote desktop has platform limits, including no Wayland support on Linux.

Practical Implication

No separate implication has been recorded yet.

Agent-Ready Context

OpenBot supports Codex, Claude, Grok, OpenCode, Gemini, Cursor, and Cline, with independent workspaces, persistent queues, context monitoring, and agent-to-agent collaboration. Agents currently run with **danger-full-access** and **approvalPolicy: never** after explicit first-launch consent.
For builders coordinating multiple coding agents, it offers a desktop workspace with task ownership, delegation, shared history, and pause or reassign controls. Treat each agent as having broad access to its workspace and machine capabilities.
OpenBot is a development preview and local-first, not offline-only: providers and visited pages use the network. Computer Use is optional, and remote desktop has platform limits, including no Wayland support on Linux.

Connected Context · Feed7 Judgment

OpenBot packages persistent, multi-agent coordination in a local-first desktop workspace, but its agents currently receive broad machine access after first-launch consent. That makes task visibility and pause or reassignment useful controls for coordination, not substitutes for per-agent isolation; network use also means local-first does not mean offline.

stablyai/orcaBoth provide desktop coordination across coding agents, but Orca describes isolated worktrees while OpenBot's agents run with broad access; this distinction changes the isolation assumptions behind their similar workspace features.Multiplayer agentic engineering — Arjun Singh, SuperconductorSuperconductor's workflow pairs shared visibility with isolated cloud environments and review, clarifying the controls that OpenBot's persistent queues and collaboration features do not themselves provide.Give every agent in Herdr its own Vercel SandboxHerdr returns remote agent work as reviewable patches from separate sandboxes, whereas OpenBot grants agents broad access in its workspace; the comparison highlights different containment and handoff boundaries.Run multiple isolated agents in a single SandboxVercel's Linux-user separation offers a limited boundary for cooperating agents inside a sandbox; OpenBot's stated broad access makes clear that coordination features alone do not establish even that level of separation.

Context Map

toolscodingsecurity#coding-agents#multi-agent#sandboxing