AI Context Sync

unlisted

by Mitchell Tatge

Sync your AI context notes to CLAUDE.md, .cursor/rules/, AGENTS.md, and more. One source of truth for all your AI coding assistants.

Updated 1mo agoMIT
View on GitHub

AI Context Sync for Obsidian

GitHub release License: MIT

One source of truth for all your AI coding assistants.

Tired of maintaining separate context files for Claude, Cursor, GitHub Copilot, and other AI tools? This Obsidian plugin lets you write your project context once and sync it everywhere.

AI Context Sync Demo

The Problem

Modern AI coding assistants use different context files:

  • Claude CodeCLAUDE.md
  • Cursor.cursor/rules/*.md (works with GPT, Claude, Gemini, DeepSeek, etc.)
  • GitHub Copilot.github/copilot-instructions.md
  • Windsurf/Codeium.windsurfrules
  • Continue.dev.continuerules
  • Sourcegraph Cody.cody/instructions.md
  • OpenAI Codex CLIAGENTS.md
  • DeepSeek CoderDEEPSEEK.md
  • Google Gemini.gemini/context.md
  • Amazon Q.amazonq/rules.md
  • Zed AI.zed/assistant/context.md
  • Aider.aider.conf.yml
  • ChatGPT → Manual memory export
  • AGENTS.md → Universal standard (emerging)

When you work primarily with one tool (like Claude) but occasionally switch to others (like Cursor with GPT), your carefully crafted context doesn't transfer. You end up maintaining multiple files or getting subpar assistance.

The Solution

Write your AI context once in Obsidian, sync to all your tools automatically.

                    ┌─────────────────────┐
                    │   Obsidian Note     │
                    │   "AI Context.md"   │
                    └─────────┬───────────┘
                              │
                              ▼
                        ┌───────────┐
                        │ AI Context│
                        │   Sync    │
                        └─────┬─────┘
                              │
       ┌──────────┬───────────┼───────────┬──────────┐
       ▼          ▼           ▼           ▼          ▼
   ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
   │CLAUDE  │ │AGENTS  │ │.cursor/│ │.windsurf│ │.github/│
   │.md     │ │.md     │ │rules/  │ │rules    │ │copilot │
   └────────┘ └────────┘ └────────┘ └────────┘ └────────┘
       │          │           │           │          │
       ▼          ▼           ▼           ▼          ▼
    Claude    DeepSeek     Cursor      Windsurf   Copilot
              Codex CLI   (any model)  Codeium
              Gemini
              ChatGPT*

*ChatGPT export is for manual copy/paste into memory

Features

  • 🔄 Auto-sync - Syncs automatically when you save your source note
  • 🎯 Multi-target - Sync to Claude, Cursor, Copilot, AGENTS.md, and more
  • 📁 Multi-project - Sync to multiple project directories at once
  • 📝 Templates - Customizable output templates per target
  • Commands - Quick commands for manual sync and configuration
  • 📊 Status bar - See sync status at a glance

Installation

From Obsidian Community Plugins (Recommended)

  1. Open Obsidian Settings
  2. Go to Community Plugins → Browse
  3. Search for "AI Context Sync"
  4. Click Install, then Enable

Manual Installation

  1. Download the latest release from GitHub Releases
  2. Extract to your vault's .obsidian/plugins/ai-context-sync/ folder
  3. Reload Obsidian
  4. Enable the plugin in Settings → Community Plugins

From Source

git clone https://github.com/mctatge/obsidian-ai-context-sync.git
cd obsidian-ai-context-sync
npm install
npm run build

Copy main.js, manifest.json, and styles.css to your vault's .obsidian/plugins/ai-context-sync/ folder.

Quick Start

  1. Create your context note - Use the command AI Context Sync: Create AI context template note to get started with a template, or use any existing note

  2. Set as source - Open your context note and run AI Context Sync: Set current note as AI context source

  3. Add project paths - Run AI Context Sync: Add project path to add your project directories

  4. Sync! - Click the sync icon in the ribbon or run AI Context Sync: Sync AI context to all targets

Configuration

Settings

SettingDescription
Source noteThe Obsidian note containing your AI context
Auto-sync on saveAutomatically sync when source note is modified
Show status barDisplay sync status in Obsidian's status bar
Include timestampAdd timestamp comments to synced files
Custom headerHeader comment added to all synced files

Sync Targets

Enable/disable specific targets in settings:

TargetOutput PathDescription
Claude CodeCLAUDE.mdClaude Code's context file
AGENTS.mdAGENTS.mdUniversal standard (Codex, DeepSeek, etc.)
Cursor Rules.cursor/rules/ai-context.mdWorks with ALL Cursor models
GitHub Copilot.github/copilot-instructions.mdCopilot custom instructions
Windsurf.windsurfrulesWindsurf/Codeium rules
Continue.dev.continuerulesContinue for VS Code/JetBrains
Sourcegraph Cody.cody/instructions.mdCody context instructions
OpenAI Codex CLIAGENTS.mdCodex CLI reads AGENTS.md
ChatGPT.chatgpt/project-context.mdExport for manual memory
DeepSeek CoderDEEPSEEK.mdDeepSeek context file
Google Gemini.gemini/context.mdGemini/AI Studio context
Amazon Q.amazonq/rules.mdAmazon Q Developer rules
Zed AI.zed/assistant/context.mdZed editor AI assistant
Aider.aider.conf.ymlAider configuration

Project Paths

Add multiple project directories to sync your context to all your codebases:

  • /Users/you/projects/my-app
  • /Users/you/projects/another-project
  • /Users/you/work/client-project

Commands

CommandDescription
Sync AI context to all targetsSync to all enabled targets
Sync AI context to specific targetChoose a specific target to sync
Set current note as AI context sourceSet the open note as the source
Add project pathAdd a project directory for syncing
Create AI context template noteCreate a starter template

Template Variables

Use these variables in custom templates:

VariableDescription
{{CONTENT}}The content of your source note
{{HEADER}}The configured header comment
{{TIMESTAMP}}Current ISO timestamp
{{SOURCE}}Path to the source note

Example Context Note

# AI Context

## Project Overview
A React + TypeScript web application for task management.

## Tech Stack
- Frontend: React 18, TypeScript, TailwindCSS
- Backend: Node.js, Express, PostgreSQL
- Testing: Vitest, Playwright

## Coding Conventions
- Use functional components with hooks
- Prefer named exports
- Use `const` by default, `let` only when reassignment is needed
- Error handling: Always use try/catch with proper error types

## File Organization
- `src/components/` - React components
- `src/hooks/` - Custom hooks
- `src/utils/` - Utility functions
- `src/types/` - TypeScript type definitions

## Important Patterns
- State management via Zustand
- API calls through custom `useQuery` hook
- Form handling with React Hook Form + Zod

## Things to Avoid
- Don't use `any` type
- Don't use default exports (except for pages)
- Don't mutate state directly

Why Obsidian?

Obsidian is the perfect home for AI context because:

  1. Already in your workflow - If you use Obsidian for notes, your context is always accessible
  2. Markdown native - Perfect format for AI context files
  3. Linking - Link your context to other notes, documentation, decisions
  4. Version history - Track changes to your context over time
  5. Cross-platform - Access and edit from any device

Roadmap

  • Import existing CLAUDE.md/AGENTS.md back into Obsidian
  • Template library for common project types
  • Git integration (auto-commit synced files)
  • Selective section sync (sync only parts of a note)
  • VS Code extension companion

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/AmazingFeature)
  3. Commit your changes (git commit -m 'Add some AmazingFeature')
  4. Push to the branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

MIT License - see LICENSE for details.

Acknowledgments

  • Inspired by the fragmentation of AI context files across different tools
  • Built with the Obsidian Plugin API
  • Thanks to the Obsidian community for plugin development resources

Built by Mitch Tatge.

Found this useful? Give it a ⭐ on GitHub!

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.