Local Cursor over thousands of markdown files works solo, but team sharing stays unsolved
Petr275 · reddit · 2026-10-02
A Reddit user shares a practical playbook and its limits for running agents over a large internal docs corpus.
- What works: Running Cursor IDE on a local parent folder over thousands of small markdown files (procedures, per-client folders) handles both search and code execution well — vector retrieval "only covers the search half and never worked precisely."
- The bottleneck: Once teammates need the same setup, copying the folder means desynced knowledge bases with client notes stranded on individual machines.
- Failed attempts: Publishing via Azure AI Foundry never worked; syncing via SharePoint plus local Cursor is unsafe to maintain.
- Requirements: one shared, continuously edited knowledge base; an agent that searches files, runs code, and connects via MCP; cloud access without full local copies, ideally phone-friendly.
The author asks whether an existing product covers this or whether they should self-host a small internal harness.
More from coding & agent
- Alternating prompt and model upgrades lift science agent from 42% to 73% — rohanpaul_ai · 2026-10-02
- Simple Blocklists Don't Work Against Agents: One Python Concat Bypasses Them — rchardkovacs · 2026-10-02
- PewDiePie's open-source project Odysseus hits 88.5k stars, recruits co-maintainers — ben_burtenshaw · 2026-10-02
- Grok Build v1.0.48 adds better control over complex agent runs and parallel tool calls — XFreeze · 2026-10-02
- OpenAI and Perplexity rush out 'decision models' to compete with Jev, dev shares dead-code experiment — bendee983 · 2026-10-02
- Full-time agent developer: the hardest part of AI agents isn't AI, it's failure paths and handoff — jakes_takes_ · 2026-10-02