Changelog
What shipped, and what it fixes. Where a feature reads your code, we say whether a result is extracted from the code (a fact) or written by an AI model (a draft to check).
Release check: what a change between two refs can reach
Shipped: Pick two refs and see files outside the change that depend on it, routes and services it touches, changed files no test reaches, and files that usually change with it. It reads GitHub's compare data and the repo map, and calls no AI model, so every line is extracted fact.
Fixes: Before this you had to guess the blast radius of a release from the diff alone.
· Early access
Incident context: weekly brief, incident detail and RCA starter
Shipped: Connect a log source and get a weekly brief, an incident detail view and a root-cause starter that lists extracted facts and leaves the conclusion sections blank for you. Briefs can be shared through a read-only, revocable link. Available by invitation.
Fixes: Ties production incidents back to the changes that came shortly before them, without an AI writing the conclusion for you.
Scheduled runs skip when nothing has changed
Shipped: A scheduled run now checks the repo first and skips if there are no new commits, or only the docs folder changed. A skipped run does not use any of your monthly runs.
Fixes: Scheduled runs no longer spend a run on a repo that has not moved.
Missing pages now return a real 404
Shipped: Unknown use cases, projects and brief links now answer 404 instead of a 200 page that says "not found".
Fixes: Search engines were treating those pages as real pages (soft 404s).
Free-trial repos get 5 MCP questions
Shipped: A repo on the free run includes 5 questions through MCP, then asks you to subscribe. Paid repos stay unlimited.
Fixes: Makes the limit of the free run clear up front, on pricing, free-run and MCP setup pages.
Your first run on a repo is free
Shipped: Connect a repo and run Ask Jentic on it once with no card. One free run per connected GitHub account.
Fixes: You can see the result on your own code before you subscribe.
check_change tool for AI assistants (MCP)
Shipped: Give an assistant the files it changed and a one-line intent, and it gets back facts from the repo map: paths not in the map, dependents and co-changing files the change left out, tests to run, and high-risk files touched. The intent match is a labelled keyword heuristic, so the assistant still has to judge the fit.
Fixes: Lets an AI coding assistant check its own change against your repo before you review it.
Scheduled runs are opt-in
Shipped: Scheduled runs are off by default. A checkbox turns them on, every other day by default, and the scheduler skips a subscription that has used its included runs.
Fixes: No run you did not ask for, and no surprise use of your allowance.
Interactive walkthrough and a cleaner repo footprint
Shipped: The product tour lets you jump to any chapter and adds a relationship map and a view of screens, API routes and tables. The generated data-map.json is no longer committed to your repo.
Fixes: Easier to see how the map is built, and fewer generated files in your repository.