Reasoning
Works a problem through, and says where the reasoning stops.
Code, where the code actually is.
In the desktop app you open a folder and it works there: it reads the files, runs the build, reads what came back and fixes what it broke. Not on a copy you pasted into a chat window.
Three steps.
- 1
Open the folder
In the desktop app you point at a folder. Nothing outside it is reachable, in any mode.
- 2
Say what is wrong
“The test in OrderServiceTests fails since the last commit.” It reads the file, then the test, then the diff.
- 3
Confirm the change
Every write is a separate confirmation - or none at all, if you switch that off for a session.
Pages and tools that run.
Ask for a page, a widget or a small tool and it runs right next to the answer. Switch to the code, change it in place and see the result at once.
What it does.
- Reads whole files, not just the names, and follows an import to the file it points at
- Runs
dotnet buildanddotnet test, then reads the compiler output instead of guessing git status,diff,logandblamewithout asking; commit and push only when you say so- Writes into your folders, one confirmation per file - or none, if you switch that off
- Force pushes and hard resets are not available at all, in any mode
- Long files open in a panel beside the conversation instead of scrolling past it
- Web pages and small React apps it writes run as a live preview beside the answer, with a switch to the code, which you can edit in place
- Draws how a request moves through the system as a flow, sequence or use case diagram
Where it stops
It does not run your application, and it does not touch anything outside the folders you opened. A build that needs credentials, a database or a device will fail here in exactly the way it fails on a machine without them.
Asked like this
The test in OrderServiceTests fails since the last commit. Find out why and fix it, but do not change the test.
Which size to use
Medium for everyday work, Large when the change spans several files and the reasoning has to hold across them.
Compare the sizesQuestions.
Does it run my application?
No. It runs the build and the tests, reads what came back and works from that. Starting your application, with its database and its credentials, is not something it does.
Can it break my repository?
Force pushes, hard resets and clean -fd are not available at all - not behind a confirmation, not in any mode. The worst it can do is leave a bad commit you can revert.
Which languages?
Any language for reading and writing. The build and test integration is .NET today; for everything else you get the file, the reasoning and the change, and you run the build yourself.
Other kinds of work.
Office work
Reads what piled up, writes what has to be written.
School and studying
Explanations that stop where the knowledge stops.