GoClaw

GoClaw is a Golang implementation of a certain molty bot, compatible with OpenClaw session formats and “soul-ness”.

Originally intended as a “minimum viable” replacement for OpenClaw, it has molted to reasonable feature parity with OpenClaw. It’s not a complete replacement for OpenClaw but it’s very driveable.

GoClaw has superpowers: transcript search — a persistent, searchable conversation history that survives context compaction — and a memory graph that extracts facts, preferences, and relationships into a semantic knowledge graph. Your bot can recall detailed chat messages from its birth and build structured understanding over time. Long live the memories!

Telegram, WhatsApp, HTTP (web), real-time voice (via xAI), and TUI interfaces are available for chatting to GoClaw.

GoClaw can run side-by-side with OpenClaw in the same workspace directory. The two “consciousness” streams are merged at startup to create one unified timeline, and GoClaw monitors your OpenClaw session to sync any new interactions in real-time. Two brains, one identity. It can also run completely standalone if you prefer.

SQLite with vector extensions handles all session, transcript, and memory graph storage.

GoClaw is a bit opinionated about security, considering the brave new era we’re entering. Tool sandboxing and exec bubblewrap if available, as well as external content/prompt injection wrapping. The managed Chromium install can also be bubblewrapped (tested on Ubuntu). Many other guardrails also exist. Of course you can disable this if you want your bot to have unfettered, dangerous access. Nothing is ever entirely secure, but one can try.

This AI agent was written by an AI agent, under human guidance

Quick Start

Install

curl -fsSL https://goclaw.org/install.sh | sh

Interactive Setup (Recommended)

goclaw onboard

The setup wizard is fully mouse-enabled. Click through the steps to configure:

1. OpenClaw migration — If found, offer to import settings
2. Workspace — Set up your agent’s home directory
3. User profile — Create your owner account
4. Channels — Telegram, WhatsApp, HTTP server
5. Speech-to-text — Configure transcription (Whisper, Groq, Deepgram)
6. LLM providers — Select and test providers (Anthropic, OpenAI, Ollama, etc.)
7. Real-time voice — Configure xAI voice for spoken conversations
8. Sandboxing — Configure security options

After setup, start GoClaw:

goclaw tui           # Interactive TUI mode (recommended)
goclaw gateway       # Foreground mode (logs to terminal)
goclaw start         # Daemon mode (background)

Once running, open http://localhost:1337 for web chat and voice conversations, or use Telegram/WhatsApp.

Manual Setup

For manual tweaks, use goclaw setup edit to access the menu-based editor. For full manual configuration, create ~/.goclaw/goclaw.json and ~/.goclaw/users.json by hand — see Configuration Reference for the schema.

Re-configure

goclaw onboard            # Friendly first-run / guided setup path
goclaw setup              # Auto-detect: edit if config exists, wizard if new
goclaw setup wizard       # Force full wizard (re-walk all steps)
goclaw setup edit         # Edit existing config (menu-based)

Other Installation Methods

See Installation Guide for:

• Debian/Ubuntu — .deb packages with bundled dependencies
• Docker — Container images on ghcr.io
• Windows — WSL2 installer script
• Build from source — For development or custom builds

Superpowers

Transcript Search — Your Agent Never Forgets

Every conversation is indexed into a local, searchable database with semantic embeddings. Transcripts survive context compaction — nothing is ever truly lost. The agent can recover context, find previous decisions, or recall discussions from weeks ago.

Agent: "What did we decide about the authentication system?"
→ Searches 500+ conversation chunks
→ Finds relevant discussion from 2 weeks ago
→ "We decided to use JWT tokens with refresh rotation..."

See Transcript Search for full documentation.

Memory Search — Workspace Knowledge

