Godot development tools for Visual Studio Code with local-first GDScript intelligence, incremental project indexing, documentation, debugging, and Godot Language Server integration.
Independent project: Neo Godot Tools is a substantially modified derivative of the original Godot Tools VS Code extension. It is not an official Godot Engine project and is not affiliated with or endorsed by the Godot Foundation. See Provenance and Notices for details.
Features
- GDScript (
.gd) language features
- syntax highlighting
- project-symbol definition lookup
- Godot native class and member documentation lookup
res:// resource links and hover previews
- builtin code formatter
- autocompletion
- local semantic analysis for project symbols
- incremental indexing for responsive project-wide language features
- typed GDScript support
- optional Smart Mode for dynamically typed scripts
- function and variable hover information, including doc-comments
- scene/script switching (
Alt+O by default)
- script warnings and errors
- GDScript Debugger
- breakpoints, exceptions, and stepping
- variable watch and call stack
- current project/current file/pinned file launch targets
- active scene tree and inspector
- editable primitive values in the inspector
- GDResource (
.tscn, .tres, and related resources)
- syntax highlighting
- symbol and resource definition lookup
- hover previews for external and sub-resources
- inlay hints
- in-editor Scene Preview
- Resource Inspector: a Godot-style property editor for
.tres files
- Static 2D Scene Preview for
.tscn files
- GDShader (
.gdshader) syntax highlighting
- Shader Preview for uniform metadata
Compatibility
| Component |
Compatibility target / automated coverage |
| Godot 3 |
3.6.2 is a documented compatibility target; engine-in-the-loop checks are opt-in |
| Godot 4 |
4.5.1 and 4.7 are documented compatibility targets; engine-in-the-loop checks are opt-in |
| Visual Studio Code |
^1.96.0 |
| Standard GitHub Actions CI |
Ubuntu (ubuntu-latest), plus a Windows (windows-latest) Zig backend job |
The standard CI workflow checks TypeScript compilation, unit and release tooling, coding standards, formatter snapshots, and VSIX packaging. It also builds the Zig 0.17.0 analysis sidecar for Windows and Linux x64, runs its unit tests, and requires the lexer differential suite to run against the native binary. The checked-in CI and release workflows do not automatically invoke the Godot engine-in-the-loop runner (npm run test:engine), so the Godot versions above should not be interpreted as an automatically exercised engine-version matrix.
Godot 3 releases older than 3.6 remain outside the project's documented compatibility target. Other Godot 4 releases may work, but are not individually covered by an automated engine-in-the-loop matrix.
Installation
Visual Studio Marketplace
The Marketplace is the recommended installation channel because it provides normal extension update handling.
GitHub Releases
Stable VSIX packages are also attached to GitHub Releases. This is useful when installing a specific version or testing a package outside the Marketplace.
Development builds
Development builds are produced by GitHub Actions. They are intended for development and validation rather than normal production use.
To install a VSIX manually, use VS Code's Extensions → ... → Install from VSIX... command.
Release channels
Neo Godot Tools deliberately separates its release channels:
- GitHub Release — the canonical repository release artifact. Stable tags use
vX.Y.Z; development tags use vX.Y.Z.devN and are published as GitHub pre-releases.
- Visual Studio Marketplace — stable releases only. Marketplace publication is performed by a dedicated GitHub Actions workflow using VS Code Marketplace OIDC trusted publishing; it does not use a long-lived Azure DevOps PAT.
GitHub Releases and Marketplace publication are therefore independently automated and can be diagnosed independently.
Commands
Commands are grouped under Neo Godot Tools in the VS Code Command Palette.
- Open workspace with Godot editor
- Open EditorSettings
- Start or stop the GDScript Language Server
- List Godot native classes
- Inspect and refresh debugger views
- Debug the current or pinned scene/script
- Pin and unpin scene files
- Open Scene Preview and related resources
- Switch between a scene and its script
- Copy resource paths
Configuration
Godot editor integration
To use VS Code as the external script editor in Godot:
- Open Editor Settings.
- Select Text Editor → External.
- Enable Use External Editor.
- Set the VS Code executable as Exec Path.
- Use
{project} --goto {file}:{line}:{col} as Exec Flags.
On Windows, point Exec Path at Code.exe (or VSCodium.exe); the
code.cmd wrapper cannot receive Godot's arguments. On macOS, use the
GUI executable inside the bundle
(Visual Studio Code.app/Contents/MacOS/Electron); on Linux, use the
code binary rather than a desktop launcher or a wrapper script.
Godot refuses to start a second instance for the same project when the editor
is already open, so close it before launching the project from VS Code again.
For automatic reloads, also review Godot's external-change and focus-loss settings.
VS Code settings
Extension settings use the neoGodotTools.* namespace:
neoGodotTools.editorPath.godot3
neoGodotTools.editorPath.godot4
neoGodotTools.editor.verbose
neoGodotTools.editor.detached
neoGodotTools.editor.revealTerminal
neoGodotTools.lsp.serverHost
neoGodotTools.lsp.serverPort
neoGodotTools.lsp.headless
neoGodotTools.lsp.autoReconnect.*
neoGodotTools.documentation.*
neoGodotTools.formatter.*
neoGodotTools.scenePreview.*
neoGodotTools.inlayHints.*
neoGodotTools.resource.inspector.diagnostics
When the selected Godot version supports headless LSP operation, Neo Godot Tools can launch a windowless Godot process for the language server.
Resource Inspector
.tres files open in the text editor by default. Neo Godot Tools: Open Resource Inspector (or Open With... -> Resource Inspector) opens a dedicated Godot-like property editor: every property of the [resource] section and of each [sub_resource] gets a widget that fits its value, and edits are written back into the text file, so the file stays the source of truth.
.tres files use a dedicated Resource Inspector editor tab through Open With....
.tscn files open in the static 2D preview by default. The preview shows node hierarchy, basic transforms, Control sizes, text, colors, and safe local textures, with source navigation from selected nodes. Choose Open With... -> Text Editor to edit the scene as text.
.gdshader, .shader, and .gdshaderinc files open in the shader metadata preview by default. Canvas item uniforms are listed with their types and defaults; spatial and other shader types are identified as metadata-only because browser execution is unavailable. Choose Open With... -> Text Editor to edit shader source as text.
neoGodotTools.resource.inspector.diagnostics reports resource problems (dangling ExtResource/SubResource ids, unparsable values, type mismatches against the attached script) in the Problems view. It is off by default: without the Godot language server's complete property list the inspector cannot tell a real mistake from a property it does not know about, and Godot's own inspector does not flag resources either.
The inspector understands both Godot 3 and Godot 4 text-resource syntax, including PoolColorArray, Transform, StringName("…") and ExtResource( 1 ).
- Resource properties use a single selector with Browse/Open actions, and controls adapt to a narrow sidebar without overlapping.
- Range properties provide synchronized sliders and number fields with bounds, step sizes and Godot's
or_greater/or_less flags. Bit flags can be combined with checkboxes.
- Image references and image-path strings show thumbnails. Hover or focus the path/thumbnail for a larger preview and dimensions; click the thumbnail to open the image. Inline previews stay inside the project/workspace and show an explanation for missing or unsupported formats.
- Modified compares known script or built-in defaults, including when native LSP metadata is available. If the actual default cannot be determined, Revert removes the explicit override rather than guessing a type's zero value.
- New external-resource IDs continue after the largest numeric prefix in the file. Existing IDs are preserved, including Godot 3's numeric reference syntax.
Architecture
Neo Godot Tools is no longer a thin wrapper around the upstream Godot Tools architecture. The current implementation is organized around a local-first language intelligence pipeline:
VS Code extension
│
├── Local GDScript semantic analysis
│ └── Incremental project index
│ └── Zig 0.17.0 native symbol mirror
│
├── Godot resource / scene / shader tooling
│
├── Debugger and editor integration
│
└── Godot LSP
└── advanced semantic fallback / engine integration
Run Neo Godot Tools: Show Architecture and Native Backend from the command
palette to see the same technology map and the live sidecar counters in the
editor. The map stays visible when the native binary is unavailable.
| Area |
Implementation |
Main sources |
| Extension host and providers |
TypeScript, Node.js, VS Code API |
src/extension.ts, src/providers/ |
| GDScript analysis and project index |
TypeScript |
src/analyzer/, src/index/, src/language/ |
| Native analysis sidecar |
Zig 0.17.0, JSON-RPC 2.0 over stdio |
backend/src/ |
| Native symbol mirror |
TypeScript adapter, Zig symbol store |
src/backend/zig_backend.ts, src/index/zig_symbol_mirror.ts |
| Editors, previews and inspectors |
TypeScript host, HTML/CSS/vanilla JavaScript webviews |
src/dashboard/, src/resource_inspector/, src/scene_tools/ |
| Godot language server integration |
TypeScript, TCP/JSON-RPC |
src/lsp/ |
| Godot debugger |
TypeScript, Debug Adapter Protocol |
src/debugger/ |
| Syntax highlighting |
TextMate JSON grammars |
syntaxes/ |
| Build, tests and CI |
Node.js, TypeScript, Zig build, GitHub Actions YAML |
package.json, backend/build.zig, .github/workflows/ |
Detailed design and development documents are available in docs/:
Support
See SUPPORT.md for the supported-version matrix, troubleshooting guidance, and issue-reporting requirements.
Issues and contributions
Neo Godot Tools is an open-source community project derived from the Godot VS Code tooling ecosystem. Bug reports, feature requests, documentation fixes, and focused pull requests are welcome.
Before opening an issue, check the FAQ, SUPPORT.md, and changelog.
For development workflow details, see CONTRIBUTING.md.
License and provenance
Neo Godot Tools is distributed under the MIT License. The project preserves the upstream Godot Tools copyright and license terms while adding copyright to original Neo Godot Tools modifications and contributions.
FAQ
Why does it fail to connect to the language server?
- Verify that the installed Godot version is supported by the project; Godot 3.6.2 and current CI-covered Godot 4 versions are the release-validation targets.
- Open the project in the Godot editor before opening it in VS Code.
- If the editor was started after VS Code, retry the language-server connection.
- Verify that the LSP host and port match between Godot and VS Code.
Why isn't IntelliSense displaying script members?
GDScript is gradually typed, so some dynamic code cannot be resolved statically. Neo Godot Tools resolves many project-level symbols locally, while ambiguous or engine-dependent cases can still fall back to Godot's Language Server. Static typing generally improves result quality.
Can Godot reload external script changes automatically?
Review these Godot Editor Settings:
- Text Editor → Behavior → Files → Auto Reload Scripts on External Change
- Interface → Editor → Save on Focus Loss
- Interface → Editor → Import Resources When Unfocused
Why isn't drag and shift-drop working on Linux?
This can occur when VS Code is running under Wayland. If necessary, add --ozone-platform=x11 to the VS Code launch flags so it runs through XWayland.