Run local AI models, search your files and code, and crawl the web, all in one program. Cited answers, local-first, w...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Llama
Fastest way to find out if lilbee belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add lilbee -- npx lilbeeRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove lilbeeNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ lilbee ← registers here
Run local AI models, search your files and code, and crawl the web, all in one program. Cited answers, local-first, with an MCP server for your coding agent. TUI, CLI, REST API, and Python library.