Vault sync improvements for the Obsidian plugin
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the proposal and task list in openspec/changes/obsidian-vault-sync/. The current sync lives in the ot vault watch Go CLI command; understand its two-way sync logic. Done means Obsidian mobile edits sync to OpenTodo without a desktop Go binary, per the spec's acceptance criteria.
Written by the indexing model from the issue text.
Description
Roadmap: 0.20 Everywhere · OpenSpec change: obsidian-vault-sync
ot vault watch keeps a folder of Obsidian Tasks files in two-way sync with OpenTodo, but only where a Go binary can run. Obsidian on iPhone, iPad and Android cannot run it (research §3.2: "Obsidian Mobile cannot execute a background Go CLI binary"), so people who keep their notes only on a phone, or who want their phone's edits to reach OpenTodo without a desktop running ot, have no vault sync at all. This is the third of the three changes the roadmap item obsidian-plugin (0.20 "Everywhere", size L) is split into: obsidian-origin (the link-back kind), obsidian-plugin (connect, send a line, distribution), and this one, which puts the vault sync inside the plugin.
The proposal, design decisions, spec changes and the task list are in openspec/changes/obsidian-vault-sync/. Comments and ideas are welcome here before implementation starts.
🤖 Generated with Claude Code
- Dominant language
- Go
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pixari/OpenTodo
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 54/100
-
enhancement needs design
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Add Japanese (日本語)Openenhancement needs design
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
WriterSetTimes: the UTIME_NOW check fails when the kernel uses its coarse clockPossibly taken @JakeChampion claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JakeChampion/lang#14224 ·
Maintainers usually reply within 1 day
-
agent-butler-finding bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jordansmall/spindrift#6391 ·
Maintainers usually reply within 1 day
-
common.Retry: data race on the shared response/err variables when the request context ends mid-attempt (v65.127.0, v65.128.0)Possibly taken @kmohit00 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oracle/oci-go-sdk#676 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SAP/crossplane-provider-btp#1175 ·
Maintainers usually reply within 1 day