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.
## 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. Sixteen seconds, no cuts.
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 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.
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.
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.
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.
Plain markdown in your own vault. TaskForge is free to download on iPhone, iPad, Mac, and Android.
Get Free - iOS & Mac 
Get Free - Android