How do I ask an AI agent to make a first small project change?
Open the correct local project folder, give an agent a bounded change and clear completion criteria, then inspect its file changes and verification evidence.
Maintained by the 路墨 Lumoswitch product team
Choose the project folder first, then describe one small change. Use Plan mode for multi-step work and inspect the resulting diff and checks.
What should I prepare first?
1. In the workspace picker, choose a folder and open the project root; or reopen a saved folder. 2. Check that the folder name is right, then choose the model and agent for this run. 3. Start with a small change. If the project already has uncommitted work, note which files were changed before the agent starts. The workspace works around the selected local folder; other directories are not automatically part of its context.
What should I put in the first task?
Give the agent a concrete result, scope, and constraint. For example: “Inspect this project's home page and fix the navigation text being clipped on narrow screens. Change only the relevant component and styles; do not add dependencies. First tell me which files you plan to inspect, then implement the fix and run the relevant project checks. If you cannot run a check, explain why.” 1. Use Chat for a small request; choose Plan when work has several steps and needs a plan and independent review. 2. Add observable completion criteria when you need a clearer acceptance target. 3. File edits, commands, and other operations follow the current permission setting; review each requested action when the app asks.
How can I tell whether the work is done?
1. Read the task status, run history, and final report in the workspace. 2. If files changed, open the file-change record and inspect the paths and patch; check that any verification report or test result matches this change. 3. Do not treat the completion message as a deployment. Use the project's own preview or checks to confirm the result. Plan mode also shows planning, execution, and review results; you can keep adjusting instead of completing the task.
What if there is no result or the wrong file changed?
1. Confirm that the workspace is the project root and name the target page or file explicitly. 2. If the model or runtime is unavailable, check the workspace's model and runtime status before retrying. 3. Stop and open the correct folder if the path is wrong; do not keep editing in a guessed directory. 4. Give one concrete correction, such as “Change only the mobile styles in `src/...`; leave the desktop layout alone.” Agent changes can still miss things, so inspect the patch and run project checks for important work.