Begin with the project, not a blank chat.
A coding task has a location. It may be a failing test, a route that behaves differently in production, or a change that touches several files. Aditya Code starts from a selected project so the investigation can refer to actual files and tool results.
As the run progresses, the useful question is not simply whether the agent has an answer. It is whether you can follow how it got there. Which files were inspected? Did a command complete? What did the test actually say? A failed check should remain a failed check, not become a confident sentence about success.
That trail also makes review easier. You can challenge an assumption, inspect a proposed diff, or ask for another check without having to reconstruct the whole journey from the final message.
When evidence is missingIf a check cannot run because a dependency or service is unavailable, the result should stay unverified. A plausible patch is not the same as a tested one.