- Home
- Skills
- Technical Documentation
- Vault Sync: Shared Memory for AI Coding Agents
Works with the AI Agents you already use
Vault Sync: Shared Memory for AI Coding Agents
Saves each coding session to your Obsidian vault, so the next agent you open already knows what was done and why.
Free
Vault Sync: Shared Memory for AI Coding Agents
Example session with this skill installed
Sync the vault. We added Google login with NextAuth and fixed the redirect loop after sign-in.
- Read your context and instructions
- Compiled the vault sync
Synced this session to your vault
- Created
01_Projects/shop-app/Chats/2026-10-26.md - Updated
01_Projects/shop-app/README.md(Progress Log, Key Decisions, Problems & Solutions, TODOs)
Chats/2026-10-26.md
# shop-app — 2026-10-26
**Goal:** Add Google login and fix the redirect loop after sign-in.
## Done
- Added the Google provider to NextAuth in `src/auth.ts`
- Protected `/account` and `/orders` in `src/middleware.ts`
- Added a sign-in button to `src/components/Header.tsx`
## Decisions
- Database sessions instead of JWT — admins need to revoke sessions
## Problems & fixes
- Redirect loop after the Google callback → `NEXTAUTH_URL` was http in prod; switched to https
## Next
- Add the GitHub provider
- E2E test for the sign-in flow
README.md: new entries
## Key Decisions
- Database sessions (Prisma adapter) instead of JWT, so admins can revoke sessions. (2026-10-26)
## Progress Log
- **2026-10-26** — Google login via NextAuth; fixed the prod redirect loop. [[Chats/2026-10-26]]
## Open Questions / TODOs
- [ ] Add GitHub provider
- [ ] E2E test for sign-in
Connects securely to your tools. The creator never sees your data.
About this skill
Switch from Claude Code to Cursor, or just open a new chat, and you usually end up explaining your project all over again. Vault Sync writes every session to your Obsidian vault, so the next agent can read it instead.
At the end of a session it:
- writes a short chat log to
Chats/YYYY-MM-DD.md: the goal, what changed, decisions, problems and fixes, next steps - updates the project's living README: tech stack, key decisions, problems and solutions, progress log, TODOs
Why use it
- Plain Markdown in your own vault. No server, no account, no API keys.
- Works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Copilot, Windsurf, Cline, Antigravity and more.
- Never overwrites an existing log, and keeps secrets out of your notes.
Setup: set VAULT_PROJECTS_ROOT to your vault's projects folder (for example ~/Vault/01_Projects), or tell the agent the path once.
Pair it with Vault Recall, which loads this memory at the start of the next session.
Open source (MIT): https://github.com/ali-novruz/universal-vault-sync
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
- Runs when you ask for it ("sync the vault"). It does not sync automatically.
- The agent needs permission to read and write files in your vault folder. Browser-only chats without file access can't use it.
- Summaries come from what the agent still has in context. In very long sessions that were compacted, early details may be missing.
- The project is identified by the workspace folder name. Renaming the folder starts a new project note.
- The vault path comes from VAULT_PROJECTS_ROOT (or CLAUDE_VAULT_ROOT). If neither is set, the agent asks you once.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
Trust & safety
Security scan
Security scan passed 21 days ago
- Free with an Agensi account
Nothing to install. It runs in your AI agent.
- Optional
- Obsidian
Any Markdown folder works instead of Obsidian.
Permissions
File Scopes
Reads and writes Markdown files only inside your vault's projects folder. Reads VAULT_PROJECTS_ROOT to find that folder (or asks you once). No network access, no shell commands.