grepai-storage-gob

Configure GOB local file storage as the vector index backend for GrepAI.

Updated May 12, 2026
One-click install
npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill grepai-storage-gob-eduardtomasek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grepai-storage-gob
Source: https://github.com/eduardtomasek/codex-dev-stack/tree/main/skills/.agents/grepai-storage-gob
Command: npx skills add https://github.com/eduardtomasek/codex-dev-stack --skill grepai-storage-gob-eduardtomasek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up semantic code search requires choosing and configuring a storage backend for vector embeddings, and developers on single-machine setups need a simple option without external database dependencies. ## Core Features & Use Cases - GOB Backend Configuration: Set up GrepAI's default Go Binary storage backend with minimal YAML configuration in .grepai/config.yaml. - Index Lifecycle Operations: Create, inspect, back up, clear, and rebuild the index.gob and symbols.gob files using grepai commands. - Migration Guidance: Move from GOB to PostgreSQL or Qdrant backends when the codebase outgrows local file storage. - Use Case: A solo developer working on a medium-sized codebase initializes GrepAI with GOB storage, monitors index size via grepai status, and backs up the index before switching embedding models. ## Quick Start Configure GrepAI to use GOB local file storage and create the vector index for my current project.

Frequently Asked Questions about grepai-storage-gob

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure GrepAI to use GOB storage?▼

Set the store backend to gob in .grepai/config.yaml, which is the default configuration. Then run grepai init followed by grepai watch to create the index.gob file containing vector embeddings.

What is GOB storage in GrepAI?▼

GOB is Go's native binary serialization format used by GrepAI to store vector embeddings, file metadata, and chunk information in a single local file. It requires no external services and is the default storage backend.

When should I migrate from GOB to PostgreSQL or Qdrant?▼

Migrate when the index exceeds 1 GB, when you need concurrent access from multiple users, when sharing an index across a team, or when the codebase grows beyond roughly 50,000 files. Update the backend in config.yaml and re-index.

Can I share a GrepAI GOB index across machines?▼

Sharing is not recommended because the index requires an identical embedding model, contains absolute file paths, and may reflect different code versions. Each developer should run their own grepai watch to generate a local index.

How do I fix a corrupted GrepAI GOB index?▼

Delete the corrupted index files and re-index from scratch. Remove .grepai/index.gob and .grepai/symbols.gob, then run grepai watch to rebuild the vector and symbol indexes.