gobby-cli

Rust CLI tools for AI-assisted development.
Code search, symbol navigation, output compression, local LLM launching, and multimodal research vaults — all from the terminal.

---

What's Inside

This workspace ships five Gobby CLI tools plus a shared library.

Current Release Set

Crate	Binary	Version	Release tag
gobby-code	gcode	1.0.0	gcode-v1.0.0
gobby-core	n/a	0.4.0	gobby-core-v0.4.0
gobby-hooks	ghook	0.4.6	ghook-v0.4.6
gobby-squeeze	gsqz	0.4.6	gsqz-v0.4.6
gobby-local	gloc	0.1.4	gloc-v0.1.4
gobby-wiki	gwiki	0.3.0	gwiki-v0.3.0

gcode — Code Search & Navigation

AST-aware code search powered by tree-sitter. Indexes 18 languages plus safe repo text files into the Gobby PostgreSQL hub, with pg_search BM25 for symbol lookup, exact indexed grep over repo content chunks, ranked repo-content search across source/docs/config/scripts, file tree navigation, and hybrid ranking. In the full Gobby-backed stack, required FalkorDB, Qdrant, and embedding sources provide graph-aware search, semantic search, opt-in graph expansion for exact symbol lookup (gcode search-symbol --with-graph), dependency analysis (callers, usages, imports, blast-radius), and Rust-owned graph/vector projection lifecycle. gcode graph clear --project-id <PROJECT_ID> is available for daemon stale-project graph cleanup without cwd project resolution.

For non-Gobby-managed projects, gcode init installs the bundled gcode skill for Claude Code, Codex, Droid, Grok, Qwen, and Antigravity CLI. Gobby-managed projects skip those project-local skill writes because Gobby owns CLI wiring.

gsqz — Output Compression

Squeezes CLI output before it eats your context window. 28 built-in pipelines for git, cargo, pytest, eslint, ruff, npm, and more. Filters noise, groups errors by rule, collapses repeats, and typically reduces token consumption by >90%. ~9ms overhead. YAML-configurable with layered config (global → project → CLI).

gloc — Local LLM Launcher

One command to launch Claude Code or Codex against a local LLM backend. Auto-detects LM Studio and Ollama, manages Ollama model lifecycle (pull, load, warmup), sets the right env vars, and execs into your CLI of choice. YAML-configurable with aliases, per-client env templates, and ordered backend priority.

ghook — Hook Dispatcher

Sandbox-tolerant hook dispatcher invoked by host AI CLIs (Claude Code, Codex, Gemini CLI, Qwen CLI) on lifecycle and tool-use events. Spools envelopes to ~/.gobby/hooks/inbox/ before POSTing to the local Gobby daemon, so the daemon's drain worker can replay any delivery lost to a sandbox FS-read denial, network blip, or daemon restart. You don't usually invoke it directly — Gobby wires it into your AI CLI for you.

gwiki — Research Knowledge Vault

Ingests multimodal sources — documents, PDFs, URLs, MediaWiki, git repos, Wayback snapshots, and audio/image/video — into a Markdown knowledge vault with frontmatter provenance and citations, then indexes and searches them with the same hybrid BM25 + semantic + graph stack as gcode. Compiles vault material into cited briefs, runs a reason-act research loop with step/token/source budgets, and answers questions directly with gwiki ask. Multimodal and AI capabilities degrade gracefully when transcription, vision, or the configured datastores are unavailable.

gobby-core underpins them all — a small shared-primitives library for project root walk-up, bootstrap config, daemon URL composition, setup/provisioning contracts, and datastore client adapters. It is not a standalone tool.

Documentation

• gcode User Guide — search, symbols, dependency graphs, project management
• gsqz User Guide — pipelines, step types, configuration, debugging
• gloc User Guide — backends, clients, model management, configuration
• ghook User Guide — hook wiring, diagnose mode, inbox/replay, troubleshooting
• gwiki Development Guide — research vault ingest, indexing, and hybrid search
• Release Guide — crate versions, tag order, and local binary installation
• Changelog — release history
• gcode README — architecture and build details
• gsqz README — architecture and build details
• gwiki README — architecture and build details

Install

Pre-built binaries

Download from GitHub Releases. Binaries are available for macOS (ARM/x86), Linux (x86/ARM), and Windows (x86/ARM).

From crates.io

# gcode
cargo install gobby-code

# gsqz
cargo install gobby-squeeze

# gloc
cargo install gobby-local

# ghook
cargo install gobby-hooks

# gwiki
cargo install gobby-wiki

gcode graph and semantic features are configured at runtime. There are no Cargo feature flags for FalkorDB, Qdrant, or embeddings support. Gobby-managed projects read FalkorDB settings from databases.falkordb.*; daemon-independent setups can use GOBBY_FALKORDB_HOST, GOBBY_FALKORDB_PORT, and GOBBY_FALKORDB_PASSWORD.

gcode 0.8.0+ uses the migrated Gobby PostgreSQL hub. It asks the local daemon broker for the hub DSN first. If the daemon is unavailable, it checks fallback sources in order: GCODE_DATABASE_URL, GOBBY_POSTGRES_DSN, ~/.gobby/gcore.yaml databases.postgres.dsn, then bootstrap database_url. Bootstrap fallback is valid only when hub_backend: postgres and bootstrap contains an inline database_url.

For daemon-independent service provisioning, use gcode setup --standalone. The default setup path is non-destructive. If incompatible code-index state is already present, rerun with gcode setup --standalone --overwrite-code-index only when you intend to reset all gcode-owned code-index PostgreSQL, FalkorDB, and Qdrant projection state.

Graph/vector lifecycle is code-index scoped. FalkorDB clears target-only code-index labels, and Qdrant clears target-only code_symbols_{project_id}; Gobby memory graph and memory vector collections stay outside this boundary.

Installing from source or crates.io requires Rust 1.88+.

From source

git clone https://github.com/GobbyAI/gobby-cli.git
cd gobby-cli
cargo install --path crates/gcode
cargo install --path crates/gsqz
cargo install --path crates/gloc
cargo install --path crates/ghook
cargo install --path crates/gwiki

Development

cargo build --workspace --no-default-features   # Build all tools
cargo nextest run --workspace --no-default-features # Test all tools except doctests
cargo test --doc --workspace --no-default-features  # Test doctests
cargo clippy --workspace --no-default-features -- -D warnings  # Lint all tools
cargo fmt --all --check                         # Check formatting

License

Apache 2.0 — see LICENSE.