Qwen Code proposal adds a repo-bound external memory profile for trusted teams
doudouOUC · ghdev · 2026-07-23
Qwen Code proposal would add a repository-bound external memory provider
This issue proposes a Direct External Context Provider Profile for Qwen Code: an extension that lets one interactive CLI process pull repository-shared context from an administrator-bound external memory or knowledge service without changing Qwen Core.
The target user is a trusted repo team that already has:
- Mem0
- an enterprise knowledge base
- a RAG/search endpoint
The credential is meant to be restricted to a single repository corpus, and the design is intentionally smaller than the more general multi-tenant gateway discussed in another issue.
The post also includes a comparison of current coding-agent patterns:
- repo instructions/rules loaded as context
- local project-scoped memory generated by the agent
- external systems connected through MCP or product-specific retrieval
Its core argument is that existing agents do not treat a client-supplied repo ID, memory entity ID, or search filter as a real enterprise authorization boundary.
More from coding & agent
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- 105 hidden bugs, 2 repos: DeepSeek V4.1 Flash fixes 24 at $1.80 vs Opus 5's 27 at $51.33 — ChartsJournalX · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- Running the Firefox MCP on Android via Termux, ngrok, and mcp-proxy — Nervous-Strain7544 · 2026-09-11
- SmolVM open-sources persistent computer infrastructure for agents that outlive chat sessions — aniketmaurya · 2026-09-11