Sheet 1

Your codebase, remembered.

Your coding agents write down what they learn, in a knowledge base tied to your repos. The next session reads it back. So do you.

Read the docs See the demo

How to get here

Add the marketplace
claude plugin marketplace add GitianDocs/gitian-tools
Install the plugin
claude plugin install gitian-kb@gitian-tools

Then start Claude Code. Your browser opens once to approve the connection.

ci

Topic · The test pipeline.

Doc:Split the test jobplan · in-progress
Memory:ci-flaky-oauth-token
Memory:ci-cache-key-includes-lockfile
Journal entry:Nightly suite green again9 Oct

Doc
Memory
Journal entry
Topic

One region per topic, one mark per item.Example knowledge base. Point at a region, or tab to it.

It writes as it works.

While your agent works, it publishes what it learns to the knowledge base over MCP, in three kinds: docs for work with a lifecycle, memories for one durable fact each, and a dated journal of what happened.

Split the test job
status in progress · next: move e2e to the nightly run
ci-flaky-oauth-token
The mocked OAuth token expires mid-run. Mint one per test.
Nightly suite green again
Journal · 9 Oct

Enlargement of the ci region, from the example knowledge base above.

It finds its way back.

Search in your words or the agent's. Full-text and meaning are searched together, so a paraphrase finds a note that shares none of its words. Topics connect related work, and rare topics count for more than umbrella ones.

why do e2e runs fail at random?

ci-flaky-oauth-tokenci · F5
Found by meaning. It shares no words with the question.
Session cookie rotationauth · E5
Related: the memory also touches the topic auth.

A search across two regions of the example knowledge base.

Nothing is overwritten.

Every write gets a URL and a history you can diff, and every revision records who wrote it. It survives /compact: compaction drops the conversation, not what was published.

gitian.dev/kb/acme/doc/split-the-test-job

Rev	Date	Written by	Change
3	12 Oct	Claude Code	Next steps revised
2	9 Oct	you	Status set to in progress
1	2 Oct	Claude Code	Published

Rev 2 to rev 3

next: split unit and e2e jobs

next: move e2e to the nightly run

After /compact, all three revisions are still at that URL. Example data.

Shared with your team.

An org knowledge base follows your GitHub org's seats. A personal one is never widened to anyone. Your agent reads every knowledge base you belong to and writes to one.

Your knowledge basesolid boundary
Personal. Never widened to anyone.
acme/teamdash-dot boundary
Org knowledge base. Follows the seats of the acme GitHub org.

The example knowledge base, with an org knowledge base offshore.

And your code, too.

Add @gitian to a comment you already wrote and it becomes a browsable annotation. A docs/ directory pairs files with their source by name, and a knowledge-base item can link straight to a symbol, and to the pull request that implemented it.

src/auth/session.ts

// @gitian:security Sessions are signed
// with ES256 only. A token with any
// other alg is refused.
export function verifySession(
  token: string,
) {
  …
}

Annotation · security

Sessions are signed with ES256 only. A token with any other alg is refused.

Paired by name: docs/auth/session.md

From a memory: [[repo:acme/app/src/auth/session.ts#verifySession]]

Example repository.

Start your map.

Install the plugin in Claude Code, or add the server to any agent that speaks MCP. Your first session draws the first region.

Read the docs

Add the marketplace
claude plugin marketplace add GitianDocs/gitian-tools
Install the plugin
claude plugin install gitian-kb@gitian-tools

Then start Claude Code. Your browser opens once to approve the connection.