Capture what matters
Bring useful outcomes from connected conversations and tools into your knowledge.
WormVoltAn open-source project in development
We’re building WormVolt to grow your Obsidian and Markdown knowledge through everyday AI use—and keep the right context moving between your tools and agents in the background.
Knowledge you own. Context you can reuse.
Freedom to change tools.
WormVoltYour knowledgeA brain that
stays with you.
01 / An evolving Obsidian brain
Your decisions, research, preferences and project history become more valuable when they build on each other. WormVolt’s design brings them into a living Markdown vault, where useful AI work can develop the knowledge over time.
Start with what you know. Capture useful additions, revise existing notes and improve how the knowledge is organised as your work develops.
Explore the knowledge lifecycleBring useful outcomes from connected conversations and tools into your knowledge.
Develop records, relationships and structure instead of endlessly accumulating disconnected transcripts.
Inspect and edit your knowledge, with Obsidian as a natural working environment.
The brain is your maintained knowledge—not a model’s weights.
02 / Asynchronous by design
Capture a change, refine the relevant knowledge and propagate permitted information to connected vaults while the current task continues. A background update can lead to a revision, an archive, a new version or further activity—under each volt’s definition.
Useful results enter working knowledge.
Relevant notes and structure develop.
Context is selected and transformed.
Another tool starts from maintained knowledge.
Background work can continue independently. A task that needs a particular update may still need to wait for it.
Inside the background flow03 / Your knowledge, beyond one provider
Models change. Prices change. Your knowledge should remain useful. WormVolt’s architecture separates the knowledge you build from the AI service you happen to use.
A structured, extensible vault gives new tools a starting point. Suitable connectors select and adapt what they need, preserving the work of organising your knowledge as your setup evolves.
Understand portability and connectorsThe foundation stays
Notes · Relationships · Definitions
Add a specialist tool. Combine providers. Keep more options when needs or prices change.
Architecture illustration. Connections need adapters and testing; switching does not guarantee identical results or lower total costs.
04 / Autonomy, defined by you
Some knowledge should stay stable. Some should evolve freely. Some can travel widely; some belongs in a narrower context. A volt’s definition sets those boundaries.
Updating knowledge, using it as context and sharing it onward are separate decisions. Automatic working knowledge can coexist with a stable reference or a reviewed publishing destination.
Explore definitions and autonomyIllustrative definition—not configuration syntax or a demonstration of implemented controls.
05 / An open-source ambition
The ambition is bigger than a single assistant: a knowledge layer that people can use, developers can extend and a community can help improve.
Inspectability, reusable knowledge structures and adaptable connections sit at the centre of the project.
Explore the open-source directionHelp establish which knowledge flows are useful in real work.
Help shape adapters, transformations and reusable definitions.
Help develop documentation, tests and clearer behaviour.
Explore the possibilities
Keep preferences, research and useful history with you as your tasks and tools change.
Explore the scenario 02 /Carry decisions, constraints and project knowledge into the next development task.
Explore the scenario 03 /Give customer-facing tools and internal teams appropriate views of maintained information.
Explore the scenarioBuild with us
Explore the architecture and help turn portable, evolving knowledge into an everyday tool.