lilbee
Reduces time spent searching disparate knowledge sources and eliminates dependency on external APIs or indexing services, lowering operational overhead and i…
Terminal-first local search and AI chat over your documents, code, and crawled websites. Semantic + hybrid search, vision OCR, auto-built wiki, browsable GGUF model catalog. Works as CLI, TUI, MCP server, REST API, or Python library. Offline by default, no sidecar services.
- Ask Claude to search your codebase for implementation patterns across multiple files at once.
- Generate summaries of technical documentation by uploading PDFs and extracting key sections.
- Find answers from crawled internal websites without leaving your terminal or IDE.
Reduces time spent searching disparate knowledge sources and eliminates dependency on external APIs or indexing services, lowering operational overhead and improving search relevance across documents, code, and web content.
Engineering teams managing large internal codebases, documentation, and technical knowledge who need fast offline semantic search without external infrastructure.
https://github.com/tobocop2/lilbee
By tobocop2
How to Get It
claude plugins install tobocop2/lilbee
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Search my codebase for implementation patterns across multiple files at once
Trust Signals Auto-scanned
Community Pulse Emerging
Discussed on Reddit
1 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 39 GitHub stars; 3 contributors; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 39 GitHub stars; 3 contributors; last commit 0d ago; license MIT.