Repository navigation
Releases
CodeOtter v0.8.1 - Hosted first-run fixes
Hosted installs (Railway, Render, any container without a git checkout) now start cleanly and go straight into onboarding.
Fixes
- Container start without
PB_ADMIN_EMAIL.bin/start.shnow exports its PocketBase admin defaults, so the server signs in with the superuser it just created instead of crashing withPocketBase auth 400. - No default repository outside a checkout. A new hosted install starts with no repositories and opens onboarding, instead of showing
dharmeshgurnani/CodeOtter. - GitHub App manifest accepted. Create app no longer asks for the
installation_repositoriesevent, which GitHub rejected ("Default events unsupported"). - GitHub App install returns to onboarding. New apps no longer request sign-in during installation. Apps created that way earlier land back on onboarding (or Git providers) instead of "Sign-in state mismatch" on the login page.
Also
- README: deploy buttons first, a comparison table and shorter feature tiles.
Upgrade
- Docker installs with Watchtower update on their own within the hour. To hold back, pin
ghcr.io/dharmeshgurnani/codeotter:0.8.0.
Full list in CHANGELOG.md.
CodeOtter v0.8.0 - GitHub Marketplace action and TypeScript
CodeOtter is on GitHub Marketplace. The new CodeOtter Review action sends a repository's pull requests to your own CodeOtter server from a workflow, with no GitHub App install and no relay. The backend is now strict TypeScript.
Highlights
- GitHub Action on Marketplace. CodeOtter Review posts a workflow's
pull_requestandissue_commentevents to/webhooks/github, signed with the instance's new Action secret (Settings → System → Git providers → GitHub; repository secretCODEOTTER_SECRET). The server URL comes fromurl:incodeotter.ymlon the default branch, so a pull request cannot redirect it. Setup: docs.codeotter.io/docs/github-action. - TypeScript.
core/,tui/,bin/,test/andweb/scripts/are strict TypeScript, run directly by Node's type stripping with no build step.pnpm typecheckruns in CI and beforepnpm test.
Also new
- Re-creating the GitHub App with Create app keeps the webhook forwarder and Action secrets, so running forwarders and Action workflows keep working.
- Malformed API request fields are treated as empty instead of failing with a TypeError.
Upgrade
- Node 22.18 or later for installs outside Docker.
pnpm startrunsnode core/server.ts, and thecodeotterCLI istui/codeotter.ts. - Docker installs with Watchtower update on their own within the hour. To hold back, pin
ghcr.io/dharmeshgurnani/codeotter:0.8or:0.8.0, or stay on:0.7.
Full list in CHANGELOG.md.
CodeOtter v0.7.0 - Bitbucket, Azure DevOps and webhooks
CodeOtter now reviews pull requests wherever your code lives: Bitbucket Cloud, Bitbucket Data Center and Azure DevOps join GitHub, Forgejo and Gitea. Pull requests arrive by webhook into one review queue, teams get a developer role with per-repository access and invites, and CodeOtter is open source under the AGPL-3.0.
Highlights
- Bitbucket and Azure DevOps. Bitbucket Cloud (
bitbucket~workspace/repo), Bitbucket Data Center (bitbucketdc~PROJECT/repo) and Azure DevOps Services (azure~org/project/repo) get the same reviews as the others: inline suggestions, scores and triage statuses, PR tools, comment commands and auto-review. Connect them under Settings → System → Git providers. Sign-in adds Bitbucket and Microsoft (Entra ID, pinned to one tenant). - Webhooks and one review queue. GitHub Apps made with Create app carry a webhook, and onboarding a Forgejo, Gitea, Bitbucket or Azure DevOps repository registers its hook. Deliveries are signature-checked, de-duplicated and answered before work starts. Webhooks, the catch-up poll and the local forwarder all feed one queue that reviews one pull request at a time. A failed auto-review is retried three times, ten minutes apart.
- Auto-review. New and updated pull requests in onboarded repositories are reviewed and posted without a command. Drafts and PRs labelled
codeotter:skipare left alone. - Developer role, repository access and invites. Developers see Home and the repositories assigned to them on Manage accounts, and nothing else. After the first (owner) account, signing in needs an invite.
- Repository settings. Review settings are per repository, under each repository in the sidebar: findings, diff size, context, self-check, what gets posted, auto-review and comment commands, plus guidelines and team learnings.
- Open source. CodeOtter is licensed under the GNU AGPL-3.0 (was Elastic License 2.0).
Also new
- Git providers and Auth providers are separate pages. Create app sets up a GitHub App, or a Forgejo or Gitea OAuth app, in one click.
- One table and one badge style across the app. The reviews list shows verdict, author and effort.
- Forward webhooks here gives a localhost instance webhook events through
gh webhook forward. - OpenAI-compatible endpoints send
max_tokensfor Claude 4 and later, and notemperaturefor Claude 5. - The CLI, TUI and MCP server review through the same engines as the web app. A configured System One model owns every score and gate there too.
- Documentation moved to docs.codeotter.io.
Under the hood
- The backend is one module per subsystem under
core/and serves HTTP with Hono, with one route module per area and access checks as route middleware.honoand@hono/node-serverare its only dependencies. - Unknown
/api/*paths now answer a JSON 404. Request bodies over 1 MB (webhooks 2 MB) answer 413. - Every
ghcall is asynchronous, so one slow call no longer blocks the rest of the server./healthzreports storage health. - Tests run on
node:test, Vitest and a Playwright smoke run, plus a Docker-backed Forgejo and Gitea end-to-end suite.
Upgrade
- Sign-in needs an invite after the first account. Uninvited sign-ins used to become admin; they are now refused and their account deleted. Existing accounts keep their roles. Invite people under Settings → Workspace → Manage accounts.
- VPS installer URL:
https://raw.githubusercontent.com/dharmeshgurnani/CodeOtter/main/bin/install.sh(was the repository root). - CLI:
--no-critiqueis gone, since findings always go through the self-check. A flag without a value, or a non-numeric--min-score, now exits 2. - The browser forgets the remembered organization and onboarding flag once, because their storage keys were renamed.
- Docker installs with Watchtower update on their own within the hour. To hold back, pin
ghcr.io/dharmeshgurnani/codeotter:0.7or:0.7.0, or stay on:0.6.
Full list in CHANGELOG.md.
CodeOtter v0.6.0 - Cloudflare Clef, PR commands and self-checked reviews
CodeOtter now works more like a reviewer on your team: it answers commands in PR comments, writes descriptions, docs and changelog entries, checks its own findings before you see them, and remembers the fixes your team accepted. Cloudflare Clef joins Jev as a hosted System One model.
Highlights
- Cloudflare Clef. New hosted System One provider:
cloudflare/clef(27B) andcloudflare/clef-flash(9B), through OpenRouter, on the same typed endpoint as Jev. Clef scores the PR and answers the merge gates; switching between Jev and Clef is one dropdown under Admin → Model provider → System One. - PR comment commands. A comment starting with
/review,/describe,/improve,/ask <question>,/docsor/changelogruns that action and replies on the PR. Owners, members and collaborators only. Off by default: Admin → Model provider → Review → PR comment commands. - Tools card. Describe (title, type, summary, file table; writes into the PR description), Ask, Improve (ranked, self-checked, multi-line committable suggestions), Docs (missing doc comments as suggestions) and Changelog (an entry in your repository's own changelog style).
- Self-check. Each language model finding is scored 0-10 against the diff by a second pass; weak ones are dropped and the score shows on each finding. Default minimum 5.
- Accepted fixes. On a re-review, suggestions the author applied are recorded per repository and guide later reviews. Editable under Settings → Repositories → ⚙️ → Accepted fixes.
Better context
- Dynamic context. Hunks extend up to their enclosing function, method or class (12 languages), trailing context cut to one line. Admin → Model provider → Review → Context above a change.
- Large pull requests. Diffs over the budget are no longer cut at a character count: files are ranked and added whole, oversized files show their leading hunks, deletions are listed, and every file left out is named.
Fixes
- The Tools card's apply buttons (Update PR description, Post inline suggestions) now appear.
- OpenRouter System One model lists work again.
- Forgejo/Gitea integration tests run again and cover the new features.
Upgrade
Docker installs with Watchtower update on their own within the hour. Pin ghcr.io/dharmeshgurnani/codeotter:0.6 or :0.6.0 to hold back.
Full list in CHANGELOG.md.
CodeOtter v0.5.0 - One-click deploy, auto-updates and fast triage
CodeOtter now has a home at codeotter.io, installs in one line on any Linux server, and keeps itself up to date. System One also triages every new pull request before your CI spends minutes on it.
Highlights
- One-click deploy.
curl -fsSL https://raw.githubusercontent.com/dharmeshgurnani/CodeOtter/main/install.sh | bashsets up Docker, a generated PocketBase password and Watchtower; addCODEOTTER_DOMAIN=review.example.comfor Caddy HTTPS. Deploy to Azure and Render buttons in the README, Linode StackScript indeploy/. - Automatic updates. Every release publishes
ghcr.io/dharmeshgurnani/codeotter(:latest,:0.5.0,:0.5; amd64 and arm64). Compose runs Watchtower, which updates the CodeOtter container hourly. Admins see "vX.Y.Z available" in the sidebar. Pin:0.5or:0.5.0to hold back. - Fast triage. System One rates correctness risk and blast radius of each new or updated PR (polled every 2 minutes) and sets the
codeotter/triagecommit status, plus an updatable PR comment when Post scores is on. About 80 seconds with Kev 0.8B on CPU. Gate your CI with the job in docs/ci-triage.md. - Scores come from a model or not at all. The rule-based stand-in is gone. If System One fails to start, errors or skips a question, the review fails with the model's error on screen and nothing is posted.
- System One checks CodeReviewer. Each CodeReviewer comment is judged with its hunk; only comments naming a concrete problem (confidence ≥ 0.7) become findings.
Catalog
- Kev 4B (4,498 MB, Apache-2.0) on Admin → Local models: the most accurate Kev, about five times slower than Kev 0.8B on CPU; best with a GPU.
- llama.cpp runtime b11388 (was b11215); Linux arm64 tries the Vulkan build first. Existing installs keep their downloaded runtime until
runtime/llamain the data directory is removed. - Laya runtime 0.9.7 (fixes "Illegal instruction" on CPUs without AVX-512, i.e. Docker on most laptops).
- Small-context System One models (Laya, Kev 0.8B) read a digest of the whole change and show an info icon on their cards. Onboarding preselects Kev 0.8B.
- Anthropic models:
claude-opus-5-5,claude-sonnet-5-5,claude-haiku-4-5.
Upgrade notes
- New GitHub App installs request
statuses: writefor triage. Existing installs need to accept the new permission to use it. - Free to self-host under the Elastic License v2.
Full list in the CHANGELOG. Docs: codeotter.io/docs.
CodeOtter v0.4.0 - Forgejo, Gitea and unified OAuth
CodeOtter now supports GitHub, Forgejo and Gitea in the same installation. Provider connections and sign-in settings are consolidated under one Admin / OAuth sidebar link.
Changes
- Add Forgejo and Gitea OAuth sign-in with PKCE. Sign-in provider and repository access are independent.
- Review private repositories, load root guidelines (including fork heads), inspect linked issues and commit history, re-review new commits, update PR comments and post inline suggestions on both self-hosted providers.
- Keep credentials, repository settings, reviews and organization scopes separate across providers, including identically named repositories.
- Consolidate server URLs, access tokens, connection tests and OAuth credentials under Admin / OAuth. Old provider settings links redirect there.
- Preserve existing GitHub and Forgejo repository IDs and sign-in configuration.
Validation
- Production frontend build and browser checks passed.
- Isolated integration suites passed against Forgejo 15 and Gitea 1.24.6 with PocketBase 0.40.4, including all three providers together and JSON storage.
- Real Forgejo/Gitea OAuth tested; GitHub OAuth and model responses use local fixtures. Live installation credentials were not changed.
Setup and limits
Configure each provider under Admin / OAuth, then add repositories in Settings / Repositories. PocketBase is required for sign-in. The included OAuth account migration disables password sign-in and permits accounts without a provider-verified email.
One Forgejo origin and one distinct Gitea origin are supported; URL subpaths are unsupported. Self-hosted re-reviews use the full PR diff plus commit history. GitHub outside-diff caller search is not applied to these repositories.
See the README for setup.
CodeOtter v0.3.0 — Smart Context & Advanced Review Automation
What's New in CodeOtter v0.3.0
🌐 Smart Context Outside-Diff Call Graph Impact Slicing
- Solves the core blindspot of diff-only AI reviewers by parsing modified symbols across TypeScript, Python, Go, and Rust, then tracing un-modified caller files across the repository via fast zero-dependency git search.
- Injects exact outside-caller invocation snippets into review prompts and System 1 state, mandating verification that modified contracts and exceptions do not break production call sites.
- Upgrades Blast Radius to compute actual call-graph fan-out, rendering outside-caller nodes in the Mermaid architecture graph and GitHub PR comments.
💡 Inline Line-Level suggestion Fixes & GitHub PR Review Thread Sync
- Generates precise
:L<line>anchors and replacement code blocks rendered as interactive Suggested Fix cards with green+diff highlighting and 1-click "Copy fix". - Adds "Post inline suggestion to GitHub" (
POST /api/review-suggestions) to publish committable GitHubsuggestionblocks directly on PR lines so developers can apply fixes in one click.
⚡ Incremental Commit-by-Commit Delta Reviews & In-Place Comment Upsert
- Compares
prevSha...headShacommits and diffs on re-review, auditing and reporting resolved prior findings (✅ Resolved since prevSha). - Replaces duplicate comment spam with in-place updating of GitHub PR review comments (
<!-- codeotter:scores -->and<!-- codeotter:review -->).
🧠 Repository Institutional "Learnings"
- 1-click "Dismiss & remember rule" persists team conventions into
repoSettings[repo].learnings, auto-injected into future LLM and System 1 prompts.
🎯 Linked GitHub Issue & Requirement Validation (Closes #123)
- Automatically detects linked issues across PR titles, bodies, and branch names, verifying acceptance criteria fulfillment and enforcing the
issue_requirementsmerge gate.
📊 Offline Architecture & Blast Radius Mermaid Diagrams
- Generates 100% offline SVG flowchart diagrams in the review terminal and GitHub PR comments with raw Mermaid source toggles.
📱 Mobile-Responsive UI
- Drawer auto-closing on navigation, stacked table views, and layout overflow containment.
CodeOtter v0.2.0
What's New in CodeOtter v0.2.0
✨ New Features
- Hugging Face Model & Provider Icons: Official Hugging Face organization and model avatars are now displayed across the Model Provider picklists and Local Models rows.
- Side-by-Side 30/70 Review Dashboard: Dedicated two-column review view with a markdown terminal session stream, per-card re-run actions (scores vs. narrative), and full diff hunk visibility.
- Automated GitHub PR Comments: Optional settings per repository and globally to automatically post calibrated System One scores, merge gate checks, and review summaries directly on pull requests (gh pr comment).
- Cinematic Product Film & Updated Documentation: Embedded 1080p/60fps product tour in the README and added reproducible Flute scene configurations.
- Dynamic OpenGraph & SEO Metadata: Rich preview cards (og.svg) and per-route metadata for shared review and repository links.
🛠️ Fixes & Improvements
- Various bug fixes, UI refinements, and stability improvements.
CodeOtter v0.1.0 - Initial Release
🦦 CodeOtter v0.1.0 - Initial Release
Autonomous, Self-Hosted AI Code Reviews & Merge Gates
CodeOtter is a dual-engine AI code review and pull request intelligence platform designed for engineering teams who demand deep code intelligence without compromising privacy or paying per-seat SaaS subscriptions.
Highlights
- Dual-Engine Review Architecture:
- System 1 Engine: Evaluates 6 calibrated rubric scores (Architecture, Security, Complexity, Testing, Documentation, Blast Radius) and enforces 8 deterministic pre-merge policy gates.
- System 2 Engine: Generates concise executive summaries, cohort file walkthroughs, and severity-ranked actionable findings.
- 100% Self-Hosted & Air-Gapped:
- Run completely offline on local hardware with GGUF / open weights (via Ollama or local sidecars).
- Flexible BYOK support for Anthropic Claude, OpenAI, OpenRouter, and private OpenAI-compatible endpoints.
- Automatic Team Guidelines Enforcement:
- Automatically detects
AGENTS.mdandCLAUDE.mdat the repository root via GitHub API. - Enforces project rules directly at the merge gate with zero manual setup.
- Automatically detects
- Multi-Organization & RBAC:
- Full organization-level data scoping with instant team switching.
- One-click GitHub App OAuth manifest integration.
- Role-based access control (Owner, Admin, Developer).
- Production-Ready Docker Deployment:
- Single-container or Docker Compose deployment with embedded PocketBase storage and zero dependencies.
- Zero Telemetry:
- Your code never leaves your infrastructure unless you explicitly configure a cloud provider.
Full Documentation: See README.md