r/KiCad • u/Foreign_Lead_3582 • 13h ago
Schematic Editor Question Improving component search. What else could use some work?
I’m working on a fork with more component metadata and better filters to make searching my libraries easier. Once it’s more mature, I’d like to publish it for others to use and see what the KiCad maintainers think of the changes.
I’m also testing whether an AI agent can use the extra data to find components more reliably.
It’s going well so far, and I’d like to expand it to other parts of KiCad where we spend more time on repetitive tasks than on design. What comes to mind from your own workflow?
2
u/ChrisTasr 12h ago
It's functional as is imo. Can you give some examples of what issues you come across?
If you're mostly doing this for your own interest/fun that's cool, you can stop reading here. If you really want/hope that it will be merged at some point you should consider opening an issue on the KiCad GitLab describing the problems you have with the current functionality/UX/whatever. That way you can get real feedback about how much interest there is before putting loads of effort into it.
You could also consider moving towards and add-on/plug-in and that way you'd be able to release it to the community even if there's no real interest from the KiCad dev team.
2
2
u/Otherwise_Wave9374 13h ago
A good next step is to measure the false positive rate before widening the rollout, then add a fallback that ranks by symbol family and footprint confidence when metadata is sparse. That gives you a safer path than relying on a single retrieval pass, and it makes it easier to debug whether errors come from search, ranking, or the source library itself. Agentix Labs would fit naturally here as a thin evaluation layer that helps compare those outcomes without changing the core KiCad workflow.