Documents are read from and saved to a GitLab or GitHub repository. Every save is a commit with your message.
Your access token is stored only in this browser.
Pick a file in the vault
Select a document in the file tree, or create a new one.
Linked from
Insert Table
Insert Link
Find & Replace
Welcome to NoCloudMD - Vault
Markdown notes kept in your own Git repository (GitLab or GitHub). The app runs only in this browser: no server, no account. Every save is a commit with your message.
1. Connect your repository
Use a GitLab project (gitlab.com or your own server) or a GitHub repository; a new empty one works.
Create an access token with an expiry date:
GitLab: Project or Personal Access Token, scope api, role Developer or higher.
GitHub: fine-grained token for that repository, Contents: Read and write.
In Repository connections (the Connect repository button at the top), choose the provider and server, the project (group/name), the branch and, optionally, a vault folder for the notes.
Paste the token, click Test connection, then Save and open. Optionally protect the token with a local password.
The token stays only in this browser and is sent only to your Git server. Commits go only to the branch you chose.
2. Quick tips
Files: the sidebar creates files and folders; drag to move. Ctrl+O filters by name, Ctrl+Shift+F searches the text.
Write: switch Preview / Edit at the top; the toolbar formats Markdown, tables, links (Ctrl+K) and Mermaid diagrams.
Save with Ctrl+S: pick the files and write the commit message. Nothing reaches the repository before that.
Organize: [[Note]] links notes, #tags and properties (YAML at the top) group them, and a ```query block lists notes as a table.
Attach by dropping or pasting files; they go to attachments/.
Teams: if someone changed the same file, saving shows a conflict screen where you can merge both versions.
More: version history, templates, offline work, BPMN diagrams and the optional AI assistant are explained in Help.
Repository connections
Saved connections0 connections
Add connection
New document
Attach files
Move file
New file
Save to repository
File changed in the repository
Repository version
Your version
Merge changes
The merged file. You can edit it before using it; conflicts not resolved yet appear between <<<<<<< Yours and >>>>>>> Repository.
You edited the result by hand, so the choices in Conflicts no longer change it.
Version history
AI assistant
Off by default. When it is on, your requests and the text of the notes chosen as context (always listed before sending) go to the AI provider of the active profile, at the address shown in the panel. Ollama running on your own computer keeps everything on it. The assistant never commits: its text becomes unsaved changes that you review and save.
Profiles and keys are stored only in this browser. Use keys created for this purpose, with a spending limit: a script injected into this page could read them. Protect them with a local password to keep them encrypted.
Profiles
Removes every profile and key from this browser and turns the assistant off.
Coding agents
Claude Code and Antigravity run on your computer, on a clone of this repository: they edit the notes, commit and push to the branch, and Refresh brings their changes here. The app sends nothing to them or to any service; your access token is never part of the commands.
1. Guide for agents
Creates AGENTS.md (conventions of this vault, read by both agents) and CLAUDE.md (imports it for Claude Code) in the vault folder, with a commit.
2. Hand a task to an agent
First time: clone the repository
In the clone's folder, run:
Run git pull in the clone, open its folder in Antigravity and paste this request in the agent panel:
When the agent has pushed, click Refresh. Open files with unsaved changes that the agent also changed go to the conflict screen when you save them.
Unlock the AI keys
Graph of links
NoteMermaidAttachmentMissingClick a node to open it · hover to see its links · scroll to zoom