Chip Fetcher (cf) · manufacturer CAD bundles
No chip selected ·0 cards ·0 full ·0 stubs ·0 MB

Say it

You never need this page's buttons: just tell your AI what you want, using the word cf (chip fetcher). Copy a prompt, or send it straight to a new AI thread.

Getting started

Once cf feels familiar, close this whole panel with the X in its corner; the ? in the header brings it back. The library starts with a few sample parts seeded from the Adom Wiki so the cards below are real; delete them any time.

  1. 1
    Check the component lights above and fix anything that is not green. The Components card in Settings has an Install button for each one.
  2. 2
    Ask your AI for a chip by part number, using the word cf. Try it right now with a serious one, the STM32H757 (a 480 MHz dual-core H7):
  3. 3
    Cards appear here as parts are fetched. Each card carries the datasheet, the KiCad symbol, the footprint and the 3D model, with one-click open and send-to-EDA buttons. The demo above runs one fetch for you, live.
Loading the library

Chip Fetcher Settings

Components

Chip fetcher (cf) is five pieces working together. The Dashboard is this page and its server. The AI skills are what your AI reads to drive the app: the main skill with its 14 sourcing playbooks, the Dock Bar skill, and chip-fetcher-sites, a pack of per-vendor crawl guides (SnapEDA, Mouser, DigiKey, Ultra Librarian and more) that any Adom user can extend with a site they have figured out. The Sister tools are thirteen command-line programs the wiki installs automatically as cf's dependencies (adom-symbol, adom-footprint, adom-step, adom-lbr, adom-chipsmith, adom-chip-thumbnailer, adom-concur, adom-ds2sf, adom-sfconvert, adom-parts-search, adom-mouser, adom-digikey, adom-jlcpcb); nothing to manage, the light only exists to catch a broken install, and it shows how much machinery one cf prompt drives. The Desktop is a connected Adom Bridge box where pup runs Chrome to fetch files. The Library is the folder of fetched parts behind the cards.

These lights are cheap cached readings, not a background loop: file checks answer from disk, the desktop probe runs at most every five minutes, and only while this panel is open does the page re-read everything live (every fifteen seconds, so an Install you just ran turns green in front of you). Install buttons run the real command in the background and stream its output into a console under the row, ending with the exit code. Nothing here is silent.

Taskbar

While your AI runs a part lookup, chip fetcher paints an indeterminate progress bar on the dashboard's Windows taskbar button, so you can see it is working without a false estimate. The bar is driven through the Windows taskbar API on the connected desktop and clears itself the moment the lookup ends.

Taskbar: Progress during a lookup

What the dashboard's taskbar button does while a lookup is running.
Default: Indeterminate bar

Dashboard

How this page behaves while your AI works. Every switch applies the instant you flip it and is written to the settings file on this container; the page you are looking at is the preview.

Dashboard: Follow the active lookup

When a heartbeat names a new part, select that card and scroll it into view, so the detail panel always shows the part being fetched. Turn it off if you are inspecting one card while a long batch runs.

Select and scroll to the card being fetched
Default: On

Dashboard: Auto-zoom the active card

Zoom the active card into the centred overlay whenever the AI moves to a new part, so you can watch progress at a readable size without clicking each card. Press Escape or the X to drop back to the grid at any time.

Zoom the card being fetched
Default: Off

Dashboard: Stock and lifecycle badges on cards

Show a Mouser stock pill, and an NRND or end-of-life warning, on each card that has distributor data. With it off the cards stay lean and the same numbers remain in the detail panel's Status tab.

Show stock and lifecycle pills on cards
Default: On

Dashboard: Heartbeat considered stale after

Fetch jobs post heartbeats with no terminal state, so the page stops showing "Fetching" once the last heartbeat is older than this many seconds. Raise it for slow vendor sites, lower it if a finished lookup lingers.

seconds
Default: 90

Logins

Some vendor portals (Component Search Engine, Ultra Librarian, SnapEDA, TI, ST, Microchip) only hand out CAD files to a signed-in browser. pup keeps those logins in the desktop's OS keychain and fills them in the background when a lookup lands on a login page; chip fetcher stores none of them and never sees a password. This list shows host and username only.

Logins: Import my browser logins

Copies the saved passwords from your desktop's Chrome or Edge into pup's vault. Expect one consent dialog and one UAC prompt on the desktop; the output streams below.

Logins: Sign in to a vendor

Opens that vendor's sign-in page in the chip fetcher pup profile on your desktop and asks pup to fill the saved login. If there is none yet, sign in there once and pup captures it.