> Docker `:latest` tag guarantees you always get current docs without manual updates.
The docs should probably be pinned to the version of the tool you have installed. Aside from that, pinning to a specific container hash (not tag) allows you to audit it and trust that malicious instructions haven’t been introduced into the docs.
mrbonner · 4h ago
Even though your demo is not that helpful, I appreciate you sharing this. I think it opens my eyes for another ideas of providing better documentation for coding agent. I believe the current RAG-based approach for coding agent is not the most optimal solution.
keminghe · 4h ago
Thank you. Yes, 50% of the core value prop is the self-updating automation and the traditional fuzzy + full text search capabilities that disrupt the embedding-centric RAG paradigm. Plus, Tantivy (Rust-based) is fast.
WhatsName · 6h ago
The demo is not convincing, I rarely find myself migrating between package managers and if I do I would expect claude code to ace this task without mcp help.
keminghe · 5h ago
Appreciate the feedback. I will make it my todo to try out your suggestion of comparing Claude Code with and without MCP to measure the quantitative difference.
keminghe · 4h ago
Genuinely curious: what are aspects of the demo you find less helpful? I want to improve it.
dcreater · 5h ago
This is superceded by Context7 no?
hobofan · 4h ago
I think in terms of providing the widest coverage, I think Dash[0] which has been in the offline documentation space for a long time should have everyone beat.
Appreciate you opening my eyes to this. Dash is indeed comprehensive, and a much bigger initiative. I wonder how it's handling the documentation staleness issue? New docs are published every minute.
hobofan · 4h ago
For the package manager ecosystem it supports, it relies on the projects auto-generated docs, and the builds the docsets from those. I guess it does that step in a cached on-demand way. That way, it can provide docs to all the packages and package versions.
E.g. for Rust: Crate is published crates.io -> triggers automatic docs build on docs.rs -> Dash clients can now pull docsets through a proxy that builds the docsets built on the static HTML bundles built for docs.rs.
keminghe · 3h ago
I see, yes, with this implementation, the networking component becomes necessary. I made different design decisions for `py-dep-man-companion` such that the tool is fully offline and can be used with local llms.
The docs should probably be pinned to the version of the tool you have installed. Aside from that, pinning to a specific container hash (not tag) allows you to audit it and trust that malicious instructions haven’t been introduced into the docs.
[0]: https://blog.kapeli.com/dash-8
E.g. for Rust: Crate is published crates.io -> triggers automatic docs build on docs.rs -> Dash clients can now pull docsets through a proxy that builds the docsets built on the static HTML bundles built for docs.rs.