From notes to cited knowledge
PocketContext
vs Obsidian
Obsidian is a strong home for notes you write and link yourself. PocketContext fits when you want an agent to turn collected material into cited knowledge while preserving the sources and each published revision. The two can work alongside each other.
WHAT YOU GAIN
Why choose PocketContext?
Separate evidence from interpretation.
PocketContext preserves the original files you ingest. Pages are separate, revisable interpretations with citations to source passages. Agent conversions of PDFs, images and audio are explicitly recorded as derived text.
Publish connected changes together.
An agent can stage a revised overview and its related pages, check their citations and links, and publish them as one update. Earlier published revisions remain available in the reader.
Use one running knowledge base.
Keep PocketContext on an always-on computer and connect authenticated agents to it. In that setup, you do not need to synchronize note copies between those computers. The host and connection must remain available.
AN ILLUSTRATIVE WORKFLOW
“What do these research notes agree on?”
Start with
Your vault contains several reading notes and source documents. You want a synthesis that distinguishes agreements, disagreements and missing evidence.
Build with PocketContext
Keep writing in Obsidian. Bring selected material into PocketContext and ask your agent to publish a cited research overview. When new evidence arrives, publish a new revision and retain the earlier interpretation.
THE TRADEOFFS
When Obsidian fits better
Obsidian wins for directly editable files.
An Obsidian vault is already a local folder of Markdown files that other editors can open. PocketContext pages contain Markdown, but live in SQLite with citations and history. Version 0.24.0 has no built-in page exporter; an agent can prepare exports separately.
Choose the writing experience you prefer.
Keep Obsidian if editing your vault is central to your workflow. PocketContext provides a browser reader and agent-driven knowledge updates. Its optional import script brings a snapshot of supported collections, not ongoing two-way synchronization.
Your knowledge, away from your desk
Your knowledge.
In the app you use.
Connect your preferred MCP app to PocketContext through your own domain, or open the reader to browse pages and follow citations. Your host keeps the knowledge; your chosen app brings the conversation.
- 01 / Your phoneChoose your interfaceUse the reader, or connect a compatible MCP app and check access on your phone.
- 02 / Your main computerYour host serves the knowledgeKeep it awake and online for access away from home.
- 03 / Your project folderPocketContext keeps the knowledgeSources, cited pages and history stay together.
PocketContext 0.24.0 has no built-in chat. Your chosen agent supplies the conversation; the phone reader provides browsing and search. Custom-app availability, attachments and voice support depend on the client. Confirm a read on your own phone during setup. Public hosting is optional, and local-only use remains available.
A SMALL FIRST STEP
Bring a copy. Keep what works.
- Start with a copy of one collection. Preserve the original vault and decide which app owns future edits.
- For compatible Obsidian collections, the optional repository import helper requires Python 3.10+, a matching source checkout and a local PocketContext project. Review its audit for unsupported or missing material.
- Imported prose is marked as needing verification. Ask your agent to review it against the sources before treating it as cited synthesis. Refreshes and exports remain separate agent workflows.
CHECK THE DETAILS
Sources & scope
Based on PocketContext 0.24.0 and documentation reviewed November 3, 2026. Product capabilities and account availability can change. Examples illustrate workflows, not completed integration tests.
Give your knowledge a home.
Start with two notes and ask your agent for an answer you can trace.
Set up PocketContext Explore the other comparisons