OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Coding Agents

Agor

Agor is a web workspace for running coding agents on isolated Git branches and coordinating their work with teammates on live spatial boards. Each branch has its own working directory, development environment and conversation history; boards let a team view, arrange and collaborate on branches and sessions.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Agor — OpenViST project profile in Coding Agents.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Agor when coding-agent work needs both branch-level separation and a shared team view for reviewing progress or collaborating. Its documented workflow also suits teams that want to reuse agent knowledge and skills across sessions.

Who it is for

  • Developers who run coding agents on software tasks.
  • Teams that want to follow, discuss and share agent work in a common workspace.

Documented uses

  • Run coding-agent tasks in separate Git branches with distinct environments and conversation histories.
  • Arrange branches and sessions on a shared board so teammates can follow work and step in.
  • Fork a session to explore an alternative with copied context, or spawn a focused subsession with a fresh context window.
  • Build reusable team context through shared knowledge namespaces and skills.
Before you choose

Requirements & limits

The repository documents an npm installation for self-hosting and also points to Agor Cloud Open Beta. It requires Node.js 22.12 or later and Git for the documented npm setup.

  • Agor supplies no model; users bring their agent CLI or SDK, provider and subscription.
  • The README lists Claude Code, Codex, Gemini, OpenCode and Copilot as runtimes; Cursor is marked beta.
  • Each unit of work is organized around a Git branch with a separate working directory, development environment and conversation history.
  • Self-hosting options described include LibSQL or Postgres and trusted local, fail-closed sandbox or delegated external execution modes.
  • HTTPS and SSH Git remotes have separate system prerequisites.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install Agor with npm and open its web UI

Initialize a local Agor installation and open the web workspace.

Before you start

  • Node.js 22.12 or later
  • Git available on PATH
  • For HTTPS Git remotes, a working system CA trust store; for SSH remotes, an SSH client and configured keys or agent access

Steps

  1. Install the Agor package globally with the command below.

    Documented command
    npm install -g agor-live

  2. Run agor init to create the configuration and database and select agentic tools.

  3. Start the background daemon with agor daemon start.

  4. Run agor open to open the web UI, then follow the onboarding wizard to create a board.

Expected outcome

Agor is initialized, its daemon is running, and the web UI opens to onboarding for a first board.

Guide limitations

  • The documented npm installation requires Node.js 22.12 or later and Git on PATH.
  • HTTPS and SSH remotes have the additional trust-store or SSH setup requirements listed above.
  • Agent credentials are configured later in the UI; selecting tools during initialization installs them but does not configure credentials.
Documentation 1 ↗Documentation 2 ↗
Source-based practical guide

Start Agor with Docker Compose for evaluation

Run Agor in a container and open its web interface without installing Node.js.

Before you start

  • Docker and Docker Compose
  • A cloned Agor repository

Steps

  1. Clone https://github.com/preset-io/agor.git and change into the repository directory.

  2. Copy docker/.env.prod.example to .env.prod, then edit AGOR_ADMIN_PASSWORD and choose AGOR_AGENTIC_TOOLS before first boot.

  3. Start the service with the command below.

    Documented command
    docker compose -f docker-compose.prod.yml --env-file .env.prod up -d

  4. Open http://localhost:3030 and log in as admin@agor.live.

Expected outcome

The containerized Agor UI is available at `http://localhost:3030` for the initial evaluation setup.

Guide limitations

  • The first-boot administrator setup runs only once against an empty database; setting AGOR_ADMIN_PASSWORD later does not reset an existing user's password.
  • AGOR_AGENTIC_TOOLS is a fresh-install policy and changing it later does not update existing configuration.
  • For hot-reload development, multi-branch setups, or PostgreSQL, the guide points to the Docker README and Development Guide; for Kubernetes-style executor isolation, it points to Containerized Execution.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for AI coding assistance

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
AgorRun coding-agent tasks in separate Git branches with distinct environments and conversation histories.CLI, WebThe repository documents an npm installation for self-hosting and also points to Agor Cloud Open Beta. It requires Node.js 22.12 or later and Git for the documented npm setup.
LlmcodeInspect a project's directory structure with `/tree`.CLIThe documented setup requires an API key and supports an API base URL and model setting. The project is open source under Apache-2.0.
Klaat CodeOpen a project directory for terminal-based coding assistance.CLI, ServerThe README provides a global npm installation command and documents browser sign-in with a KlaatAI account. It also identifies the repository as open source under Apache 2.0.
Evidence and transparency

Sources & review

Official repository ↗Guide documentation ↗
Source record details
Source availability
Active
Sources checked
15 October 2026
Original website title
preset-io/agor · Official homepage title · retained in its source language
How we review sourcesSuggest a correction