Skip to content
For miners

Pick better work. Preflight branches. Ship cleanly.

Gittensory's MCP and CLI give you private, deterministic context for every contribution: lane fit, blockers, scoreability scenarios, and the next actions most likely to clear the gate.

Plan next work
Lane-aware repo targets to pursue or avoid, with risk-adjusted priority.
Preflight branches
Metadata-only analysis of your current branch — labels, refs, linked issues, commits.
Explain blockers
Cleanup-first guidance: queue pressure, missing issue links, unsquashed commits, validation gaps.
Prepare PR packets
Compose public-safe PR descriptions that read well to maintainers without leaking private signals.
Zero PAT
Sign in via GitHub Device Flow. Session tokens are Gittensory-issued, not your personal access tokens.
Drift-aware
When upstream Gittensor scoring shifts, your CLI warns you before you act on stale assumptions.
Four commands

A miner's loop, end to end.

1 · Sign in

GitHub Device Flow

Authorize the CLI without ever pasting a PAT. The session token is a Gittensory token backed by your GitHub identity.

gittensory-mcp login
gittensory-mcp whoami
2 · Plan

Get a decision pack

Lane fit, repo targets, freshness, and the ranked next actions that move you forward.

gittensory-mcp agent plan --login your-login --json
3 · Preflight

Analyze the branch

Metadata-only branch analysis returns lane context, scoreability scenarios, branch + account blockers, and maintainer-fit notes.

gittensory-mcp analyze-branch --login your-login --json
gittensory-mcp preflight --login your-login --json
4 · Packet

Compose the PR packet

Public-safe PR description and ranked actions to take before opening or pushing. Private signals stay local.

gittensory-mcp agent packet --json
No source upload. The MCP sends metadata only: refs, changed-file metadata, labels, linked issues, commit messages, validation summaries, optional local scorer output.
How it fits your day

A calm contributor loop.

Three small moments where Gittensory removes guesswork without getting in your way.

Step 1 · Morning

Pick what to work on

Open the CLI; pull a fresh decision pack. Lane fit and ranked next actions are ready before your coffee.

Step 2 · Mid-flow

Preflight the branch

One command analyzes your branch metadata and tells you what would block scoreability before you push.

Step 3 · Before opening a PR

Compose a public-safe packet

A ready-to-paste PR description with linked issues and labels — no private signals leak into GitHub.

Install the MCP and try it

Two commands, no PAT, no source upload. You can also explore the agent playground first.