Gittensory

Gittensory is a deterministic control plane for Gittensor OSS contribution work.

It helps contributors plan cleaner work, helps maintainers review with less public noise, and keeps private scoring, wallet, hotkey, and reviewability context out of public GitHub output.

It is not a Gittensor explorer, public leaderboard, reward-farming bot, wallet dashboard, or autonomous PR agent.

Privacy Boundary

Gittensory keeps sensitive context private by default.

• MCP local branch analysis sends metadata, not source contents.
• Public GitHub comments never include wallet, hotkey, reward estimate, private ranking, raw trust score, or reviewability context.
• Optional AI summaries receive compact deterministic signal bundles, not raw source code.
• Maintainer packets and scoring context stay on protected API/MCP surfaces.

See Privacy and security for the full boundary.

Review Capabilities

Gittensory CI and gittensory review score, gate, and comment on pull requests. The review algorithm is open-source; operators tune behavior through per-repo settings and the GITTENSORY_REVIEW_* feature flags, every one of which ships OFF and is opt-in per repo.

• Safety scan — defangs untrusted PR title/body/diff (prompt-injection neutralization) before the AI reviewer reads them, and scans the diff for leaked secrets, surfacing a secret_leak blocker.
• CI + full-file grounding — grounds the AI reviewer with the PR's finished CI status and the full post-change content of the changed files, so claims are verified against reality instead of predicted.
• Codebase RAG — retrieval-augmented context that queries the codebase vector index for related callers, modules, and conventions and appends them to the reviewer prompt (additive only; inert until an index exists).
• Submitter-reputation gating — an internal-only spend control that downgrades new / burst / low-reputation submitters to a deterministic-only review, never surfaced on any public comment, label, or check.
• Unified review comment — renders the public PR feedback as one in-place comment instead of multiple panels.
• Per-repo activation — capabilities roll forward (and back) one flag and one repo at a time via the GITTENSORY_REVIEW_REPOS allowlist.

See Review configuration for the full flag, setting, and .gittensory.yml reference.

Start Here

Audience	Start	Useful next links
Miners and contributors	Quickstart	MCP client setup, Miner workflow, Scoreability
Maintainers	GitHub App	Maintainer workflow, Privacy and security
Repo owners and operators	Beta onboarding	Upstream drift, Troubleshooting, Roadmap
Agent authors	Agents	API browser, MCP client setup

Surfaces

Surface	Link
Website	gittensory.aethereal.dev
Docs	gittensory.aethereal.dev/docs
MCP package	@jsonbored/gittensory-mcp
API	API browser and OpenAPI JSON
GitHub App	Install and setup docs
Browser extension	Extension page

MCP Install

npm install -g @jsonbored/gittensory-mcp@latest
gittensory-mcp login
gittensory-mcp doctor
gittensory-mcp --stdio

Print editor/client snippets:

gittensory-mcp init-client --print codex
gittensory-mcp init-client --print claude
gittensory-mcp init-client --print cursor

For full editor setup and stdio configuration, use MCP client setup.

Run base-agent commands:

gittensory-mcp agent plan --login jsonbored --json
gittensory-mcp agent packet --login jsonbored --json
gittensory-mcp agent status <run-id> --json

Local Development

npm install
npm run cf-typegen
npm run db:migrate:local
npm run dev

npm run test:ci

Release-only validation:

npm run test:release
npm run test:release:mcp

Frontend:

npm run ui:dev
npm run ui:build

Project Links

Need	Link
Contributing	CONTRIBUTING.md
Security	SECURITY.md
Support	SUPPORT.md
Changelog	CHANGELOG.md

Normal feature/fix PRs do not edit changelogs. Changelogs are release-prep artifacts.