The short answer
Choose Chat in the GDSense mode control, write a specific Godot or GDScript question, and add context commands only for the code or scene evidence the answer needs. Press Enter or choose Send Request; use Shift+Enter for a new line. Continue in the same conversation for dependent follow-ups, or choose + New Chat when you switch to an unrelated task.
Use Chat for explanation and focused guidance
Chat fits questions where you want an answer to read and evaluate: understanding an API, explaining an error, tracing a focused behavior, planning a small change, or reviewing an approach. It does not edit the whole project automatically.
- Ask one clear question at a time.
- Describe expected behavior and current behavior when debugging.
- Name constraints that a suggestion must preserve.
- Attach project content explicitly when the answer depends on it.
Attach the smallest complete context
- 1
Use the active script
Attach the script currently open in the Godot script editor.
@openscript - 2
Use highlighted lines
Attach the current code selection with its source location.
@selection - 3
Use a specific file
Attach a project file when it is relevant but not currently open.
@file res://scripts/player.gd - 4
Use scene structure
Attach a scene when node paths, types, or attached scripts affect the question.
@scene res://scenes/player.tscn --scripts
Keep in mind: More attachments can introduce unrelated details. Start small and add another file or scene only when the first answer identifies a real gap.
Write an answerable request
A strong request combines evidence, observed behavior, expected behavior, and constraints. Ask for assumptions to be called out when the attached context is not enough.
@openscript
When I run this scene, the character accelerates correctly but never slows down after input is released. Identify the line responsible, explain why it behaves that way, and propose the smallest typed GDScript change. Keep the existing input actions and maximum speed.Continue, retry, or start a new chat deliberately
- 1
Continue for dependent questions
Keep the same chat when the next question depends on the answer or context already in the conversation.
- 2
Retry a failed request
A failed Chat request keeps the original prompt available. Retry resends that prompt with the same mode and attached context.
- 3
Start clean for a new task
Choose + New Chat before an unrelated question so old discussion does not distract from the new goal.
Verify suggestions in Godot
- Check that referenced classes, methods, signals, and node paths exist in the project.
- Read code suggestions before applying them.
- Run the affected scene and reproduce the original steps.
- Keep version-control changes focused and discard edits that do not serve the request.