Your board, fixed while you code.
Kratu reads your Azure DevOps, Jira or GitHub Issues board, checks whether the work is still needed, explains the root cause and the blast radius, and opens a pull request for you to review. It uses the AI coding agent you already have.
Free during the preview. Runs on your machine. No Kratu account, no telemetry. How Kratu handles your code
Kratu takes the chores. The decisions stay with you.
Every team has a pile of small, well-understood fixes that nobody has time for. Kratu works through that pile so you can spend your day on the work that needs you.
Every change is a pull request
Kratu never merges. It never commits to protected branches. Each fix arrives as a PR with the analysis, the blast radius and the checks it ran, ready for your normal review.
It asks before anything risky
Low-risk fixes go ahead. Medium and high risk stop and ask, and you can steer the agent with your own guidance before it writes a line.
It shows its reasoning
You see the root cause, the files, the plan and why it rated the risk the way it did. Every run keeps a full transcript you can open later.
From work item to pull request in six steps
Sync your board
Kratu loads the work items you choose (types, states, assignee, sprint, area, tags) and ranks them by priority or by date.
Check it is still needed
Before planning anything, the agent looks at commits that mention the item, linked pull requests and the code itself. If the work is already done, Kratu comments with the evidence and stops.
Analyze, read-only
The agent finds the root cause and the smallest safe change, and Kratu rates the blast radius against your guardrails: blocked paths, sensitive areas, size limits.
Fix in an isolated worktree
The fix happens in a separate git worktree from the latest base branch. Your working copy is never touched.
Quick checks
Lint, type check and related tests run only for the files that changed, within a time budget. If something breaks, the agent gets one chance to repair it.
Pull request and update
A new branch (or one you pick), a linked pull request, a comment on the work item and an optional state change.
Set the limits once. Kratu keeps to them.
Which states Kratu may fix
Pick the states during setup. Done, QA and parked items get no Fix button, and clock-in skips them. Items someone already linked a commit or PR to are left alone.
How much risk is automatic
By default, only low-risk fixes go ahead on their own. Medium and high risk always stop and ask you first. You can also switch automatic fixes off in setup, so every fix waits for your yes.
Guardrails on every diff
Secrets, .env files, keys and pipeline definitions are blocked. Migrations, auth and payment code raise the risk to high. Changes stay under your file and line limits.
Working hours, only if you want them
Kratu works on its own only when you clock in or turn on working hours. Then it checks the board at the interval you set, fixes low-risk items in your allowed states one at a time, and leaves the rest for your approval. How to turn it off
Stop Kratu working on its own
Kratu changes code by itself only when you clock in or turn on background runs. Fixes you start with 🪄 Fix are never affected. Open the Command Palette with Ctrl Shift P (Cmd Shift P on a Mac) to run any of these.
Clock out
- Click Kratu: clocked in in the status bar at the bottom of the editor.
- Choose Clock out.
Or press Stop in the Kratu panel, or run Kratu: Clock Out. Closing the editor also ends a clock-in.
Stop background runs
- Run Kratu: Show Schedule Status to see whether a background job is on.
- Run Kratu: Stop Background Runs to remove it.
Clock out does not stop background runs. They were turned on in setup if you chose “Yes, run in the background”.
Explain-only mode
- Run Kratu: Set Up.
- At Automatic fixes, choose Never — explain only.
Kratu still checks the board and comments its analysis, but every fix waits for your yes.
Analyze-only clock-in
- Run Kratu: Clock In.
- Choose Analyze only.
Kratu works through the queue and explains each item, without editing any code.
The Kratu status-bar menu also has Background runs: show status and Stop background runs (Kratu 0.6.3 and later).
Your editor, your agent, your board
Install Kratu in any VS Code-based editor. It drives the AI coding CLI that is installed and signed in on your machine, under your own account and plan.
Three steps, all inside VS Code
Install Kratu
In VS Code, Antigravity, Windsurf or Cursor, open the Extensions view, search for Kratu and press Install.
Run “Set up Kratu”
Paste a link to your Azure DevOps, Jira or GitHub board, sign in (your token stays in the editor’s secure storage), pick the states and the agent.
Press Fix
Choose an item in the Kratu sidebar and press 🪄. Or tick several and fix them in one go. Each gets its own branch and pull request.
Step-by-step setup guide with screenshots, for Azure DevOps, Jira, GitHub and mixed setups
Where Kratu is heading
Plans can change with your feedback. Tell us what would help your team most.
Azure DevOps, Jira and GitHub
Azure Boards, Jira (Cloud and Data Center) and GitHub Issues, with pull requests on Azure Repos and GitHub.
Every VS Code-based editor
VS Code, Antigravity, Windsurf, Cursor and VSCodium, from the VS Code Marketplace and Open VSX.
GitLab and Bitbucket
Pull requests opened directly on GitLab and Bitbucket, and GitLab issues as a board.
More from Kratu
New ways for Kratu to help your team ship. Follow along on LinkedIn to hear first.
Kratu for teams
Shared team settings, a dashboard of what Kratu fixed, and bulk fixing for larger queues.
Clear the small stuff off your board.
Free while Kratu is in preview. Early users will hear first when team plans arrive.