v0.61.0

Your agent sets Repowise up, and decisions that govern

On repowise.dev your coding agent sets Repowise up from one prompt, pinned decisions hold for agents and the PR bot until a person lifts them, and results refresh sooner after a push; the 0.61 engine gives agents a lighter tool list and every edit site of a symbol in one call.

This cycle was about getting you to a useful answer with less work on your side. On repowise.dev your coding agent sets Repowise up from one prompt, the decisions your team pins hold until a person lifts them, and results land sooner after a push. repowise.dev runs the 0.61 engine across the API, the indexer and the PR bot, so most of the open-source work below reaches your hosted repositories too, starting with agent calls that return more of what an agent acts on.

Let your agent set Repowise up

On repowise.dev.

The agent setup card on the dashboard copies one prompt for your coding agent. The agent installs the CLI if it needs to, signs in (a device code works with no browser), connects the MCP server to your client, turns on the PR bot and coverage, and hands you only the approvals that need a person.

While it works, the dashboard shows "agent connected, waiting for its first call" with a ready prompt, then the first call as it lands, and Finish setup lists whatever is left. Setup status is available over the API and as an MCP tool, and setup emails hand the job to your agent in one prompt. The install buttons register the server as repowise-hosted, and with the 0.61 CLI, repowise agents add --hosted connects every client on your machine in one command.

Fresh results sooner after a push

On repowise.dev.

An update on repowise.dev used to redo work the last run had already done. With the 0.61 engine it picks up where the last run left off:

  • Updates patch the graph in place. Before 0.61, almost every update on repowise.dev rebuilt the whole graph.
  • Each update reuses the caches from the run before it.
  • The security scan rescans only the files that changed: on 9,000-file repositories it takes under 0.3 s, where a full scan took 27 to 57 s.
  • Your repository's pages build straight from the stored index on an update: on a 690-file repository that step takes 1.3 s instead of 55.8 s.

On one repository a whole update went from 687 s to 370 s. On another, the one-time rebuild after the upgrade took 396 s, and the next two updates took 320 s and 168 s.

Decisions a pull request states

On repowise.dev.

When a pull request's description states a decision, the PR bot puts it in force when the pull request merges. A reply that replaces a decision the review cited supersedes it, and /repowise forget on the bot's acknowledgement restores the old one or says why it could not.

AI included with Pro

On repowise.dev.

AI answers and AI review are on by default for Pro, with a monthly credit meter. When credit runs out, answers keep coming from the index, and the notice tells you when free answers reset.

A PR bot that starts on install

On repowise.dev.

Installing the bot reviews your newest open pull request right away, free, and paid repositories get AI review by default. Check runs post once per push, and blast radius lists only callers that still name the symbol at the pull request's head. On a private pull request, the check lists every finding, so your whole team reads the full review right on GitHub.

Agents carry less and get more from each call

On repowise.dev and in the open-source release.

  • get_context(include=["references"]) returns a symbol's whole edit set as line numbers, the definition first and then every use by file. On 25 symbols, recall went from 20.0% to 90.9% and precision from 89.6% to 98.4%, in two thirds of the bytes.
  • get_symbol adds a one-line fact row (callers, how many of them are tests, fields it assigns, complexity) and the tests that run the function.
  • search_codebase reads a|b|c as written and returns each name with its own share of lines.
  • A flow question to get_answer returns the call path, up to 12 hops as caller file:line -> callee file:line.
  • get_health and get_dead_code replies are smaller: get_dead_code is a median 1.4 KB, down from 2.2 KB.
  • Server instructions name only the tools your client is served.

A lighter tool list for every client

Open-source release.

Each client gets a tool list sized to how it loads tools. Cursor, Codex, VS Code and other clients that send every schema on every request get the five core tools in 1,836 tokens instead of 4,131, and the fixed Repowise text Claude Code carries on every turn drops from about 1,870 tokens to 657. A repeated get_answer returns in 0.09 s instead of about 4 s.

Decisions that govern

On repowise.dev and in the open-source release.

The Decisions page reads in four sections. In force comes first, with pinned decisions at the top. Recent holds what came into force in the last week. Background holds decisions mined from history: get_why serves them when asked, and they are never pushed at you as a to-do. History keeps the rest.

A person can pin a decision in force, and agents and the PR bot respect the pin. An agent's change to a pinned decision becomes a proposal, and only a person can unpin it. Reaffirming a decision takes write access. get_why leads with the decisions in force and marks the pinned ones.

On repowise.dev each record has a "Check with your agent" prompt, and your agent acts on it through the MCP decision tool. A decision an agent records with an evidence commit comes into force once that commit reaches the default branch, by merge, squash or rebase.

Health findings worth acting on

On repowise.dev and in the open-source release.

Health is calibrated against a blind review of 705 findings on 64 repositories. A marker that holds up in one language and rarely in another is advisory in that language: it is listed and costs no points. Runs of guards count once, literal tables and SwiftUI, Compose and Flutter view trees count as data, and idiomatic error handling in Python, Go and Rust is not flagged. Each repository on repowise.dev picks up the new scores on its next index.

Faster updates at monorepo scale

Open-source release.

The graph patch covers documentation edits, added and removed files, config edits that leave the build unchanged, and C and C++ edits. On a 62,000-file C++ repository an update takes 52 s where a full graph rebuild took 303 s, health takes 435 s instead of 1,781 s, and the first index peaks at 11.8 GiB of memory instead of 39.9 GiB.

Every setting in one place

Open-source release.

All 207 settings repowise reads live in one registry. repowise config list shows each value and where it came from, explain describes one, and set validates the value and prints the undo command. Settings > All settings shows the same in the local web UI, settings suggest a better value when your repository clearly needs one, and repowise doctor fails a row for any value repowise cannot use.

Review leads with the verdict

Open-source release.

The local Review page puts the change's review priority and its top drivers under the verdict, then an ordered list of what to check. It opens a merge or pull request by number, and the whole review is available as Markdown for your agent.

Also in this release

  • On repowise.dev, Review lists pull requests under their own tab.
  • On repowise.dev, one account-wide MCP endpoint connects every repository you can see, and public repositories connect with repo-scoped sign-in.
  • On repowise.dev, a repository that goes private on GitHub leaves the public pages, and every page for it shows that it is private.
  • On repowise.dev, test fixture secrets are labelled as fixtures, not live leaks.
  • On repowise.dev, a failed index retries large repositories on a bigger machine.
  • GitLab merge requests get the gate summary as one note, edited in place on later pipelines.
  • Workspace contracts read Temporal task queues, Redis streams, Redis pub/sub and Dapr topics, and Django REST framework and aiohttp routes.
  • repowise doctor reports index freshness, a stuck update lock and a missing vector store.

Upgrading

pip install --upgrade repowise

You don't need to re-index. The first repowise update re-scores health and refreshes the parse cache in one run, on its own. MCP clients other than Claude Code get the core tool list by default, and repowise config set mcp.tools standard restores the wider set. On repowise.dev, each repository picks up the 0.61 engine on its next index.

Thank you

This release includes work from 50 contributors outside the core team.

Run this release on your repo.

Index a repository free and see what this release finds in it. Or explore a live repo first.