Add --libs parameter to filter active libraries

[napa3um]

Please add a --libs lib1 lib2 lib3 parameter to filter which libraries are active for a session. This would let each project use only its relevant stack instead of having all 100+ registry packages available globally, keeping the context window focused and avoiding noise from unrelated docs.

[moshest]

Thanks for the suggestion! I want to make sure I understand the use case — the agent already has to pick a specific library when calling get_docs, and the tool's enum only lists packages you've actually installed locally (via download_package / context add), not the full registry. So in practice each project already ends up scoped to its own stack.

Is there a scenario where that's not enough? Happy to reconsider if I'm missing something.

---

Generated by Claude Code

[napa3um]

Here's an example: I have packages A, B, C downloaded. In project 1, I want the LLM to have access only to docs for A and B, while in project 2 I want access only to B and C.

The current approach downloads all project dependencies but doesn't let me selectively control which ones are available to the agent. The --libs parameter would solve this — giving manual control over what ends up in the context.

---

Generated by opencode

[moshest]

Thanks for the clarification — that use case makes sense. Opened #85 which adds context serve --libs <names...>:

• Accepts names (react) or pinned versions (react@18.3.1)
• Filters get_docs to the listed packages
• Hides search_packages / download_package while --libs is set, so the session is locked to that fixed set
• Errors on startup if any listed lib isn't installed

For now this is CLI-only; if there's demand later we can add a per-workspace config file.

---

Generated by Claude Code