Skip to content
bluei

Autonomous Repository Health. bluei — Autonomous repository health.

bluei tends your repos on a schedule. It inspects your projects, finds issues, fixes them, opens PRs, does the PR review and tracks the health over time. Runs on your machine. Nothing happens without your permission.

Register your project See how it works
$ curl -fsSL https://bluei.dev/install | bash
THE SWEEP

Scans every surface.
Misses nothing.

bluei inspects your codebase the way a cleaner wrasse inspects a reef — methodically, thoroughly, and without missing a spot. Every sweep runs lint, type-check, pattern detection, and secret scanning in one pass.

$ bluei sweep $ bluei scan

Multi-language scanning

Covers 8 languages out of the box. JavaScript, TypeScript, Python, Rust, Go, and more. One sweep, full coverage.

Secret scanning

Runs gitleaks under the hood. API keys, tokens, credentials — catches what should never be committed.

19 pattern detectors

Built-in checks for common code smells: unused imports, missing error handling, inconsistent naming, and beyond.

7 external linters

Integrates ESLint, Ruff, Clippy, and others. bluei runs what your project already uses, then adds its own eyes.

4 fix backends

Tries template fixes first, then heuristic patches, then LLM-powered generation via Claude or OpenCode. Falls back gracefully.

Batch PR creation

Groups related fixes into a single pull request. One review, one merge, many problems solved.

Autonomous PR review

Reviews its own fixes before opening them. Catches false positives before they reach your inbox.

4 safety modes

Observe, issue-only, PR, or auto-merge. You decide how much autonomy bluei gets. Start silent, build trust.

THE FIX

Finds it. Fixes it.
Opens the PR.

Finding issues is only half the job. bluei generates patches, runs them through its own review, and opens pull requests — grouped by category, scoped to what changed. You review. You merge. The routine was handled.

$ bluei fix $ bluei batch
THE PULSE

Health you can see.
Trends you can track.

A clean repo today means nothing if it rots tomorrow. bluei tracks vitality over time, surfaces trends, and generates reports — so you can see the reef getting healthier with every sweep.

$ bluei vitality $ bluei report
VITALITY 87/100 +4 this week
SPECKS FOUND 23 3 critical
FIX PRS OPEN 4 2 auto-merged
LANGUAGES 8 all passing

Vitality score

0 to 100. Nine weighted components: lint health, type coverage, test gaps, docs freshness, dependency state, and more. One number, full picture.

Self-healing

Clears stale locks, removes orphaned worktrees, survives reboots. bluei maintains itself so it can maintain your repos.

5 report formats

PDF, HTML, Markdown, JSON, or WhatsApp. Share health reports with your team in whatever format they actually read.

CI/CD generation

Generates GitHub Actions workflows and pre-commit hooks. Installs discipline without nagging.

HOW IT WORKS

From issues to healthy repo
in four easy steps.

1

Register

Point bluei at a repo. It learns the language, framework, and structure in one pass.

bluei register
2

Sweep

Runs on schedule — lint, type-check, pattern detection, secret scanning. Silence means clean.

bluei sweep
3

Fix

Issues become patches. Fix engine generates fixes, reviews them, opens PRs. Safety mode controls what ships.

bluei fix
4

Track

Vitality updates every sweep. Reports surface trends. The reef gets healthier.

bluei vitality
WHY BLUEI

Fills the gap between
maintainers and codebase.

Here is what having an autonomous maintainer actually looks like.

The inherited repo

Took over a project with 200+ lint errors across 3 languages. bluei registered, scanned, and opened batch fix PRs in one sweep.

The quiet month

Haven't touched a side project in weeks. bluei runs on cron. No notifications means everything is clean. Silence is proof.

The pre-release check

About to cut v2.0. bluei catches a leaked API key, 3 type errors, and a stale test. Before the release, not after.

The team standard

New convention decided in standup. bluei learns it, scans for violations, and enforces through action — not nagging.

SAFETY MODES

You decide how much
autonomy it gets.

Start in observe. Watch what it finds. When you trust the fixes, move up. Every mode is explicit — nothing happens by surprise.

Observe

watching

Scan only. Reports what it finds. No issues, no PRs, no code changes. Pure visibility.

Issue

reporting

Creates GitHub issues from findings. Categorized, labeled, linked to source. No code changes.

PR

fixing

Opens fix pull requests. Grouped by category. You review and merge. The routine was handled.

Auto-merge

autonomous

Fixes and merges. For repos you trust bluei with. High-confidence fixes only. Full audit trail.

$ bluei safety set observe · $ bluei safety set issue · $ bluei safety set pr · $ bluei safety set auto-merge

THE WORKBENCH

19 commands. One sweep.

Everything from registration to self-healing. Most commands run once and forget. The rest are there when you need them.

Setup
$ bluei register <repo> $ bluei init
Scanning
$ bluei sweep $ bluei scan
Fixing
$ bluei fix $ bluei batch
Health
$ bluei vitality $ bluei report
Config
$ bluei config $ bluei safety
Maintenance
$ bluei status $ bluei self-heal
Full command reference View on GitHub
FAQ

Common questions.

What is bluei?
bluei is an autonomous repository health service. It tends your codebase on a schedule — scanning for issues across 8 languages, creating GitHub issues, opening fix pull requests, and tracking health over time. It runs on your machine, not in the cloud.
Which languages does bluei support?
8 languages out of the box: JavaScript, TypeScript, Python, Rust, Go, Ruby, Java, and C/C++. Each language gets its own set of linter integrations and pattern detectors.
How does the vitality score work?
The vitality score runs 0–100 and is calculated from 9 weighted components: lint health, type coverage, test gaps, documentation freshness, dependency state, secret scan results, pattern violations, code complexity, and consistency score. It updates after every sweep.
What are safety modes?
Four levels of autonomy. Observe scans and reports only. Issue creates GitHub issues without touching code. PR opens fix pull requests for your review. Auto-merge fixes and merges directly. You choose the level. Start silent, build trust.
Does bluei modify my code without permission?
Never in observe or issue mode. In PR mode, it opens pull requests — you review and merge. In auto-merge, it only merges high-confidence fixes with a full audit trail. The default is observe. Nothing happens by surprise.
Is bluei free and open source?
Yes. AGPL-3.0 licensed. Free to use, modify, and self-host. Runs entirely on your machine. No cloud, no accounts, no telemetry.
How is bluei different from a linter?
Linters find problems. bluei finds problems, fixes them, opens PRs, tracks health over time, generates CI/CD config, scans for secrets, and runs on a schedule without you thinking about it. A linter is one of bluei's tools, not the whole job.
HOW WE COMPARE

See how bluei stacks up.

Honest comparison of bluei against DeepSource, SonarQube, and GitHub Copilot Autofix. No marketing fluff — just a feature matrix and honest tradeoffs.

View comparison
bluei GET STARTED

Start your first sweep. Register bluei — Autonomous repository health.

Register a project and bluei will inspect it, find issues, fix them on a schedule, and track your codebase's health over time.

terminal
$ curl -fsSL https://bluei.dev/install | bash

Free and open source · 8 languages · runs on your machine