Lybrary,a persistent AST-aware code memory for AI agents(MCP server pip install)
On a large codebase this happens dozens of times per session. The solution lybrary gives your agent a persistent memory it can query instead of reading files. agent: memory_query("authentication flow") ↳ 3 chunks returned. Run the test suite with: pip install -e ".[dev]" pytest 📄 License MIT
- ▪On a large codebase this happens dozens of times per session.
- ▪The solution lybrary gives your agent a persistent memory it can query instead of reading files. agent: memory_query("authentication flow") ↳ 3 chunks returned.
- ▪Run the test suite with: pip install -e ".[dev]" pytest 📄 License MIT
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,046 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/vibhu-dixit/lybrary |
| Publication time | Sat, 08 Aug 2026 05:01:16 +0000 |
| Retrieval time | 2026-08-08T05:10:47.630Z |
| Last seen | 2026-08-08T05:10:47.630Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | txgFlqA24IVZ · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
🧠 lybrary Living structure-aware code memory for AI coding agents. pip install lybrary The problem Every time an AI agent starts a session, it re-reads your codebase from scratch. agent: let me grep for auth logic... agent: reading src/auth/middleware.py... agent: reading src/auth/jwt.py... agent: reading src/auth/session.py... agent: reading src/utils/crypto.py... ↳ 4,000 tokens burned before writing a single line. On a large codebase this happens dozens of times per session. Tokens wasted. Context filled. Same files read over and over. The solution lybrary gives your agent a persistent memory it can query instead of reading files. agent: memory_query("authentication flow") ↳ 3 chunks returned. 180 tokens. Done.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.