ORG2 logo

ORG2

Coding agent orgs: built for reviewability and team collaboration. Built-in rust harness & 20+ CLIs.

GitHub

What is it?

What it is

An open-source, Cursor-style agentic IDE designed for reviewability, traceability, and organizational alignment.

Why it exists

To move beyond treating AI agents as stateless, outsourced assistants and instead treat them as persistent, observable colleagues within a structured organization, addressing the lack of collaboration, observability, and shared accountability in current AI coding tools.

Who should use it

Developers and teams seeking AI-assisted coding with strong auditability, traceability, and local-first execution; especially those interested in agent observability, replayable trajectories, cross-session memory, and org-level alignment.

Who should avoid it

Users looking for a simple, zero-config AI code completion tool, those who prefer cloud-only SaaS IDEs, those uncomfortable with building from source or managing Rust/Tauri sidecars, and those who require permissive licensing over AGPL.

How it works

A quick walkthrough in plain English

How ORG2 works

Step 1 of 3

You interact with it

Open ORG2, send a request, or connect it to your stack.

Features

Long-running sessions with replayable execution traces for auditing and debugging
Rust-based agents integrated with existing API keys and agent subscriptions
GUI, CLI, terminal, Git, browser, LSP, timeline, and database tooling
Cross-session memory and cross-agent knowledge sharing
Resource-aware execution adapting to CPU, RAM, and human attention
Agent-powered GUI end-to-end testing for self-evolution
Scheduling and auto-started sessions for overnight or unattended work
Org-level alignment tools for coordinating humans, agents, and goals
Session collaboration and group issue workflows via self-hosted Supabase

Advantages

  • Enhanced reviewability and traceability through replayable execution
  • Local-first execution under 100MB disk footprint with Rust/Tauri
  • Improved collaboration via cross-session memory and shared state
  • Resource-aware execution optimizes performance and human-agent interaction
  • Supports self-evolution of agents through automated testing
  • Org-level accountability features for team coordination
  • Multi-platform support with desktop apps and source development
  • Open-source with active community and multi-language documentation

Disadvantages

  • AGPL-3.0 license may require sharing modifications publicly
  • Optional native sidecars (e.g., browser automation) add setup complexity
  • Some features (e.g., Supabase integration) are marked as WIP
  • Rust-based build may require technical expertise for development
  • Limited cross-platform availability for certain features (e.g., Computer Use on macOS only)

Installation

native

pnpm run tauri:dev

FAQ

How do I download and install ORG‑2 on macOS?

Click the macOS Apple Silicon link in the download section of the README. It will download a .dmg file. Open the .dmg, drag ORG‑2 to your Applications folder, and launch it from there. The installer automatically resolves to the latest release via GitHub’s latest release pointer.

What are the minimum system requirements and disk usage for ORG‑2?

ORG‑2 is built with Rust and Tauri for a local‑first experience and occupies less than 100 MB on disk. It runs on macOS, Windows, and Linux (x64). CPU and RAM usage is resource‑aware, reacting to system load and human attention.

How can I build ORG‑2 from source?

Run the following commands in the repository root: ```bash pnpm install pnpm run download:sidecars pnpm run tauri:dev ``` This installs dependencies, downloads optional native sidecars, and starts the development build.

What are the optional native sidecars and how do I enable them?

ORG‑2 relies on two sidecars: - **agent-browser** – for browser automation, downloaded from the `vercel-labs/agent-browser` releases. - **peekaboo** – for macOS screen automation, downloaded from `steipete/peekaboo` releases. If a sidecar is missing, the Rust build creates a placeholder. To fetch them, run `pnpm run download:sidecars` or manually download the binaries and place them in the expected directories.

How does ORG‑2 support replayable agent execution and cross‑session memory?

Each session records a trajectory that can be replayed for auditing, debugging, or review. Agents share knowledge across sessions, and the workspace state is persisted, allowing you to resume work or analyze past decisions.

Where can I get help or discuss ORG‑2?

Join the ORG‑2 community on Discord at https://discord.gg/tvWgAqhCzs. Use channels like #how-to-use-org2, #faq, #announcement, #lets-chat, and #feedback for support and collaboration.

Loading documentation…
View on GitHub

Featured in Videos

YouTube tutorials and walkthroughs for ORG2

Alternatives

Similar projects ranked by category, topics, and text overlap.

Compare
ORG2 | MushyBook