← General
0

General

Part request feature difficult to access

First of all the part request feature is incredible, keep up the great work there.

I might be using it wrong, but it seems difficult to get to the request feature depending on the part number. When I try searching for a part that isn't in the system, it will often say no results found, or pull up other similar but different parts and not give the option to initiate a request. Sometimes It will give me the option, but I guess when the system doesn't recognize what I'm asking for then it doesn't default to letting me try a request.

7 replies

Ray@ray

Hi Skyler!

Glad to hear you like it. This was my little pet project that turned into a major production service.

Can you give some example part numbers and show screenshots/ say what the confusing messages are?

We want to keep improving it, one whack a mole at a time :)

-Ray

Colby Knox@kcknox

Thanks for the feedback! The original thought was to get as many people searching for components as possible to get them using us for their part sourcing. If it wasn't found in a search then they could request it.

I can look at making the UI better, but in the meantime I would recommend having your AI use our Wiki CLI to request parts. You can use it too, but the AI is so quick at doing it. It works the same as doing it on the wiki itself.

Skyler@skyler.rosenberg

Hi Ray,

It's a wonderful pet project :) I bet it would be useful for applications outside of Hydrogen as well. Certainly, for example "Wago 250-202". Doesn't seem like I can send screenshots on here, what do you suggest?

Absolutely, an endless amount of moles I imagine with such a big and powerful product :).

Colby,

Any time! Thank you very much for your work on this software! I would not be attempting to design a PCB without Ai tools that's for sure. Right, that makes sense to me as well, it just doesn't seem to be working quite as intended yet. You certainly don't want people making requests for parts that already exist I get that.

Oh cool, I'll give that a try thanks. For some reason my Claude feels sort of resistant to use/find the Hydrogen resources/flows on it's own but that's probably because this is all new.

On a side note, It would be a great feature IMO to pull live country of origin info for components from mouser like the price data. Lastly, I'm guessing this is a VS code extension thing but does spell check not work in the claude extension for you either?

Colby Knox@kcknox

Awesome that makes me happy to hear!

You actually can post images in these comments. But you'll need to switch to the preview view rather than raw to actually see how it will look in your comment.image.png

Interesting to hear you say that about your Claude. Are you using Hydrogen? It should have no issue as long as you're in there, but if it is please open issues/bug reports so I can look into that because that is concerning.

I will look into country of origin being shown. I would say a shortcut for now is if you click the little magnifying glass next to part number it'll open its page on Mouser, Digikey or LCSC and you can see a lot more of information there.
image.png

Lastly spell check does work in the Claude Code chat box for me. I'm running it inside Hydrogen, where VS Code runs in a browser engine that provides the spell check. Are you using the regular VS Code desktop app? I believe that one turns spell check off for its whole window, extensions included. If that's it, opening Claude through Hydrogen gets you spell check today. Anthropic is also building their own spell checker into the extension (it's in the code but not switched on yet), and that should work everywhere once it ships. Hope this helps!

Skyler@skyler.rosenberg

Ah I see. I didn't realize you could copy and paste. I was looking for a file upload button or something.

Yeah it's weird. Yes I am using Hydrogen on windows. Ok will do. I think it's when it runs into some issue and then falls back to internal resources, or in my case it skipped multiple parts of the Ai flow because it thought it would save tokens since my board is pretty simple. Just a breakout board pretty much.

Cool thanks! Good tip thank you. Yeah for sure, it would just be convenient to have that right there IMO.

Oh interesting. Yeah just the regular Hydrogen desktop app. Yes VS code running inside of hydrogen. I did have VS code installed and being used on it's own for Fusion and stuff before installing Hydrogen so maybe some issues there. Oh cool, well not a big deal I'll just wait for that feature to ship :)

It's a big help thank you!

Screenshot-2026-11-18-160015.png

Colby Knox@kcknox

Thanks, that rules out my theory, since you're on the same setup as me. Your separate VS Code install shouldn't affect this, because Hydrogen's VS Code runs on its own. Two quick things would help me narrow it down:

  1. In VS Code inside Hydrogen, open the Extensions panel and find Claude Code. What version does it show? Mine is 2.1.327.
  2. Type a misspelled word in the Claude chat box and right-click it. Do any spelling suggestions show up, even without a red underline?
    I believe Hydrogen gets spell checking from Windows, so it's also worth checking that Settings › Time & language › Typing › Highlight misspelled words is on.

You can also just ask your Claude in Hydrogen something like "spell check doesn't work in the Claude chat box, can you figure out why?" It can see your extension version and your Windows settings, so it can probably track it down faster than we can back and forth. Either way, let me know what you find and I'll dig in from there.

Ray@ray

Hi Skyler,

Thank you for the kind words!

Regarding country of origin. I checked what we actually receive. The data we get gives us customs and export codes (HTS, ECCN) but no country of origin.

Origin can differ from one production lot to the next, so the distributors tend to put it on the shipment paperwork and not in the catalogue. It isn’t something we can show today. If one of them starts providing it, it’s a small add for us. But it is unfortunately not possible to do now.

We're looking into the no-WAGO problem :)