Claude, working on the codebase you already have.
A desktop workspace that reads your repository — its code, database, backlog and git history — then does the work with you. It implements work items on their own branch and proves they build, reviews pull requests, scores what the code is costing you, and answers questions that cite real files. It detects your stack rather than assuming one.
macOS, Windows & Linux · works with Azure DevOps, Jira, ClickUp and GitHub
.NET · Laravel · Symfony · Django · Rails · NestJS · Next.js · Nuxt · SvelteKit · Express · Go · Rust · Flutter · Swift · Elixir · Maven · Gradle · 31 stacks detected in all
Runs on your machine, against your checkout. Aidle uploads nothing — it drives the Claude CLI you are already signed in to.
How it works
Four beats, one work item.
The same path a senior engineer would take — on its own branch, with the build as the judge, and the knowledge left behind for the next one.
Learn the codebase
Point it at a repo. It detects the stack, maps the architecture and the database, reads the git history, and turns backlog items into knowledge every other screen reads.
→Agree the plan
It traces the item against the real code and proposes a plan you approve — before a single file is written.
→Implement and verify
Each run gets its own git worktree and branch, so nothing touches your working copy. Then it builds, lints and runs the tests — and says plainly when the machine cannot run one of them.
→Review and ship
Three reviewers read the diff from different angles, the findings come back with fixes attached, and the branch is yours to commit or open as a pull request.
→What's in the box
One workspace, the whole loop.
Fourteen screens over one project. Everything reads the same knowledge, so what you teach it once makes every other screen sharper.
Forge
Hand it a story, task or bug. It plans, writes the code on its own branch, then builds, lints and tests the result. Several can run at once, each in its own worktree.
Code quality
One scan over the whole repo: a debt score with a letter grade, what changed since last time, a treemap of where the code really lives, and a dependency graph you can focus on one folder — cycles included.
Pull requests
Reviews diffs on GitHub and Azure DevOps against how your code already does it, with the fix attached. It can run in the background and comment for you.
Knowledge base
Azure DevOps, Jira or ClickUp items in one board. Enrich one and it becomes domain knowledge every other screen reads first — plus gaps, questions, estimates and a task breakdown on demand.
DB console
MySQL and SQL Server: schema tree, stored procedures, an ER diagram, natural-language SQL, editable results, query plans with advice on the index you are missing.
Chat
Ask the codebase anything. Answers cite real files and real schema — grounded in your project, never general knowledge.
Architecture & domain maps
How the system actually fits together, drawn from the code: endpoints, layers, entities and the rules they break.
Team & planner
Capacity against real hours and commits, a delivery score per person with last month beside it, monthly reports exportable to PDF — and your own day planned around the calendar.
Documenter & notes
Documentation written from the code rather than from memory, with diagrams, and notes that export as a real document.
Get started
Download it and start shipping.
Everything is there from the first run — no feature tiers, no per-seat add-ons. Point it at a repo; connect a board when you want it working from your backlog.