gonuAsk, Plan, Build, Debug & Review
Choose how much work a task should do and which actions require your decision.
WHEN IT HELPS
Put it to work.
Separate understanding a problem from changing files, then validate a small change with the project’s real checks.
Before you begin
- An authorized project, an available model and the project’s development dependencies.
- A focused request with expected behavior and constraints.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Ask explains, Plan proposes steps, and Review inspects changes without modifying files. Build implements; Debug investigates a failure. Auto coordinates work but keeps the same permission boundaries.
Read the plan and review each requested file edit or command. For Debug, provide the error, reproduction steps and expected result. Deny actions outside the request.
Inspect actual build/test output and final diffs. A failed check stays failed. Bounded repair may retry, but missing dependencies or unresolved failures require your attention.
Worker / Mode selection
A REQUEST TO START WITH
Debug this expired-session error. Reproduce it, explain the root cause, propose a focused patch and run the relevant existing tests after approval. Report any remaining failures.
THE USEFUL RESULT
What you should leave with.
An explanation, plan, review or validated local change, according to the selected mode and available evidence.
Know the boundaries.
- A completed model response is not proof that a build, test or security review succeeded.
- Auto does not bypass publishing, destructive-action or command approvals. Local completion does not automatically deploy, commit or create a PR.
IF SOMETHING DOESN’T WORK
The task is waiting or a check fails.
Inspect pending approvals and the actual error. Provide a supported build/test command or install the project’s prerequisites yourself before retrying.
Contact support