A plugin and CLI for Claude Code

Knowledge from every repo, in every session

Globu registers the knowledge bases on your machine and tells Claude Code which to read and where to write back.

Claude opens every session with an index of your knowledge

A hook prints one entry per registered repo. Claude opens a shard only when the task in front of it needs one.

Session startglobu hook session-start

# Globu knowledge shards

These knowledge sources are registered on this machine. When a task touches a shard's area, read its entry file first and follow links from there.

- product (okf, writable)
  - Location: ~/Projects/product
  - What: Decision records, feature specs, the roadmap and the API contract.
  - Use when: Why something was decided or what a feature should do.
  - Entry: ~/Projects/product/docs/index.md
- backend (okf, ask first)
  - Location: ~/Projects/backend
  - What: The API's request pipeline, data model, sessions and migrations.
  - Use when: Changing or calling an endpoint, the data model or a migration.
  - Entry: ~/Projects/backend/docs/index.md
- infrastructure (okf, read-only)
  - Location: ~/.globu/clones/infrastructure
  - What: Terraform for the environments, Cloud Run services and backups.
  - Use when: Anything about environments, deployment, secrets or restore.
  - Entry: ~/.globu/clones/infrastructure/docs/index.md

## Writing
Only edit shards marked writable. For a shard marked ask first, get the user's agreement in this session before editing it. To record what a session learned, use the globu:update-knowledge skill.

Nothing in a repo has to change

Globu reads your docs/ directories as they are and keeps everything about your set of repos in ~/.globu.

Base: A docs/ directory of Markdown: an index.md with the authoring guide, a dated log and concept docs with frontmatter. A repo can hold one per package, and knowledge about a piece of code goes in the nearest base above it.; docs/index.md
Shard: One registered repo with two lines of routing text and a mode. A read shard is never edited, an ask shard prompts before an edit from another repo and a write shard is open.; ~/.globu/manifest.yaml
Context: A named selection of shards, such as work or personal. The active context decides what a new session sees. The manifest is portable, so it can live in your dotfiles or in a team repo.; globu use work

From an empty repo to a session that knows

/globu:setup-knowledge-base
Give a repo a base
Creates docs/index.md and docs/log.md, or upgrades a base that is already there.
/globu:update-knowledge
Record what a session learned
Routes each decision, root cause or gotcha to the doc that owns it, logs it and validates. The edits ship with the code.
/globu:register-knowledge-base
Register the repo
Adopts it as a shard and drafts its routing text. A repo given by URL is cloned read-only under ~/.globu.
claude
Work from any other repo
The session starts with the index. Claude reads a shard when the task touches it and writes back within its mode.

Built to stay out of the way

Plain Markdown, any editor

Bases follow OKF: frontmatter, an index and a log. People and agents edit the same files, and globu base validate checks the structure, never the prose.

docs/architecture.md

---
type: "Architecture"
title: "Request pipeline"
description: "How a request moves from the edge to the database."
---

Three modes

Not every repo may be edited from everywhere. A hook enforces the mode for the file tools and, best effort, for shell commands.

read: Never edited. Clones made from a URL start here.
ask: Edits from other repos prompt first.
write: Open from anywhere.

One manifest per team

Keep a manifest.yaml in a shared repo. A new laptop or a CI job imports it and clones what is missing.

globu import --yes git@github.com:team/kb.git
globu sync

Hooks do the enforcing

The plugin wires three Claude Code hooks, so the rules hold whether or not anyone remembers them.

Session startPrints the shard index for the directory the session runs in.
GuardBlocks edits to read shards and asks before edits to ask shards.
ValidateChecks a base right after an edit and hands errors back at once.

See when knowledge falls behind

The optional globu-status mod counts the edits since the last update and offers one key to run it.

○ nothing to update
◔ low
◑ medium
● strong
✓ up to date

Install

The plugin runs its CLI from an npm package that Claude Code installs with it, so node 22 or newer and npm must be on the PATH.

Latest release 0.4.0, 23 October 2026. Source on GitHub, the CLI on npm.

In a terminal, for Claude Code

$ claude plugin marketplace add kamilziajka/globu$ claude plugin install globu@globu

Optional: the status mod

$ claude plugin install globu-status@globu

The CLI on its own

$ npm install -g @kazet/globu$ globu base --help