Skip to main content

Claude Code can read and write your tasks today

Claude Code lives in the terminal and edits files, so it can already open your Obsidian vault and match the markdown lines it finds. TaskForge 3.0 adds a taskforge/agents.md file to the vault that spells out your exact format, so once that ships, pointing Claude Code at the vault gets it right from the first line instead of pattern-matching your syntax. There is no plugin, no API, and no MCP server required for the basics.

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.

Start a session in your vault

Claude Code works from a working directory. Make that directory your vault, and everything it needs is already on disk.

  1. Generate the contract once

    Open your vault in TaskForge 3.0 or later, then Settings, AI & Agents, and keep "Generate agent files" on. That writes taskforge/agents.md and taskforge/schema.json into the vault. If you change a status symbol or date format later, TaskForge rewrites them so they never drift.

  2. Launch Claude Code in the vault

    From a terminal, change into your vault folder and start Claude Code there. The vault is now its working directory, so every file, including the taskforge/ contract, is in reach.

    cd ~/Documents/MyVault
    claude
    Any vault folder works, whether it syncs through iCloud, Dropbox, or Obsidian Sync.
  3. Tell it to read the contract first

    A one-line instruction keeps every task it writes in your format: ask it to read taskforge/agents.md before adding or editing tasks. Drop the same line into a CLAUDE.md at the vault root and you never have to repeat it.

    Read taskforge/agents.md, then add every action item
    from today's daily note to tasks/this-week.md, due Friday.
    Claude Code opens the guide, matches your dialect, and writes the lines.
  4. Prefer tools over free-form edits? Add the MCP server

    Claude Code can also speak MCP. Register the taskforge server and it gets the same typed add, query, and complete tools the desktop app uses, with structured errors it can self-correct against.

    claude mcp add taskforge -- npx -y taskforge-md mcp --stdio
    Set TASKFORGE_VAULT if you run it from outside the vault folder.

What the contract tells it

The taskforge/ folder is the whole reason Claude Code gets your tasks right on the first try. It reads these files like any other source in the working tree, so a renamed "due" field or a custom "Waiting" status is a fact it looks up, not a guess it makes.

taskforge/agents.md The plain-language guide: your checkbox dialect, status symbols, renamed fields, date format, and where new tasks go.
taskforge/schema.json The same rules as structured JSON, for when Claude Code would rather parse than read prose.
taskforge/lists.json Your saved lists and their add-recipes, so "file this under Errands" ends up in the right note.

A session, start to finish

This is the workflow, not a demo. Claude Code edits the file on disk; TaskForge shows the result the moment the app reads the vault, and your phone follows on the next sync.

You type

“Read inbox.md and turn every unanswered question into a task in tasks/this-week.md, each due Friday.”

What Claude Code writes

- [ ] answer Priya's question about export formats 📅 2026-07-10

- [ ] confirm the venue headcount with Sam 📅 2026-07-10

It reads the note, writes two lines in your vault's syntax, and tells you what it added. No copy-paste, no format guessing.

You type

“Anything in tasks/ tagged #blocked that is more than a week old? Bump it to high priority.”

What Claude Code writes

- [ ] waiting on legal sign-off ⏫ #blocked 📅 2026-07-02

Claude Code greps your task files, finds the stale ones, and rewrites the priority marker in place. The edit is a plain diff you can review before you commit it.

Local files, reviewable edits

Claude Code runs on your machine and only touches the files in its working directory. Because your tasks are plain text, every change it makes is a diff you can read, and your vault's existing version history, git, iCloud, or Obsidian Sync, means a bad edit is one revert away. No TaskForge account, no cloud.

Questions people ask

Does Claude Code need the MCP server to manage tasks?

No. For the basics it just edits files. Open your vault as the working directory, tell it to read taskforge/agents.md, and it writes tasks in your format. The MCP server is an option if you would rather it use typed tools than free-form file edits.

How does Claude Code know my task syntax?

It reads taskforge/agents.md, the contract file TaskForge generates in your vault. That file describes your exact dialect, renamed fields, status symbols, and date format, so Claude Code matches them instead of writing a generic task line your other tools cannot read.

Will TaskForge notice tasks Claude Code adds while the app is closed?

Yes. TaskForge re-reads your vault when it opens and watches it for changes while running. Tasks Claude Code writes in an overnight session are there when you next open the app.

Can I keep it from touching the wrong files?

Point it at the task notes you care about, and review the diff before you accept an edit. Since everything is plain text in a folder you already version, nothing it does is hidden or irreversible.

Does this work with a vault on iCloud or Obsidian Sync?

Yes. Claude Code edits the local copy of the vault; whatever sync you already use carries the changes to your phone and other machines, the same way it carries edits you make in Obsidian.

Related setups

Claude Code is one way in. The AI overview covers the whole picture, and the CLI and MCP pages go deep on the terminal and tool-driven surfaces.

Your terminal, your vault, your tasks.

Plain markdown Claude Code can read and write. TaskForge is free to download on iPhone, iPad, Mac, and Android.