Send lines from any note to your own OpenTodo server as tasks that link back to the note, and keep a folder of task files in two-way sync. Works offline and with encrypted accounts.
Send a line, or a selection of lines, from any note to your own OpenTodo server as tasks, and keep a folder of task files in two-way sync with it. Each task sent links back to the note it came from, and the line gets a link to the task. It works on Obsidian for desktop and mobile, offline, and with end-to-end encrypted accounts.
- [ ] Renew passport 📅 2026-11-05 ⏫ #errand) is read like the Tasks plugin and OpenTodo's vault: due date, start date, priority, #tags as labels, [time:: 09:00], [estimate:: 45m], [deadline:: …]. Any other line is read like OpenTodo's quick add: Call the plumber tomorrow 9am p2 #Home @errand.[opentodo:: https://your-server/?task=…] (or, by setting, is ticked or removed). "Undo" in the notice for ten seconds puts the line back and moves the task to OpenTodo's Trash. A line that already carries the link is never sent twice.obsidian://open?vault=…&file=…, so the chip on the task opens the note. Renaming or moving the note in Obsidian updates the links; "Fix task links in this note" repairs links after a rename made elsewhere.OpenTodo/) in two-way sync with OpenTodo, with the files and rules of ot vault: one file per project, one Tasks line per task, .opentodo/state.json. It syncs when the plugin starts, a second after a file in the folder changes, every 30 seconds while Obsidian is in front and with "Sync folder now"; never in the background. A folder that Obsidian Sync, iCloud or git copies to several devices is synced by one of them; the others show which and offer "Take over syncing here".full API token because it writes tasks: a read token cannot write, and an agent token is meant for AI assistants and labels changes as theirs.todo.example.com) and paste the token, then pick Connect.The token is kept in Obsidian's storage on this device, never in the plugin's data.json inside the vault, so a vault synced to another device (Obsidian Sync, iCloud, git) does not carry it: connect each device with its own token, and revoke one without touching the others. Disconnect removes the token, the cached projects and labels and any remembered key from the device.
The plugin makes no request until you connect it. It then connects only to the OpenTodo server you configure, through Obsidian's own request function, for these routes: /healthz (the server's version), /api/v1/me, /api/v1/projects, /api/v1/labels, /api/v1/tasks/{id} (the project of a linked task, after a rename on an encrypted account), /api/v1/encryption/keys (the wrapped key record of an encrypted account) and /api/v1/sync (sending tasks, and the folder sync's exchange as a vault device vault:<id>). Addresses must be https; plain http is accepted only for this device and private networks, after a warning. With folder sync on, it reads and writes only the folder you pick (and its .opentodo/ state); it never touches files outside the vault.
It collects nothing: no analytics, no crash reports, no update check of its own (Obsidian updates plugins), no other destination. What it sends to your server is the tasks you send, the changes to their links and, with folder sync on, the changes made in the synced folder.
main.js, manifest.json and styles.css from the latest release of OpenTodoApp/obsidian-opentodo into <vault>/.obsidian/plugins/opentodo/, then enable "OpenTodo" in Settings → Community plugins.OpenTodoApp/obsidian-opentodo.The guide is docs/obsidian.md in the OpenTodo repository.
The source lives in obsidian/ of the OpenTodo repository. Each release copies it into the release repository, OpenTodoApp/obsidian-opentodo, together with the shared web modules it bundles (web/src/…), in the same layout: npm ci && npm run build there rebuilds main.js and styles.css byte for byte. Report issues in either repository; changes are made in OpenTodo. The plugin bundles OpenTodo's own quick-add parser (web/src/lib/nlp), envelope code (web/src/lib/crypto.ts, web/src/lib/e2eeEnvelope.ts) and clock (web/src/lib/hlc.ts), and the TypeScript twin of the vault (src/vault/: the task-line grammar, pinned with internal/vault by internal/vault/testdata/lines.vectors.json, and the sync engine, pinned by the step-by-step sync vectors in internal/vault/testdata/sync/ that go test ./internal/vault -run TestSyncVectors -update writes from the Go engine), so the shared vectors pin the plugin too.
make obsidian: type-check, unit tests (web/'s vitest and happy-dom, with an in-memory obsidian module), and the build of obsidian/dist/, which fails when main.js is over 400 KB (258 KB with the vault engine) or needs a Node or Electron module (Obsidian mobile has neither).make obsidian-e2e: the plugin against bin/opentodo (make build first).make obsidian-review: the checks of Obsidian's community directory on what the release repository receives: it fills a folder as the release does, runs npm ci, npm audit and npm run build there and compares the result with obsidian/dist, type-checks it, and lints it with Obsidian's own rules (eslint-plugin-obsidianmd), failing on any error (review/).cd obsidian && node esbuild.config.mjs --watch, with obsidian/dist linked into a test vault's .obsidian/plugins/opentodo.Dependencies: none at run time. Build time: obsidian (the API's types) and esbuild, pinned in package.json.
The plugin's strings are in locales/ in the six languages OpenTodo ships, follow Obsidian's language and are checked by make i18n-check.
The unit tests and make obsidian-e2e run the engine and the plugin against stand-ins and a real server; these runs on real devices are recorded here (obsidian-vault-sync task 5.3).
| Run | Device and sync service | Date | Result |
|---|---|---|---|
| Turn on, tick a line, see it done in the app; a task made in the app appears within 30 s | iPhone, vault in iCloud Drive | not yet run | |
| A file iCloud has not downloaded is skipped, then merged once it arrives | iPhone, vault in iCloud Drive | not yet run | |
| Same folder on two devices: the second shows "Synced by …", then takes over | Android with Obsidian Sync, and a laptop with ot vault watch |
not yet run | |
A folder moved from ot vault to the plugin and back (--take-over both ways) |
laptop | not yet run |
Every OpenTodo release (v0.20.0) publishes the plugin with the same version (0.20.0): CI builds it from the tag and pushes manifest.json, main.js, styles.css, versions.json, this README, the licence and the source the bundle is built from (obsidian/, web/src/…, package.json, package-lock.json, tsconfig.json) to OpenTodoApp/obsidian-opentodo with a tag equal to the version, and that repository's workflow attaches the three files to a release (mirror/release.yml). The push uses the deploy key in the OBSIDIAN_DEPLOY_KEY secret; without it the job prints the manual steps and succeeds. By hand: node obsidian/scripts/mirror.mjs 0.20.0 <checkout> after make obsidian.
The community directory. Plugins are submitted at community.obsidian.md (Obsidian stopped taking pull requests to obsidianmd/obsidian-releases in May 2026; its community-plugins.json is now copied from the directory). After the first release exists in the release repository, a maintainer signs in there with an Obsidian account linked to GitHub, adds the plugin with the repository https://github.com/OpenTodoApp/obsidian-opentodo and the owner OpenTodoApp, and fixes anything the automated review reports. What to enter, and the checklist, are in store/submission.md. Once published, the directory's entry reads:
{
"id": "opentodo",
"name": "OpenTodo",
"author": "OpenTodo",
"description": "Send lines from any note to your own OpenTodo server as tasks that link back to the note, and keep a folder of task files in two-way sync. Works offline and with encrypted accounts.",
"repo": "OpenTodoApp/obsidian-opentodo"
}
Until it is listed, the plugin installs by hand or with BRAT.
AGPL-3.0-only, like OpenTodo: the plugin bundles OpenTodo's own code. See LICENSE.