Search your memory files (memory/*.md, MEMORY.md) with hybrid semantic + keyword search. The agent finds relevant notes, decisions, and context from your written records.

See Memory Search for details.

Memory Graph — Structured Knowledge

A semantic knowledge graph that automatically extracts entities, facts, and relationships from conversations. Unlike file-based memory, Memory Graph provides structured, queryable memory with tools like recall, store, and query.

See Memory Graph for details.

Managed Browser — First-Class Web Access

GoClaw includes a managed Chromium browser with auto-download/update:

• web_fetch — Automatic browser fallback for JavaScript-rendered pages
• browser tool — Full automation: navigate, click, type, screenshot
• Persistent Profiles — Authenticated sessions survive restarts
• Domain Mapping — Route sites to specific profiles (e.g., *.twitter.com → twitter)

See Browser Tool for full documentation.

Delegated Runs, Subagents, and Fanout

GoClaw includes a first-class delegated execution architecture that powers isolated cron runs and owner-driven subagents:

• Delegated runner lane — queued/running lifecycle with bounded global concurrency
• Subagent tools — subagent_spawn, subagent_status, subagent_cancel, subagent_fanout
• Fanout coordinator — bounded parallel child spawning, deterministic reduction, optional synthesis
• Result routing policies — store_only, deliver, handoff_main, return_to_requester
• Control plane visibility — /runners dashboard + SSE event stream + Telegram/TUI summaries

See Delegated Runs for the architecture and operational model.

ACP Sessions for Cursor

GoClaw can attach to a live Cursor ACP session, steer it from GoClaw, and surface Cursor interactive flows through HTTP, Telegram, and TUI.

• Session-scoped attachment — attach a GoClaw session to Cursor when needed
• Dedicated ACP config section — configure ACP separately from generic gateway settings
• Configurable ACP model alias — stored at acp.drivers.cursor.model, defaults to claude-4.6-opus-high-thinking
• Refreshable model catalog — setup editors can refresh the in-memory Cursor model list for the current process
• Interactive UX — HTTP cards, Telegram prompts or polls, and TUI notices

See ACP Sessions for the workflow, Configuration Reference for the config shape, and ACP Tools for the agent-facing tool reference.

Key Concepts

Context Window Management

GoClaw manages the LLM’s context window automatically:

[0%]──────[25%]──────[50%]──────[75%]──────[95%]──────[100%]
           │          │          │           │
        Checkpoint Checkpoint Checkpoint  Compaction
        (optional) (optional) (optional)  (required)

• Checkpoints (optional): Rolling snapshots of conversation state, generated via LLM
• Compaction (required): Truncates old messages when context is nearly full

See Session Management for details.

Text LLM Providers

The oai-next driver uses OpenAI’s WebSocket API for lower-latency streaming compared to the standard HTTP driver.

Speech-to-Text (STT)

STT transcribes voice notes from Telegram and WhatsApp into text for the agent:

The Debian package and Docker images include a bundled Whisper model (ggml-tiny.en.bin) for zero-config local transcription.

Realtime Voice LLM Providers

GoClaw has a separate VoiceLLM Registry for real-time voice conversations:

Voice providers maintain per-session WebSocket connections and handle bidirectional audio streaming. They power the HTTP Voice channel for spoken conversations.

See Channels for voice setup.

LLM Routing & Purpose Chains

GoClaw routes LLM requests based on purpose. Each purpose has a model chain with automatic failover:

Additional purposes (heartbeat, cron, hass, memoryExtraction) fall back to agent if not configured.

If a provider fails, GoClaw automatically tries the next model in the chain. See LLM Providers for configuration details.

Metrics & Cost Tracking

GoClaw tracks LLM costs and performance automatically using embedded models.json pricing data:

• Per-turn costs — Input, output, and cache token costs calculated per request
• Accumulated totals — Running cost totals across sessions
• Persistence — Metrics survive restarts (stored in SQLite)
• Web UI — Interactive tree view at /metrics
• JSON API — Programmatic access via /api/metrics

See Metrics for details.

External Content Protection

GoClaw wraps content from external sources (web fetches, etc.) with unique randomly-generated boundary markers to defend against prompt injection:

• Unique markers — Each external content block gets a random boundary ID
• Explicit warnings — LLM is told to treat content as DATA only, not instructions
• Spoofing detection — Content containing the marker is blocked
• Homoglyph normalization — Unicode lookalike characters are detected

See External Content Wrapping for details.

Session Storage

Sessions are stored in SQLite (~/.goclaw/sessions.db) with full message history. Even after compaction truncates in-memory messages, the full history remains in the database for:

• Audit trails
• Embeddings/summarization rebuilds
• Memory Graph extraction
• Future analysis

OpenClaw Compatibility

GoClaw can run alongside OpenClaw in the same workspace. On first run, the setup wizard detects OpenClaw and offers to import:

• Workspace path and identity files
• Telegram bot token
• Anthropic API key
• Browser settings

Session transcripts from both systems are merged into a unified searchable history. GoClaw monitors OpenClaw sessions in real-time, so conversations from either system stay in sync.

After setup, goclaw.json is the authoritative config. See Configuration for details.

Documentation

Full documentation available at goclaw.org/docs or in the docs/ folder:

Getting Started

• Installation — Download, install, or build.
• Configuration — Config file reference
• First Run — Starting the gateway

Core Concepts

• Concepts Overview — Key concepts explained
• Architecture — System components
• Delegated Runs — Delegated runner/subagent architecture
• Session Management — Context and compaction

LLM Providers

• Provider Overview — Multi-provider setup
• Anthropic — Claude models
• OpenAI Compatible — OpenAI, LM Studio, OpenRouter
• Ollama — Local models
• xAI — Grok models

Channels

• Channels Overview — Communication interfaces
• Telegram — Bot setup
• WhatsApp — WhatsApp integration
• Web UI — HTTP interface
• Voice — Real-time voice via xAI
• TUI — Terminal interface
• Commands — Slash commands
• Supervision — Ghostwriting and guidance

Tools

• Tools Overview — Available tools
• ACP Tools — Agent-facing ACP control and inspection
• Browser — Web automation
• Home Assistant — Smart home
• Cron — Scheduling

Agent Memory

• Memory Overview — Memory architecture
• Memory Graph — Knowledge graph extraction
• Memory Search — Workspace files
• Transcript Search — Conversation history
• Embeddings — Vector search

Advanced

• Advanced Topics — Deep dives
• ACP Sessions — Cursor ACP attachment and workflow
• Roles & Access — RBAC and auth
• Skills — Extensibility
• Sandbox — Execution isolation
• Security — Secrets, external content protection
• Metrics — LLM usage and cost tracking
• Deployment — Production setup
• Updating — Upgrading GoClaw
• Troubleshooting — Common issues

Related Projects

• OpenClaw — The original Molt/Clawdbot