setup-gbrain

Installs and configures the gbrain CLI with local PGLite or Supabase storage and MCP registration.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill setup-gbrain-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-gbrain
Source: https://github.com/raghavbadhwar/rstack/tree/main/setup-gbrain
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill setup-gbrain-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a persistent memory and knowledge backend for a coding agent involves many manual steps: installing the gbrain CLI, choosing a storage engine, registering an MCP server, and defining trust policies per repository. This Skill automates that entire bootstrap flow in one guided command. ## Core Features & Use Cases - End-to-end gbrain installation: Installs the gbrain CLI, initializes a local PGLite database or connects to Supabase, and registers the MCP server with the coding agent host. - Remote MCP mode (Path 4): Connects to a remote gbrain server over HTTP with a bearer token, verifying connectivity and classifying failures as NETWORK, AUTH, or MALFORMED with remediation hints. - Per-repo trust policy and transcript ingest: Captures read/write/deny trust policies per git remote and optionally ingests Claude Code and Codex session transcripts, learnings, and design docs into gbrain with optional gitleaks secret scanning. - Use Case: A developer on a new machine runs the setup once and gets a working semantic memory layer, so later sessions can query past conversations and project artifacts with gbrain search instead of cold-starting. ## Quick Start Ask the agent to set up gbrain on this machine, for example by saying "set up gbrain and connect it to this project".

Frequently Asked Questions about setup-gbrain

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

FAQPage Schema
How do I set up gbrain for my coding agent?

Run the setup-gbrain skill, which installs the gbrain CLI, initializes a local PGLite or Supabase brain, registers the MCP server, and captures per-remote trust policies. The flow is idempotent, so re-running it repairs missing pieces and prints a health verdict.

How do I connect to a remote gbrain server over MCP?

Use Path 4 of the setup flow: provide the MCP URL and a bearer token issued by the brain admin. The skill verifies connectivity, classifies failures as NETWORK, AUTH, or MALFORMED, and registers the server at user scope via the claude mcp add command.

Does gbrain setup support both PGLite and Supabase storage?

Yes, the setup flow lets you choose between a local PGLite database that stays on one machine or Supabase storage for multi-machine use. The active engine is recorded in a local cache file and can be inspected later.

Is my transcript data scanned for secrets before ingestion?

Per-file gitleaks scanning during memory ingest is opt-in and off by default. Enable it with the --scan-secrets flag or an environment variable; sessions with positive findings are skipped entirely rather than partially redacted.

What happens to repositories with a deny trust policy?

Repositories under a deny trust policy are skipped entirely during ingestion, meaning neither code nor transcripts from those repos enter gbrain. Trust policies are captured per git remote during the setup flow.

Why does the preamble say gbrain CLI is missing after setup?

This means the gbrain binary is not on your PATH or the MCP registration did not complete. Re-run the setup skill, which detects existing state, repairs only what is missing, and prints a GREEN, YELLOW, or RED verdict per row.