OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Multi-Agent Systems

Goclaw

GoClaw is a self-hosted, Go-based multi-agent gateway that routes agent work to multiple LLM providers and messaging channels, with PostgreSQL-backed multi-tenant workspaces and sessions.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Goclaw — OpenViST project profile in Multi-Agent Systems.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the standard server edition when you need a self-hosted gateway for coordinating agents across providers, chat channels or tenant-isolated PostgreSQL workspaces. Use GoClaw Lite when the goal is local desktop agent management with SQLite and the documented small-team limits.

Who it is for

  • Operators deploying agent teams across multiple LLM providers.
  • Teams that want agents to coordinate tasks and communicate through supported chat channels.
  • Developers and operators who need gateway trace inspection through a CLI.
  • People seeking a local desktop edition for a small agent setup rather than a PostgreSQL server deployment.

Documented uses

  • Route agent requests to different LLM providers through a shared gateway.
  • Coordinate agents using shared task boards and synchronous or asynchronous delegation.
  • Connect server-based agent teams to supported messaging channels.
  • Separate tenant workspaces and sessions in the standard PostgreSQL edition.
  • Inspect local or remote gateway traces with the operator CLI.
Before you choose

Requirements & limits

  • The standard server quick start lists Go 1.26+, PostgreSQL 18 with pgvector and optional Docker for a source-based setup.
  • Docker setup requires at least one configured provider API key.
  • The standard server edition uses PostgreSQL; Lite uses local SQLite and has a maximum of five agents and one team of five members.
  • Lite lacks the standard edition's messaging channels, multi-tenant features and full knowledge graph.
  • Browser automation, Jaeger tracing, sandboxing, Tailscale and Redis are optional Docker services enabled with WITH_* flags.

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

Start GoClaw with Docker

Prepare the Docker environment, configure a provider key and start the gateway services.

Before you start

  • Docker
  • A provider API key for at least one GOCLAW_*_API_KEY setting

Steps

  1. Run chmod +x prepare-env.sh && ./prepare-env.sh to create an environment file with generated secrets.

  2. Add at least one provider API key to .env.

  3. Run the command below to build and start the services and apply database migrations.

    Documented command
    make up

  4. Open the built-in dashboard at http://localhost:18790.

Expected outcome

The Docker services start with the built-in web dashboard available at the documented local address.

Guide limitations

  • If PostgreSQL cannot bind because port 5432 is already in use, set a different host port with POSTGRES_PORT in .env.
  • A separate nginx service for a custom SSL or reverse-proxy setup is optional.
Documentation 1 ↗
Source-based practical guide

Inspect gateway traces with the GoClaw CLI

Use the operator CLI to list, retrieve or follow gateway traces.

Before you start

  • The GoClaw binary
  • For a remote gateway, its server address and gateway token

Steps

  1. List error traces with goclaw traces list --status error.

  2. Retrieve a trace as JSON with goclaw traces get -o json.

  3. For a remote gateway, follow a session with goclaw --server https://goclaw.example.com --token "$GOCLAW_GATEWAY_TOKEN" traces follow --session .

Expected outcome

The CLI provides the documented trace listing, retrieval and session-following operations.

Guide limitations

  • The examples require suitable trace IDs or session keys; remote use also requires a gateway token.
  • The documented commands describe inspection operations, not a trace-based diagnosis or repair procedure.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for Agent orchestration

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
GoclawRoute agent requests to different LLM providers through a shared gateway.Docker, Linux, Self-hosted, Server
AgenthubDecompose a goal and dispatch work among agent roles.CLI, Docker, Self-hosted, ServerThe repository is public and licensed under Apache-2.0. The README documents a local Docker platform path and published CLI binaries for Windows x64; it does not claim CLI binary support for other platforms.
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
14 October 2026
Original website title
nextlevelbuilder/goclaw · Official homepage title · retained in its source language
How we review sourcesSuggest a correction