Request to support KiCad on drives other than C:

Overview Files Skills Discover Packages Releases Dependencies Issues22 Breadcrumbs Pull Requests Activity

Closed general

Glenn Jones · 12d ago ·closed by Colby Knox

Filed from Hydrogen Desktop 1.0.666 on THREADSIPPER (Adom menu).

As the title says I have my iKit on Drive D and your system doesn't currently seem to support it. Also found it kind of odd that the bridge only supports KiCad under Windows yet I had to install KiCad under Linux in order for some tests to be run on my Fusion version of the project I'm building.

Device: System manufacturer System Product Name (AMD64, 31.9 GB RAM, AMD Ryzen 7 1700X Eight-Core Processor). Microsoft Windows 11 Home 24H2 build 26100. WSL: WSL version: 2.6.1.0.

Attachments: hydrogen-desktop-tail.log (last 300 KB of the app log), diagnostics.json (health, setup state, WSL status, the Doctor checks, build info, device), setup-steps-wsl.json (setup step log), setup-timing-wsl.json (setup step log).

Last 40 log lines:

15:31:41.901 [heartbeat] alive 158250s
15:31:51.073 [control] workspace exec (8s): curl -s -o /dev/null -w '%{http_code}' -m 3 http://127.0.0.1:27011/
15:31:51.902 [heartbeat] alive 158260s
15:32:01.903 [heartbeat] alive 158270s
15:32:11.904 [heartbeat] alive 158280s
15:32:12.135 [focus] hd Focused(true)
15:32:21.905 [heartbeat] alive 158290s
15:32:31.906 [heartbeat] alive 158300s
15:32:41.085 [ai-threads] hook event #374: UserPromptSubmit (claude)
15:32:41.907 [heartbeat] alive 158310s
15:32:51.078 [control] workspace exec (8s): curl -s -o /dev/null -w '%{http_code}' -m 3 http://127.0.0.1:27011/
15:32:51.119 [control] workspace exec (8s): export PATH=$HOME/.local/bin:$PATH; f=$(command -v 'hydrogen-widget-claude-usage') && r=$(
15:32:51.908 [heartbeat] alive 158320s
15:33:01.909 [heartbeat] alive 158330s
15:33:11.910 [heartbeat] alive 158340s
15:33:21.911 [heartbeat] alive 158350s
15:33:31.912 [heartbeat] alive 158360s
15:33:36.326 [focus] hd Focused(false)
15:33:41.913 [heartbeat] alive 158370s
15:33:51.072 [control] workspace exec (8s): curl -s -o /dev/null -w '%{http_code}' -m 3 http://127.0.0.1:27011/
15:33:51.914 [heartbeat] alive 158380s
15:33:54.954 [runtime-kv] published hydrogen.runtime.threadsipper (control=47084, instance=hd-4492-18e286fe9555cee8)
15:34:01.915 [heartbeat] alive 158390s
15:34:11.916 [heartbeat] alive 158400s
15:34:21.917 [heartbeat] alive 158410s
15:34:30.907 Update check: on latest (1.0.666 == 1.0.666)
15:34:31.190 [updater] fleet ping HTTP 200 (user 'Glenn')
15:34:31.918 [heartbeat] alive 158420s
15:34:33.429 [ai-threads] hook event #375: Stop (claude)
15:34:41.919 [heartbeat] alive 158430s
15:34:51.079 [control] workspace exec (8s): curl -s -o /dev/null -w '%{http_code}' -m 3 http://127.0.0.1:27011/
15:34:51.150 [control] workspace exec (8s): export PATH=$HOME/.local/bin:$PATH; f=$(command -v 'hydrogen-widget-claude-usage') && r=$(
15:34:51.920 [heartbeat] alive 158440s
15:35:01.921 [heartbeat] alive 158450s
15:35:03.845 [agents] skills: [claude] (default) nothing to do
15:35:05.764 [focus] hd Focused(true)
15:35:11.922 [heartbeat] alive 158460s
15:35:21.923 [heartbeat] alive 158470s
15:35:31.924 [heartbeat] alive 158480s
15:35:41.925 [heartbeat] alive 158490s

3 Replies

Colby Knox · 11d ago

Thanks, Glenn. Today the KiCad bridge only looks for KiCad on C:, and some of its library paths assume C: too. The fix to find it on any drive is tracked here: https://wiki.adom.inc/adom/kicad-bridge/issues/137.

You shouldn't need KiCad installed inside the Linux workspace either. The AI should run those checks through the bridge or our hosted KiCad service, and we're tightening that up as part of the same work.

Glenn Jones · 11d ago

I guess because I didn't have KiCad installed under Windows on the particular system I was using with Hydrogen, it suggested an alternative where it could install KiCad under Linux and do some of the KiCad work that has to be done (even when you're using Fusion). At least that's what it told me. I let it install KiCad under Linux and then later on, when I wanted to actually do a KiCad version of the same project, I was told "Hey you need KiCad under Windows. Said, "Wait a minute. You told me you needed to install it under Linux. Why can't you just use the version under Linux?" And it said, "Well the bridge is only supported under Windows." That's fine for me right now because I primarily use Windows anyway.

Colby Knox · 11d ago

Thanks, Glenn, that explains it. The AI took a wrong turn there. When KiCad isn't on your Windows PC, it should offer to install it there for you. The bridge can do that itself: the official KiCad installer, per user, no admin rights and no UAC prompt. Installing KiCad inside the Linux workspace doesn't help, because the bridge always drives the KiCad on your Windows machine, including for headless checks like DRC and ERC. We've added that rule to the instructions the AI reads, so it shouldn't suggest the Linux install again.

KiCad on drive D: is fixed in kicad-bridge 1.0.95, which is public now. The bridge looks on every fixed drive and in KiCad's uninstall records, not only C:, and Adom Bridge's own "is KiCad installed" check covers other drives too. Hydrogen picks the update up automatically. Once it has, ask the AI to "check KiCad readiness" and it will show which KiCad it found and where. Details: https://wiki.adom.inc/adom/kicad-bridge/issues/137

Closing this. If KiCad on D: still isn't found after the update, reopen it and paste what "check KiCad readiness" says.

Colby Knox closed this · 11d ago