08.09.2026, 19:58
Hi,
First thanks for the effort. This plugin is really a needed one to use AI integration for code assist. I think your work will be very useful in the future. Unfortunately this extension doesn't work in my system right now, so here is what I found.
SDlink for SpaceLynk / LogicMachine — bug report
Extension: sdlink.sdlink-vsc-sl, version 0.1.9
VS Code: 1.134.0, Windows (win32)
LM5 controller: reached over HTTPS, authenticated via the extension's own device profile (URL + username; password in VS Code SecretStorage)
Observed: 2026-09-08
Three problems found in one session spent setting up the extension and using it to deploy a single library update. Each is reported as observed, with the evidence that supports it.
1) Pushing a "user" library does not reach the device, with no error shown
Pushing a modified library (a .lua file whose metadata entry has "type": "user") through the sync dialog reports success ("Sync complete — 1 pushed"), and the Script Errors view stays at 0. The controller still holds the previous content.
Verified independently: a LogicMachine backup taken immediately before and immediately after the push showed byte-for-byte identical content (same size, same SHA-256). The push notification was the only signal claiming success; the controller's own backup, and later a full reload of the LM web editor, both still showed the old version.
Reproduced twice: once in the original workspace folder, once in a brand-new workspace folder created solely to rule out anything folder-specific. Same result both times.
Working hypothesis, not verified against the source: libraries carry "id": "undefined" in .sdlink-metadata.json rather than a numeric id like scripts do. They may be routed to a push path that doesn't work, or that silently no-ops.
Workaround used: pasted the library content by hand into the LM web editor, then confirmed with a full sync in the device-to-local direction, which does work reliably.
2) Local files move between folders on their own, with no user input
Files whose metadata says "category": "User library" get placed under a folder named System one moment and User library the next, with no sync command run, no click, no keystroke, the editor simply left open and idle. Watched happening in real time over a few minutes, including mid-command: a git add on a set of file paths failed partway through because one of the files had already moved to a different folder in the seconds between being listed and being staged.
Confirmed not caused on our side: it happened in a brand-new workspace folder synced for the first time, before any push or edit in it. The controller's own content was unaffected across this churn, confirmed by two LM backups minutes apart, byte-for-byte identical for the affected files. A single file's category field was seen to flip between "System" and "User library" across two consecutive reads, with no action in between.
Impact: this makes the local mirror unusable for version control as-is, since a git status taken minutes apart shows a different, unforced diff each time, on files nobody touched.
3) No usable debug output could be found
Output: Show Output Channels, filtered on sdlink, space, and logic, returned no SDlink channel in the standard Output panel.
The extension's own sidebar (Script Logs, Script Errors, Formatted Logs) stayed empty even right after the silent failure described in point 1.
A notification referenced "Skipped ..." lines and pointed at an "SDlink Debug" output channel for detail, but that channel could not be located anywhere, by name or by content search.
Consequence: when something fails silently, nothing lets a user see why, beyond a toast notification whose wording does not distinguish "pushed and applied" from "pushed and discarded".
Suggested priority: point 1 has the real operational consequence, since a false success is worse than a visible error. Point 3 compounds it, since no diagnostic path was available. Point 2 is disruptive but self-evident, and caused no change on the controller in our case.
Thanks for the job!
First thanks for the effort. This plugin is really a needed one to use AI integration for code assist. I think your work will be very useful in the future. Unfortunately this extension doesn't work in my system right now, so here is what I found.
SDlink for SpaceLynk / LogicMachine — bug report
Extension: sdlink.sdlink-vsc-sl, version 0.1.9
VS Code: 1.134.0, Windows (win32)
LM5 controller: reached over HTTPS, authenticated via the extension's own device profile (URL + username; password in VS Code SecretStorage)
Observed: 2026-09-08
Three problems found in one session spent setting up the extension and using it to deploy a single library update. Each is reported as observed, with the evidence that supports it.
1) Pushing a "user" library does not reach the device, with no error shown
Pushing a modified library (a .lua file whose metadata entry has "type": "user") through the sync dialog reports success ("Sync complete — 1 pushed"), and the Script Errors view stays at 0. The controller still holds the previous content.
Verified independently: a LogicMachine backup taken immediately before and immediately after the push showed byte-for-byte identical content (same size, same SHA-256). The push notification was the only signal claiming success; the controller's own backup, and later a full reload of the LM web editor, both still showed the old version.
Reproduced twice: once in the original workspace folder, once in a brand-new workspace folder created solely to rule out anything folder-specific. Same result both times.
Working hypothesis, not verified against the source: libraries carry "id": "undefined" in .sdlink-metadata.json rather than a numeric id like scripts do. They may be routed to a push path that doesn't work, or that silently no-ops.
Workaround used: pasted the library content by hand into the LM web editor, then confirmed with a full sync in the device-to-local direction, which does work reliably.
2) Local files move between folders on their own, with no user input
Files whose metadata says "category": "User library" get placed under a folder named System one moment and User library the next, with no sync command run, no click, no keystroke, the editor simply left open and idle. Watched happening in real time over a few minutes, including mid-command: a git add on a set of file paths failed partway through because one of the files had already moved to a different folder in the seconds between being listed and being staged.
Confirmed not caused on our side: it happened in a brand-new workspace folder synced for the first time, before any push or edit in it. The controller's own content was unaffected across this churn, confirmed by two LM backups minutes apart, byte-for-byte identical for the affected files. A single file's category field was seen to flip between "System" and "User library" across two consecutive reads, with no action in between.
Impact: this makes the local mirror unusable for version control as-is, since a git status taken minutes apart shows a different, unforced diff each time, on files nobody touched.
3) No usable debug output could be found
Output: Show Output Channels, filtered on sdlink, space, and logic, returned no SDlink channel in the standard Output panel.
The extension's own sidebar (Script Logs, Script Errors, Formatted Logs) stayed empty even right after the silent failure described in point 1.
A notification referenced "Skipped ..." lines and pointed at an "SDlink Debug" output channel for detail, but that channel could not be located anywhere, by name or by content search.
Consequence: when something fails silently, nothing lets a user see why, beyond a toast notification whose wording does not distinguish "pushed and applied" from "pushed and discarded".
Suggested priority: point 1 has the real operational consequence, since a false success is worse than a visible error. Point 3 compounds it, since no diagnostic path was available. Point 2 is disruptive but self-evident, and caused no change on the controller in our case.
Thanks for the job!