Coding tasks

Start a task

1. Choose New coding task, or type /code in the composer.
2. Bind a workspace: a folder on your computer (desktop app) or a GitHub repository.
3. Ask for an analysis first when the scope is unclear, then ask for the change.

What “done” means

• A change counts only when it is real and its checks pass; checks run in layers you can see.
• Unfinished work is marked unfinished, with the reason and the suggested next step.
• UI changes come with before-and-after screenshots.

Keep going

• Say “continue” to resume the same task and workspace.
• Buttons on the result card run the report’s recommended steps one by one.
• Pull requests describe what changed, why, how it was verified and what is still risky.

If you have uncommitted changes

TheOne stops before touching a folder whose tracked files have uncommitted changes, and lists them. Commit them, or set them aside and bring them back afterwards:

git stash
# let TheOne make its change, then
git stash pop