I don't have to live with the standard
Obsidian served me well until its limits got in the way. On building past them, and what owning that costs.
On 27 July my notes vault held 1,159 PDFs, 510 MB, about 83 per cent of its size. My documents live in kDrive and the vault only links to them, but my home server kept its copy as real files, and from there they had got into Sync, on a plan of 1 GB in all that refused files over 5 MB.
Claude and I set out to exclude them, but the exclusion went into Obsidian’s settings file while Obsidian was running, and Obsidian reads that file only when it starts, so nothing was excluded. The server’s copy was deleted as if it were, and Sync followed the link into kDrive: 1,198 files became 892 before a stop condition caught it. All came back from kDrive’s trash; checked against an earlier backup, nothing was missing.
A good tool, for a long time
Obsidian was the right start in February (post 1): Markdown files in a folder, links between them, and live tables from the notes’ properties (Obsidian’s Bases). Sync kept five devices in step.
Then the limits came, and storage was only the trigger. A sync client on a server hung for three days in August without a word. The tables worked only in the app, so every phone held the whole vault, and history went back one month.
No server for that? I write one
Claude reaches my tools through MCP servers, small connectors with one capability each. Of the seven my desktop app loads, at least two are my own: 44 lines of Python from May that let Claude run commands on the Mac, and a password-vault tool from September that prints only metadata (post 8).
Mail went the same way: in one measured search the stock connector found 2 messages, a direct mailbox search 10,212. My own mail tool, built on 27 July, sat unused for ten days, because Claude’s instructions still pointed at a connector I had switched off.
A reader of my own, in a week
On 3 October, of three ways off Sync that Claude laid out, I chose git plus a reader of my own, a small web app on Yavin*. A headless Claude run built the core that afternoon, 7,021 notes rendered and none failed; a cloud session added the pages.
The first comparison with Obsidian found 69 of 172 table views differing, because of my notes: Obsidian reads task-status == "open" as a subtraction that never matches, so 54 views had shown fewer rows than intended, often none. I had the notes fixed, and the next day all 172 matched.
On 4 October the reader’s home page became my morning cockpit, and Claude’s stand-up instructions shrank from 847 lines to 330. On 8 October the reader was named Helm, and Sync went off everywhere (post 11). I hardly open Obsidian now, except to edit long texts.
What owning it costs
Then I cleared out: on 7 October all 27 old scheduled Claude tasks were archived and deleted, on 8 October more than a dozen unused repositories went to an attic, and on 9 October one ignore file went into all 48 repositories. That day 12 of 128 regression checks failed, half of them documentation checks: my notes no longer matched the machines.
On 4 October an update reached the server without a restart and broke Helm’s home page. Since 9 October a merge counts as a deploy, because the server pulls every repository hourly, and it waits for my go. That day Yavin* also ran short of memory and stopped answering for thirteen minutes, Helm with it; the next day a read-only copy went live on Bespin*.
The pattern
Standard software comes with standard features, prices and limits. I no longer have to live with them, because building my own has become a cheap option. I ask before I accept a limit, and I own only what I will maintain.
Building got cheap: my code repositories took 23 commits in March, 250 in June, 474 in September and 519 in the first nine days of October. Claude writes much of that code; I decide and review. The upkeep stays with me: every tool is one more thing to update and one more instruction to keep true, and Helm still runs on one machine.
Part 10 of twelve in the series on how I built my AI OS. Start with the preface.
Next: in March the sync was the glue of my whole setup; in October I switched it off. The next post tells that move, with the system by the numbers.
* Host names are changed (here: Yavin, my home server, and Bespin, my VPS). The real ones come from a different saga.
Appendix — for builders
- Write the limit down with its number. Mine: 1 GB in all, 5 MB per file, one month of history. A number can be checked; an annoyance cannot.
- Measure the lock-in before you leave. With no community plugins, only Bases tied me to Obsidian, in 172 plain table views, so a reader of my own was a matter of days.
- Test the copy against the original, and fix the source. Obsidian 1.12 returns a view’s rows from its command line, so Helm was compared view by view; what it cannot evaluate gets a banner, never a wrong table.
- A connector can be small; ask what it must never return. Mine for the shell is 44 lines; my password tool prints metadata only.
- Change the instructions with the tool, and treat a merge as a deploy. My mail tool sat unused for ten days because the rulebook did not know it. Keep a one-command revert, and retire what the new tool replaces that same week.
- What I considered instead: git with Obsidian everywhere and a git app on the phone (less to build, but conflicts solved on a phone, tables still only in the app); tasks in a database (the largest build); Sync for the phone and tablet only. I chose git plus my own reader: reading on the phone mattered most, the views were tables I could rebuild, and the handhelds now hold no copy.
Also published on Kalli Family.