11–20 of 92 posts
The context problem with coding agents is real. We've been coordinating multiple agents on builds - they often re-scan the same files or miss cross-file dependencies. Interested in how Nia handles this - knowledge graph or smarter caching?
This looks neat, we certainly need more ideas and solutions on this space, I work with large codebases daily and the limits on agentic contexts are constantly evident. I've some questions related to how I would consume a tool like this one: How does this fare with codebases that change very frequently? I presume background agents re-indexing changes must become a bottleneck at some point for large or very active team…
For large and active codebases, we avoid full reindexing. Nia tracks diffs and file level changes, so background workers only reindex what actually changed. We are also building “inline agents” that watch pull requests or recent commits and proactively update the index ahead of your agent queries.
Local vs upstream divergence is a real scenario. Today Nia prioritizes providing external context to your coding agents: packages, provider docs, SDK versions, internal wikis, etc. We can still reconcile with your local code if you point the agent at your local workspace (cursor and claude code already provide that path). We look at file paths, symbol names and usage references to map local edits to known context. In cases where the delta is large, we surface both the local version and the latest indexed version so the agent understands what changed.
[under-the-rug stub] [see https://news.ycombinator.com/item?id=45988611 for explanation]
[under-the-rug stub] [see https://news.ycombinator.com/item?id=45988611 for explanation]
> favorite doc sites so I do not have to paste URLs into Cursor
This is especially confusing, because cursor has a feature for docs you want to scrape regularly.
Cursor promises to do this[0] in the product, so, especially on HN, it'd be best to start with "why this is better than Cursor". > favorite doc sites so I do not have to paste URLs into Cursor This is especially confusing, because cursor has a feature for docs you want to scrape regularly. 0 - https://cursor.com/docs/context/codebase-indexing
[under-the-rug stub] [see https://news.ycombinator.com/item?id=45988611 for explanation]
Absolutely insane that we celebrated coding agents getting rid of RAG, only with the next innovation being RAG