Copilot's agent mode in VS Code reads and writes the files in your open workspace. Open your Obsidian vault there today and your tasks, which are plain markdown lines, are just more files it can edit. TaskForge 3.0 adds a taskforge/agents.md contract file to the vault so Copilot gets your exact format right instead of guessing. Want typed tools instead of free-form edits? VS Code speaks MCP, and the taskforge server, also shipping with 3.0, will drop in too.
Coming in TaskForge 3.0
The TaskForge CLI and MCP server ship with the TaskForge 3.0 release. Everything on this page describes how they will work at launch. The TaskForge app is available today.
Copilot's agent mode edits workspace files directly, which is enough on its own. The MCP server is there if you want the agent to call add and complete tools instead of writing lines by hand.
Open your vault in TaskForge 3.0 or later, then Settings, AI & Agents, and keep "Generate agent files" on. TaskForge writes a taskforge/ folder describing your task format so Copilot writes tasks in your dialect.
File, Open Folder, and choose your vault. Copilot now sees every note, including the taskforge/ contract, as part of the workspace.
In the Copilot Chat panel, switch to agent mode so it can edit files. Tell it to read taskforge/agents.md before adding or changing tasks. Add the same instruction to a .github/copilot-instructions.md and it applies to every session.
# .github/copilot-instructions.md This folder is an Obsidian vault. Before adding or editing tasks, read taskforge/agents.md and follow its exact syntax.
VS Code supports MCP servers. Add taskforge and Copilot's agent gets the same typed tools the desktop clients use: add_task, query_tasks, complete_task, and the rest.
Get Free - iOS & Mac 
Get Free - Android // .vscode/mcp.json
{
"servers": {
"taskforge": {
"command": "npx",
"args": ["-y", "taskforge-md", "mcp", "--stdio"],
"env": { "TASKFORGE_VAULT": "/path/to/your/vault" }
}
}
} The taskforge/ folder is the source of truth either way. Agent mode reads agents.md as a workspace file; the MCP server exposes the same data as resources. So Copilot writes a task in your dialect, with your renamed fields and status symbols, instead of a generic checkbox.
| taskforge/agents.md | Your task syntax in plain English, the file your Copilot instructions point at. |
| taskforge/schema.json | The machine-readable version, exposed to the MCP server as taskforge://schema. |
| taskforge/lists.json | Your saved lists and where new tasks land, so a task filed to a named list goes to the right note. |
Ask Copilot in the chat panel with the vault open in agent mode. It reads the contract, edits the markdown, and shows the change as a diff you approve.
You ask Copilot
“Read standup.md and add each of my action items to tasks/this-week.md, due Friday.”
What lands in the file
- [ ] update the deploy runbook 📅 2026-07-10
- [ ] review the migration PR 📅 2026-07-10
Copilot reads the note and the contract, then writes both lines in your vault's syntax and stages the diff for you to accept.
You ask Copilot
“Mark the deploy runbook task done and add a follow-up to test in staging next Monday.”
What lands in the file
- [x] update the deploy runbook ✅ 2026-07-07
- [ ] test the runbook in staging 📅 2026-07-13
It completes the first task in place and appends the follow-up. TaskForge shows both the next time it reads the vault.
Copilot's agent edits the files in the folder you opened, and the taskforge MCP server, if you add it, runs locally. No TaskForge account, no cloud copy of your tasks. Your existing sync, iCloud, Dropbox, or Obsidian Sync, moves the edits to your other devices.
Yes, in agent mode. Copilot's agent reads and writes the files in your open VS Code workspace, so with your vault open it edits your markdown task lines directly. Ask it to read taskforge/agents.md first and the tasks come out in your format.
No. Agent mode editing files is enough for most people. Add the taskforge MCP server only if you want Copilot to call typed tools like add_task and complete_task instead of editing lines by hand. VS Code supports MCP, so both work.
No. Any folder opened in VS Code is a workspace, including a plain Obsidian vault. Copilot does not care whether it is a git repo, though versioning your vault with git is a nice safety net for any edit an agent makes.
Yes. Copilot edits the same markdown files TaskForge reads. The app shows the change on that machine right away, and it reaches your phone once your vault sync runs.
It reads taskforge/agents.md, the contract TaskForge writes into your vault. That file describes your exact dialect, so Copilot writes a task your other tools can read instead of a generic one.
Copilot is one agent among many. The AI overview covers the whole picture, and the MCP and CLI pages go deep on each surface.
Plain markdown in your own vault, edited by Copilot. TaskForge is free to download on iPhone, iPad, Mac, and Android.