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
- Anthropic researcher: 99% of engineers now run swarms of 300+ self-improving agents — AlishaOutridge · 2026-09-11
- Gergely Orosz: Shipping 10x PRs With AI Agents, Sites Fill With Small Regressions — ducha_aiki · 2026-09-11
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11