loopover

# LoopOver _Formerly LoopOver._ <p align="center"> <a href="https://github.com/JSONbored/loopover/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/JSONbored/loopover/actions/workflows/ci.yml/badge.svg" /></a> <a href="https://www.npmjs.com/package/@loopover/mcp"><img alt="MCP package" src="https://img.shields.io/npm/v/@loopover/mcp?label=mcp" /></a> <a href="https://github.com/JSONbored/loopover/blob/main/LICENSE"><img alt="License" src="https://img.shields.io/github/license/JSONbored/loopover" /></a> <a href="https://gittensory.aethereal.dev/docs"><img alt="Docs" src="https://img.shields.io/badge/docs-gittensory.aethereal.dev-0b6bcb" /></a> <a href="https://gittensor.io/miners/repository?name=JSONbored/loopover"><img alt="Gittensor impact" src="https://api.gittensor.io/repos/JSONbored%2Floopover/badge.svg" /></a> </p> LoopOver 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 also the single converged home of the native review system; the legacy separate reviewbot repo/runtime is not part of the active architecture described here. It is not a Gittensor explorer, public leaderboard, reward-farming bot, wallet dashboard, or autonomous PR agent. ## Privacy Boundary LoopOver 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](https://gittensory.aethereal.dev/docs/privacy-security) for the full boundary. ## Review Capabilities LoopOver CI and LoopOver review score, gate, and comment on pull requests. The review algorithm is open-source; operators tune behavior through per-repo settings and the `LOOPOVER_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. With `.loopover.yml`'s `review.changed_files_summary` also on (off by default), it gains a deterministic, no-AI "Changed files" collapsible: one row per file category (source/test/docs/config/generated), with file counts and +/- totals. - **Per-repo activation** — capabilities roll forward (and back) one flag and one repo at a time via the `LOOPOVER_REVIEW_REPOS` allowlist. **Check-run and comment surfaces, disambiguated** (a common point of confusion — these are three independent, separately-configured things, not layers of the same feature): - **`LoopOver Orb Review Agent`** (`gate.*` / `settings.reviewCheckMode`, off by default) — the authoritative GitHub Check Run carrying the gate's pass/fail verdict. This is the one worth making a required status check. - **`LoopOver Context`** (`settings.checkRunMode` / `settings.checkRunDetailLevel`, off by default) — a separate, purely advisory Check Run. At its default `checkRunDetailLevel: minimal` it publishes no findings at all; even at `standard`/`deep` it only re-renders content already shown elsewhere. Never make this one required. - **Inline review comments** (`LOOPOVER_REVIEW_INLINE_COMMENTS` + `.loopover.yml`'s `review.inline_comments`, off by both by default) — real, reply-able line-anchored PR review comment threads (CodeRabbit-style). This is the ONLY one of the three that posts an interactive per-line thread; the two check runs above never do. With `.loopover.yml`'s `review.suggestions` also on, a precise line-anchored fix is additionally rendered as a one-click, committable GitHub suggested-change block. With `review.finding_categories` also on (off by default), each finding is additionally tagged with a category — security/correctness/performance/maintainability/tests/style — in both the inline comment label and the unified comment's "Finding categories" collapsible; a deterministic path/keyword fallback covers whatever the model omits. See [Tuning your reviews](https://gittensory.aethereal.dev/docs/tuning) for the full flag, setting, and `.loopover.yml` reference. ## Start Here | Audience | Start | Useful next links | | ------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Miners and contributors | [Quickstart](https://gittensory.aethereal.dev/docs/quickstart) | [MCP client setup](https://gittensory.aethereal.dev/docs/mcp-clients), [Miner workflow](https://gittensory.aethereal.dev/docs/miner-workflow), [Scoreability](https://gittensory.aethereal.dev/docs/scoreability) | | Maintainers | [GitHub App](https://gittensory.aethereal.dev/docs/github-app) | [Maintainer workflow](https://gittensory.aethereal.dev/docs/maintainer-workflow), [Self-host reviews](https://gittensory.aethereal.dev/docs/maintainer-self-hosting), [Privacy and security](https://gittensory.aethereal.dev/docs/privacy-security) | | Repo owners and operators | [Beta onboarding](https://gittensory.aethereal.dev/docs/beta-onboarding) | [Upstream drift](https://gittensory.aethereal.dev/docs/upstream-drift), [Troubleshooting](https://gittensory.aethereal.dev/docs/troubleshooting), [Roadmap](https://gittensory.aethereal.dev/roadmap) | | Agent authors | [Agents](https://gittensory.aethereal.dev/agents) | [API browser](https://gittensory.aethereal.dev/api), [MCP client setup](https://gittensory.aethereal.dev/docs/mcp-clients) | ## Surfaces | Surface | Link | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Website | [gittensory.aethereal.dev](https://gittensory.aethereal.dev/) | | Docs | [gittensory.aethereal.dev/docs](https://gittensory.aethereal.dev/docs) | | MCP package | [@loopover/mcp](https://www.npmjs.com/package/@loopover/mcp) | | Engine package | [`@loopover/engine`](packages/loopover-engine/README.md) — shared deterministic logic for the review stack and miner | | Miner package | [`@loopover/miner`](packages/loopover-miner/README.md) — local foundation CLI for the autonomous miner runtime | | API | [API browser](https://gittensory.aethereal.dev/api) and [OpenAPI JSON](https://gittensory-api.aethereal.dev/openapi.json) | | GitHub App | [Setup docs](https://gittensory.aethereal.dev/docs/github-app) — self-hosting is the only currently available path | | Browser extension | [Extension page](https://gittensory.aethereal.dev/extension) | ## MCP Install ```sh npm install -g @loopover/mcp@latest loopover-mcp login loopover-mcp doctor loopover-mcp --stdio ``` Print editor/client snippets: ```sh loopover-mcp init-client --print codex loopover-mcp init-client --print claude loopover-mcp init-client --print cursor ``` For full editor setup and stdio configuration, use [MCP client setup](https://gittensory.aethereal.dev/docs/mcp-clients). Run base-agent commands: ```sh loopover-mcp agent plan --login jsonbored --json loopover-mcp agent packet --login jsonbored --json loopover-mcp agent status <run-id> --json ``` ## Local Development ```sh npm install npm run cf-typegen npm run db:migrate:local npm run dev ``` ```sh npm run test:ci ``` Release-only validation: ```sh npm run test:release npm run test:release:mcp ``` Frontend: ```sh npm run ui:dev npm run ui:build ``` ## Gittensor Contributor Impact <p align="center"> <a href="https://gittensor.io/miners/repository?name=JSONbored/loopover"> <img src="https://raw.githubusercontent.com/JSONbored/loopover/gittensor-impact-assets/gittensor-impact-dark.svg" alt="Gittensor contributor impact" width="600"> </a> </p> Refreshed weekly by [`.github/workflows/gittensor-impact.yml`](.github/workflows/gittensor-impact.yml). ## Project Links | Need | Link | | ------------ | ---------------------------------- | | Contributing | [CONTRIBUTING.md](CONTRIBUTING.md) | | Security | [SECURITY.md](SECURITY.md) | | Support | [SUPPORT.md](SUPPORT.md) | | Changelog | [CHANGELOG.md](CHANGELOG.md) | Normal feature/fix PRs do not edit changelogs. Changelogs are release-prep artifacts.