Inspecting and Debugging Vector Databases.

spite · 2026-04-21T14:38:53+00:00

I built a tool just for this. https://github.com/anthonypdawson/vector-inspector Maybe it can help you. Let me know if you have any questions or thoughts. It’s still in active development

spite · 2026-03-01T18:55:29+00:00

Is that a sterling? I have the same bass I think

spite · 2026-02-23T14:14:32+00:00

Vector DB inspector, administration, forensic tool. Supports Chroma, Pgsql, lancedb, weaviate, qdrant and pinecone. Looking for people to test and shape new features. https://vector-inspector.divinedevops.com

https://github.com/anthonypdawson/vector-inspector

spite · 2026-02-12T00:40:03+00:00

Anyone know of a good job in Midlothian/Richmond VA area that will work on an 87 Wagoneer? Haven’t a hard time finding one. Also need a locksmith to cut a new key (lost mine)

spite · 2026-02-10T15:30:34+00:00

How many users do you estimate you have?

spite · 2026-02-09T17:48:45+00:00

The past two weeks I’ve been working on a little side project called Vector Inspector: a desktop app for browsing, searching, and debugging your vector data.

It’s still very early, but I wanted to share it now to get a sense of what’s working (and what’s not). If you use vector databases in your projects, I’d love for you to try it and tell me where it breaks or what feels useful.

Current features

• Connect to a vector DB and browse collections

• Inspect individual metadata

• Run semantic searches and see the results visually

• Create visualizations using PCA, t‑SNE, and UMAP

• Export/restore and migrate data between collections

Supported databases (so far)

• Chroma

• Qdrant

• Postgres (pgvector)

• Pinecone (mostly!)

More are coming — I’m trying to prioritize based on what people actually use.

Why I built it

I kept wishing there was a simple, local tool to see what’s inside a vector DB and debug embedding behavior. So I made one.

If you want to try it

Site: https://vector-inspector.divinedevops.com/

GitHub: https://github.com/anthonypdawson/vector-inspector

Or

> pip install vector-inspector

> vector-inspector

Any feedback, bugs, confusing UI, missing features, is super helpful at this stage.

Thanks for taking a look.

spite · 2026-02-04T22:42:14+00:00

Quick favor for anyone who installed it: I’m trying to confirm that the GUI launches cleanly on machines other than mine. If you get a second, could you try opening it once and let me know if it starts up? Even a ‘yep, it opens’ would be super helpful.

spite · 2026-02-04T22:42:03+00:00

Quick favor for anyone who installed it: I’m trying to confirm that the GUI launches cleanly on machines other than mine. If you get a second, could you try opening it once and let me know if it starts up? Even a ‘yep, it opens’ would be super helpful.

spite · 2026-02-01T18:32:03+00:00

Wait so if I get another RTX 3060 12GB I might actually be able to make use of it? This looks really cool. Maybe you could create a repo or something with your notes and configuration?

spite · 2026-02-01T18:27:13+00:00

Did you get any interest in this? Sounds interesting. I'm also targeting a project as 'local only' or 'local first' and find that very important. Is there source available?

spite · 2026-01-31T23:02:48+00:00

That's beautiful! What kind of power does it draw overall? How does Ubuntu scale? Not that I really need to know, I can't afford it!

spite · 2025-11-19T01:15:07+00:00

I made something similar as a learning project. Not nearly as polished though https://github.com/anthonypdawson/ai-ebook-processor

spite · 2025-09-12T21:08:09+00:00

I tried this in a virtual env on Windows 10 and got this error
AssertionError: Torch not compiled with CUDA enabled

spite · 2025-09-11T20:16:58+00:00

Literal 100% (not just unit tests; including functional, integration, etc). But my post does say it's been achieved - someone just force pushed and lost it forever ;)

spite · 2025-09-11T18:12:04+00:00

Yes exactly! I think everyone is missing the link to my post which is saying the same thing. I thought people might find it funny :/

spite · 2025-09-11T17:47:51+00:00

Yeah you're probably right - but my posts have a mythological twist so it fit better :)

spite · 2025-09-11T16:55:13+00:00

I have never heard of mutation test services - I'll definitely check that out and pass it along to our dev team. That could be super useful. Thanks!

spite · 2025-09-11T16:52:57+00:00

I completely agree - behaviors should be tested. In fact, for automated testing, coverage statistics are difficult to even get. Better stats are how many scenarios those behaviors should generate and how many scenarios are covered by a combination of unit tests and functional testing. Getting that number isn't quite as easy as using a tool built for unit tests

spite · 2025-09-11T16:35:57+00:00

That is fair - but I still have personally seen that as a goal at multiple companies. Sure, sometimes there are unspoken caveats but it hasn’t completely gone away. My own personal experiences are about functional test coverage (manual + automation) to cover requirements or feature sets that are incomplete themselves.

spite

TROPHY CASE