You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am still not sure if there's a pattern to this issue, but sometimes, variables will not show at all. This seems to happen on first debugging session after launching Godot and Zed most of the time, and seems to be resolved in subsequent sessions.
Just so you know, we do almost nothing in this extension, and we have limited control over what happens. We just connect with a few lines of code, and then Zed and Godot communicate through the debugger adapter protocol.
I'll leave this up in case someone has an idea for things we could do, for example, to verify that the connection was successful and that the two processes are communicating successfully. We looked before at automatically restarting the language server or things like these, like what was done in the VS Code extension, but found that we did not have a hook for that. For the debugger, maybe we can hack it because we do have an entry point for launching debug commands.
Just so you know, we do almost nothing in this extension, and we have limited control over what happens. We just connect with a few lines of code, and then Zed and Godot communicate through the debugger adapter protocol.
I take it this is a Godot issue, then?
When variables don't show, do other debugger functions work? Like console output, breakpoints, stepping through code, etc.
I do not know, I would need to take time to investigate and read the streams of data exchanged between Godot and Zed. I have quite a lot on my plate, so I'll leave that for someone else to do if they would like to (at least for the time being/while I have higher priority tasks I need to attend to).
Activity
NathanLovato commentedon Sep 11, 2026
Just so you know, we do almost nothing in this extension, and we have limited control over what happens. We just connect with a few lines of code, and then Zed and Godot communicate through the debugger adapter protocol.
I'll leave this up in case someone has an idea for things we could do, for example, to verify that the connection was successful and that the two processes are communicating successfully. We looked before at automatically restarting the language server or things like these, like what was done in the VS Code extension, but found that we did not have a hook for that. For the debugger, maybe we can hack it because we do have an entry point for launching debug commands.
fstxz commentedon Sep 12, 2026
When variables don't show, do other debugger functions work? Like console output, breakpoints, stepping through code, etc.
atirutw commentedon Sep 12, 2026
I take it this is a Godot issue, then?
Everything else works fine, yeah.
NathanLovato commentedon Sep 12, 2026
I do not know, I would need to take time to investigate and read the streams of data exchanged between Godot and Zed. I have quite a lot on my plate, so I'll leave that for someone else to do if they would like to (at least for the time being/while I have higher priority tasks I need to attend to).