gigarag-claude-code
v0.3.2
Published
The GigaRAG plugin for Claude Code. Commands, an indexing agent, hooks and an MCP server that carry the gigarag CLI inside them.
Readme
GigaRAG for Claude Code
Your GigaRAG knowledge base inside Claude Code.
Install
claude plugin marketplace add GigaRAG/marketplace
claude plugin install gigarag@gigarag --scope userSign in once. gigarag login runs in a terminal, and your terminal does not see the plugin's copy of the CLI, so install it too: npm install -g gigarag, or use the standalone installer. The plugin carries its own copy for Claude Code's use, and nothing else needs installing for that.
Commands
| Command | Does |
|---|---|
| /gigaindex [path] | Index a codebase into a bucket named for the repository |
| /gigasync | Update only the files that changed since the last index |
| /gigasave | Write this session's decisions into memos |
| /gigarecall <query> | Search, and load the results into the conversation |
| /gigadocs <url> | Ingest external documentation |
| /gigainbox | File imported items into memos in the right buckets |
| /gigaimport <source> | Write memos from a web page, transcript or document you can reach |
Hooks
- SessionStart adds a short index of your most recent memos to the session, says how many imported items are waiting for /gigainbox, and, at most once every 24 hours for a given newer version, whether a newer plugin version is out. It reads a local file and makes no network call itself.
- PostToolUse on Write, Edit, MultiEdit and NotebookEdit notes which files changed since the last index.
- Stop refreshes that index in the background when it is stale, and is also where the once-a-day check against npm for a newer version happens, never inside a hook itself. Set
GIGARAG_NO_UPDATE_CHECK=1to turn it off.
No hook runs on UserPromptSubmit. That one blocks every turn, and nothing here should.
Updating
claude plugin marketplace update gigarag
claude plugin update gigarag@gigaragThen restart Claude Code. SessionStart names the exact two commands above when a newer version is out, so you never need to check by hand.
How it finds the CLI
scripts/run.mjs uses, in order: the GIGARAG_CLI path, the copy in the plugin's cli/ folder, a gigarag on your PATH, then npx. A hook that cannot find any of them exits quietly and never breaks a session.
