Post

I wanted my AI agent to be able to read my calendar. Turns out the easiest way is to just make a directory of text files. So I built caldir caldir.org 🧵

caldir.orgCaldirYour calendar as a directory

T4T5

@t4t5.com

Caldir is the "file-over-app" philosophy applied to calendars. One ICS file per event, human-readable filenames, sorted chronologically by default. A standard plaintext format makes your events trivial to read and composable with other unix tools.

6/3/26, 5:14 pm0 reposts0 likes

T4T5

@t4t5.com

6 Mar

Caldir's sync mechanism works similarly to git. You push and pull changes to keep your local directory in sync with a remote (can be Google Calendar, iCloud Calendar, CalDav, or any other cloud calendar)

T4T5

@t4t5.com

6 Mar

The caldir-core package is intentionally simple and extensible. By tackling the basic problem of storing and syncing events, it makes it easy for anyone to experiment with UIs and workflows on top of it. TUIs like khal should already support Caldir quite well. GUIs are coming soon!

T4T5

@t4t5.com

6 Mar

After years of big-tech dependency I feel like I'm finally able to break free from proprietary walled-garden apps, and I absolutely love it. Moving your data into portable, plaintext file formats keeps you from being trapped in digital ecosystems that you can't control. 👉 github.com/t4t5/caldir

github.comGitHub - t4t5/caldir: "file over app" for calendars"file over app" for calendars. Contribute to t4t5/caldir development by creating an account on GitHub.