GDSense getting started

GDSense Quick Start for Godot 4

Go from an enabled plugin to a focused first GDScript question with explicit project context and a result you can verify.

Published Updated

All documentation

The short answer

Enable the plugin, save your GDSense API key in the dock’s Settings tab, return to Chat, and keep Chat selected in the mode control. Open a GDScript file, add @openscript to a specific question, then press Enter or choose Send Request. Read the answer, verify it against your project, and use + New Chat when you want a fresh conversation.

Start from a connected dock

  • GDSense is enabled under Project → Project Settings → Plugins.
  • The GDSense dock is visible on the right side of the editor.
  • The Settings tab reports that an API key is loaded.
  • A GDScript file relevant to your question is open in the script editor.

Send a useful first request

  1. 1

    Open Chat

    Choose the Chat tab and leave Chat selected in the mode control.

  2. 2

    Attach the open script

    Insert @openscript from the Commands menu or type it in the prompt so the request includes the active GDScript file.

    @openscript
  3. 3

    Ask one concrete question

    State what the code should do, what happens instead, and the kind of help you want.

  4. 4

    Send the request

    Press Enter or choose Send Request. Use Shift+Enter when you want a new line without sending.

First-request example
@openscript
This CharacterBody2D stops immediately when I release an input key. Explain where that behavior comes from in the attached script and show the smallest change that would add gradual deceleration. Do not change the input actions.

Treat the answer as a proposal to verify

Chat answers can explain code and suggest a change, but your running project remains the source of truth. Read the explanation before copying code, keep the edit focused, and rerun the affected scene.

  • The answer addresses the behavior you described rather than a different problem.
  • Any node paths, method names, and input actions match the project.
  • You understand the proposed change before applying it.
  • The affected scene runs without a new parser or runtime error.

Continue the conversation or start clean

Ask follow-up questions in the same chat when they depend on the current exchange. Choose + New Chat when the next task is unrelated; the completed conversation becomes available through History.

Keep in mind: GDSense does not automatically read every project file. Add only the scripts, selections, scenes, or nodes that the next question needs.

Try this workflow inside Godot

Use GDSense to ask questions, attach the context you choose, and review proposed changes without leaving the editor.