Ask for One Small Change
Use a prepared request to improve one sentence in the notes file, then look at the result together.
Look around. Try a small click.
This lesson works as a written guide with interactive examples. You can explore here before opening VS Code. A recorded video has not been added yet.
What will make more sense
- Recognize a small change request with a clear file and result.
- Understand how the assistant can update the actual document.
- Know that a prepared browser example is enough to practice the idea.
One idea to keep
Ask for one small change, then look at the actual result.
The short lesson
Read the explanation at your pace
You have seen where the files live, where the document appears, and where the conversation goes. You have also tried giving the assistant a useful starting point. Now we can ask for one small change. We will use an ordinary sentence in the prepared notes file. You do not need to understand website markup or ask the assistant to build something large. A small result is easier to recognize and discuss.
The notes file begins with Today's goal: Find my files. Our change is to make that goal a little more specific: Today's goal: Find my files and ask one clear question. Both sentences are already provided in the lesson. You are not expected to invent a project idea or write a detailed assignment. The activity is simply about seeing how a request relates to the words in a file.
A vague request might say make it better. That leaves the assistant to guess which document, which sentence, and what better means. Our prepared request names notes.md in this course folder and gives the exact replacement sentence. It also asks the assistant to leave everything else alone. This is a useful pattern: point to the item, describe one change, and make the result easy to check.
In the browser example, choose the specific request and read the prepared response. Then look at the document area. The example shows only the intended sentence changing. It does not send a message to a real service or alter a downloaded file. You can explore the idea here before deciding whether you want to try it in the application. The next lesson will make the before-and-after comparison even clearer.
If you use a real connected assistant, open notes.md and send the supplied request. Watch which file it says it changed, then read the actual sentence in the editor. A reply saying done is not the same as checking the document. Depending on the assistant setup, its edit may already be saved when you see a change review. The interface does not always wait for a separate approval before writing a file.
If the result is different from what you asked for, a simple follow-up is enough: Please change only the goal sentence to the supplied wording and leave the other text as it was. You can also stop and stay with the browser example. There is no need to keep making changes just to complete a lesson. The useful habit is connecting one clear request to one visible result.
You have now met the basic idea of working with an agent beside your files. It can help with a real document rather than only describe a possible answer in chat. Your role is to tell it the small outcome you want and look at what happened. That skill matters more at this stage than knowing how the assistant performed the edit behind the scenes.
Try it here
Make one request clear
Compare the vague request with the supplied one-sentence edit. This example does not change your files.
This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.
Which request makes the intended result clear?
A prompt you can keep
These are example words to copy into your own AI chat when you want to try them. Copying does not send a request.
In courses/vs-code-for-beginners/notes.md, replace the goal sentence with: Today's goal: Find my files and ask one clear question. Leave the other text and files unchanged.A tiny next step, if you want one
Optional: try 2 small actions in VS Code
You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.
- Optional: open notes.md in your course folder.
- Optional: copy the supplied request into your connected assistant and read the resulting sentence.
A quick confidence check
These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.
Your place is saved in this browser when storage is available. There is no grading or account sync.
Try a short question
Choose an answer to see why it fits. You can try again or explore every explanation.
Why is the prepared request easy to check?
What should you do after an assistant says it changed the file?
If something looks different
The assistant changes more than the goal sentence.
Ask it to keep only the requested sentence change and preserve the other text. Review the document before continuing.
I do not have a connected assistant yet.
Use the prepared browser activity. You can learn the request-and-result pattern without signing in.
Useful official help
These links open the product’s own guidance. You can keep them for later; you do not need to read every reference now.