GitHub Copilot and Obsidian: Working With Markdown Notes

GitHub Copilot does not have an official Obsidian plugin or direct vault integration. What it does have is the ability to work with any markdown file you open in VS Code or another supported editor. If your Obsidian vault is on disk, you can open vault files in VS Code, use Copilot to draft or revise them, and save changes back to the vault. Tools like fenbs keep the project decisions and rules that should travel with the work regardless of which editor or AI tool you are using.

There are also third-party Obsidian plugins with names that include "Copilot," but these are not GitHub Copilot. They tend to call other AI APIs, such as OpenAI, and work independently of your GitHub Copilot subscription. This article focuses on using the real GitHub Copilot with Obsidian vault files.

How Copilot can work with vault files

Your Obsidian vault is a folder of markdown files on disk. VS Code can open that folder as a workspace. With GitHub Copilot active in VS Code, you get inline suggestions, the Copilot chat panel, and the cloud agent mode for vault markdown files the same as any other code or text file.

This means you can ask Copilot to help write or revise a note, extract structure from a long document, or generate a template. Changes save directly to the vault file, and Obsidian will show the updated content the next time you open it or if it is already open and the vault is set to detect external changes.

The difference between GitHub Copilot and Obsidian Copilot plugins

Searching Obsidian's community plugin directory for "Copilot" returns several plugins. These are not GitHub Copilot. They are community-built plugins that typically call OpenAI or other AI APIs and offer AI-assisted note features within Obsidian itself. They have their own API key requirements and are separate from any GitHub Copilot subscription you hold.

The distinction matters for two reasons. First, you should not assume a GitHub Copilot subscription gives you access to these plugins. Second, these plugins connect to different AI providers than GitHub Copilot, so their output quality, privacy practices, and cost structures differ.

Set clear boundaries for vault access

When you open a vault folder in VS Code, Copilot can see files in the workspace and may use open files as context for suggestions. Check which files Copilot sends as context through the Copilot settings or the chat panel's context indicators. If your vault contains sensitive personal or client notes, consider opening only the subfolder you need rather than the whole vault.

• Open only the vault subfolder relevant to the current work, not the entire vault.
• Check Copilot chat's context panel to see which files it is using.
• Avoid putting API keys, passwords, or personal financial data in vault notes you open in VS Code.
• Review Copilot's output before saving a note back to the vault.

Keep shared project decisions in fenbs

Copilot works well for individual note tasks: drafting, revising, extracting structure. What it does not carry between sessions is the project context: which decisions have been made, what the current tasks are, and what rules apply. If you are using Copilot across multiple vault notes over several sessions, keeping those rules in fenbs means a connected assistant reads them before any session starts.

For development projects that also involve vault notes, fenbs fits well alongside GitHub's own project tracking. The GitHub Copilot models article covers what different Copilot models are available and what they are suited for. For review workflows, AI agents for PR review explains how AI fits into code review without replacing human judgment.

How to do this with fenbs

Use Copilot in VS Code for note editing and fenbs for the project record that should apply across all your AI tools.

1. Create a free account and add a project for the work your vault notes support.
2. Write Decisions and rules for the project: which notes are approved sources, what phrasing or conventions apply, and anything else a session should respect.
3. Add the current tasks so any connected assistant knows what work is active.
4. Connect a supported AI app to fenbs via Integrations so the rules apply in every session, not just VS Code.
5. When a Copilot session produces a decision worth keeping, record it in fenbs before closing the editor.

What Copilot cannot do with Obsidian

Copilot cannot browse your vault from within Obsidian itself, trigger Obsidian-specific features, or interact with plugins. It works only when you open vault files in a supported editor. It also cannot write to vault files without you opening them first in that editor and saving manually or through the editor's save mechanism.