Reports indicate that Microsoft is testing Project Pantheon under the name Context Vault, a Windows 11 AI information app that stores content users manually add rather than automatically taking regular screenshots. Users can save webpages, files, screenshots, text, audio and video, then use AI to organize, search, summarize and ask questions about the material. The reports describe Windows entry points, including the File Explorer sharing menu and Click to Do, as well as Model Context Protocol access for tools such as Claude and Cursor. One report says the app must be installed from the Microsoft Store, while another describes deeper Windows integration; the app is not officially listed and its release remains uncertain.
What problem it solves
Software work often needs several agents to handle independent tasks while preserving clear model routing, file ownership, and verification. It is also important to distinguish work that was planned or reported complete from work supported by observed test, review, or CI results.
Key features
Model routing by work category — Each lane receives a work category, model chain, a…
The common approach to RAG is to first collect documents into a vector database, then retrieve context from it in response to a query. This workflow is smooth, but it has an organizational prerequisite: data owners are willing to hand their materials to the same infrastructure. In cross-organizational collaboration, this is often the hardest step to coordinate. Hospitals, research institutions, an…
What problem it solves
Teams that rely on AI agents need a way to give each agent a role, workspace, and instructions, keep context across conversations, and control what agents are allowed to do. Without that, agents run blind: actions happen without review, memory does not persist, and repeating scheduled work means redoing setup by hand.
Key features
Create agents and teams — Give an agent a na…
What problem it solves
Coding agents commonly pause for human approval before risky steps, which makes unattended repository work difficult to run in CI, daemons, and scheduled jobs. Teams also need consistent policies, tools, and supervision across different execution environments without maintaining separate framework integrations.
Key features
Repository tooling through MCP — Give an LLM tools …
What problem it solves
Coding-agent notes are commonly tied to one machine, one agent, or a single tool, so important context disappears when work changes hands or continues elsewhere. Teams also need a shared, durable way to preserve decisions, failed approaches, session state, and open questions without depending on opaque storage or an LLM for every operation.
Key features
Shared memory across …
What problem it solves
Coding agents often need to read many files into their context to locate relevant code and documentation. Projects also need a shared way to search code, structured data, logs, and documents, retain agent memory, and expose those capabilities through familiar APIs and MCP clients.
Key features
Automatic folder indexing — Point the CLI at a folder and XERJ detects file types,…
What problem it solves
Teams building retrieval-augmented AI systems need to extract useful knowledge from complex, heterogeneous documents and ground generated answers in traceable evidence. They also need an orchestrated workflow that can combine document understanding, chunking, retrieval, reasoning, and citations.
Key features
Deep document understanding — Extract knowledge from unstructured d…
After an Agent completes a task, what it leaves behind is often more than an answer. There is also an expensive exploration path: which files it read, which tools it tried, where it failed, and what checks it used to confirm the result. The problem is that the next execution may not be able to use those experiences. The model parameters have not changed, and a new session will not naturally inheri…