TaskForge tasks are plain markdown lines in your Obsidian vault. Any agent that can read and write files can add them, complete them, and move their dates. There is no plugin to install, no API to wire up, no MCP server to run.
Updated July 2026
## This week
- [x] send the invoice to Hartman ✅ 2026-06-10
- [ ] follow up on the printer quote 📅 2026-06-12
- [ ] prep slides for Monday's review ⏫ 📅 2026-06-15
Your agent writes to a markdown file in your vault, and TaskForge reads that same file on each device that has your vault.
It writes or edits a line in a markdown file in your vault, the same way you would in Obsidian. Agents have been trained on markdown since day one; nothing here is new to them.
One line of Obsidian Tasks syntax carries the whole thing: status, dates, priority, recurrence. There is no hidden database to keep in sync with it.
- [ ] book the dentist 🔁 every 6 months 📅 2026-06-20
The app watches your vault for changes. When the file is saved, your lists, widgets, and reminders update on that device, and every other device follows as soon as your vault sync (iCloud, Obsidian Sync, or any file sync you already use) delivers the file.
One prompt, one file edit, and the task list on the phone updates. Recorded in real time.
TaskForge 3.0 will write a short reference into your vault: a visible taskforge/ folder holding agents.md (this vault's exact task syntax, in plain English), schema.json (the same facts, machine readable), and lists.json (your saved lists and where new tasks land). Read agents.md first and an agent will get your dialect right on the first try, whether that means [key:: value] fields, a renamed due date, or TaskNotes YAML under Tasks/. Generation will happen on-device; nothing will leave your vault to produce it. It will ship on by default, with one Settings toggle to remove every file it creates.
## Inline task lines: Dataview format
This vault writes [key:: value] fields. One field is renamed: due is written as deadline.
- [ ] Ship v2 release [deadline:: 2026-07-15] [priority:: high]
- [ ] Water the plants [repeat:: every week]
These are not previews of a planned integration. External edits to vault files are how TaskForge has always worked, so every recipe below runs on the app you can download right now.
In a terminal, with your vault as the working directory.
The prompt
“Read inbox.md and turn every unanswered question into a task in tasks/this-week.md, due Friday.”
What lands in the file
- [ ] answer Priya's question about export formats 📅 2026-06-12
- [ ] confirm the venue headcount with Sam 📅 2026-06-12
Claude Code edits the file directly. On that machine, the tasks are in TaskForge the moment the file saves; they reach your phone with the next vault sync.
With ChatGPT reaching your vault through an MCP server or a desktop client that has folder access.
The prompt
“Read meeting-notes.md and add every action item to tasks/this-week.md, each due this Friday.”
What lands in the file
- [ ] send the signed contract to legal 📅 2026-06-12
- [ ] book the venue deposit 📅 2026-06-12
ChatGPT writes the lines straight into the file. TaskForge shows them the moment it reads the vault, and they reach your phone with the next sync. No connector to set up on the TaskForge side.
With Claude Desktop given access to your vault folder.
The prompt
“What’s overdue in my vault? Push anything that can wait to next Monday, and raise the priority on what can’t.”
What lands in the file
- [ ] renew the domain 📅 2026-06-15
- [ ] pay the contractor invoice ⏫ 📅 2026-06-11
The dates change inside the same markdown lines, so the reschedule shows up in TaskForge and in Obsidian at the same moment.
A scheduled script, a local model, an agent framework. The bar is appending a line of text.
The prompt
“Every weekday at 5pm, read today’s meeting note and add the follow-ups to tasks/follow-ups.md.”
What lands in the file
- [ ] send Marta the revised timeline ➕ 2026-06-11 📅 2026-06-12
Tasks filed while you commute, ready on your phone after the next vault sync. The agent never knew TaskForge existed; it just wrote markdown.
With your vault opened as a folder in Cursor.
The prompt
“Add a task for the client review packet, due Thursday, high priority.”
What lands in the file
- [ ] client review packet ⏫ 📅 2026-06-18
Cursor reads the existing lines in your vault to match your format, then writes the new one the same way. No plugin, no connector.
The recipes above work with any file-capable agent. These walkthroughs go step by step for one tool each, including the exact config to paste and an honest account of what that tool can and cannot reach on your machine.
An API call vanishes into someone’s database. A markdown edit sits in the file, in plain text, where you can open it and check the work.
Vaults are ordinary folders, so git, iCloud, or Obsidian Sync already version them. An agent’s bad afternoon is one revert away.
There is nothing to authenticate against and nothing to throttle. The agent writes at disk speed, offline included.
Agents will keep changing; markdown will not. Whatever you switch to next can read the same files it finds in the same folder, going back years.
If your tasks already live in an Obsidian vault in Tasks-plugin syntax, there is nothing to set up. Point an agent at the vault and point TaskForge at the same vault; both are reading the files you already have.
TaskForge. Its tasks are plain markdown lines in your vault, so Claude, ChatGPT, Cursor, or any file-capable agent can manage them with no plugin and no API. On top of the same files your agent edits, you get native apps, home screen widgets, and reminders on iPhone, iPad, Mac, and Android.
Yes. If you run an MCP server that can edit vault files, an AI client like Claude or Cursor can add and update tasks through it, and TaskForge shows those changes because it watches the vault. You do not have to run one though; any agent with plain file access works the same way.
Yes. TaskForge tasks are plain markdown lines in files on disk, so any AI agent that can edit files can add, complete, and reschedule tasks. TaskForge picks up the file changes automatically.
Give Claude Code or Claude Desktop access to your Obsidian vault folder and ask it to add or edit tasks in your markdown files. TaskForge picks the changes up immediately on that device, and they show up on your phone, tablet, and desktop once your vault syncs (iCloud, Obsidian Sync, or any file sync you already use). No connector or setup step is involved.
Give ChatGPT a way to write to your vault, either an MCP server that edits Obsidian files or a desktop client with folder access, and ask it to add or change tasks in your markdown. TaskForge reads those same files, so the tasks show up on your phone and desktop after your vault syncs. There is nothing to connect on the TaskForge side.
Yes. Open your Obsidian vault as a folder in Cursor and ask it to edit your task files. Cursor writes the markdown line, and TaskForge picks it up the next time it reads the vault. It is the same file either way, so there is no extra setup.
It does not need one. The integration surface is the markdown file itself: agents read and write the same files TaskForge reads and writes. That means it works with every file-capable agent, not only the ones someone built a connector for.
It is a task manager that stores every task as a line of markdown in a plain text file instead of in a private database. Because models are trained on markdown, agents can manage those tasks with ordinary file edits. TaskForge is built this way, using the Obsidian Tasks format.
Yes. TaskForge re-reads your vault when it opens and watches it for changes while running. Tasks added overnight by a script or an agent are there when you open the app.
Safer than letting it use an API, because every change is visible and reversible. The edits are plain text you can diff, and vault folders are easy to version with git, iCloud, or Obsidian Sync.
Yes. ChatGPT with file access, local models, cron scripts, and agent frameworks all qualify; the only requirement is the ability to write a text file. TaskForge does not know or care which tool made the edit.
It is a short reference file that TaskForge 3.0 will generate in your vault, describing that vault's exact task syntax: field names, status symbols, the TaskNotes folder, and real example lines. Since your dialect is configurable, agents.md will always match your current Settings, not a generic default, with a toggle in Settings > AI & Agents to turn it off. TaskForge 3.0 has not shipped yet; until it does, an agent with vault access can already read and match your existing task lines directly.
No, not for the basics, and that is true today: point any file-capable agent at your vault folder and it can already read and write your task lines, matching the format it finds. TaskForge 3.0 will go further and generate taskforge/agents.md and schema.json automatically the moment you have a vault, so an agent no longer has to infer your syntax from examples. Cursor will still need one copy-paste .cursor/rules snippet pointing at agents.md, since Cursor does not auto-discover in-vault files.
Plain markdown in your own vault. TaskForge is free to download on iPhone, iPad, Mac, and Android.
Get Free - iOS & Mac 
Get Free - Android