Skip to main content
Every item in Wrixton that has a due date can appear in your calendar app. You have two options: export a one-shot .ics file for a point-in-time snapshot, or subscribe to a live feed URL that your calendar app re-polls automatically so new items, snoozed due dates, and completed items always stay current.

​
One-shot export with track ics

Generate an .ics file from the command line whenever you need a fresh snapshot: 
# Print the VCALENDAR text to stdout
track ics

# Write directly to a file
track ics --out track.ics

# Include done and canceled items as well as active ones
track ics --all
Each item with a due date becomes an all-day event. Chores use their rolled-forward due date — last_done + every — rather than the raw due field, so the event lands on the day the chore is actually next due. Open the resulting file in any calendar app that supports .ics import (Apple Calendar, Google Calendar, Outlook, and most others accept it from File → Import or equivalent).

​
Live subscription feed

A one-shot file goes stale as soon as you add or snooze something. For a calendar that stays in sync, subscribe to the hosted feed instead: 
https://projects.wrixton.xyz/api/calendar?key=<your-api-key>
Your calendar app polls this URL on its own schedule (typically every few hours) and updates automatically. The feed is read-only and scoped to your API key — no other user’s items appear, and callers cannot modify your data through it. To include done and canceled items in the subscription feed, append &all=1: 
https://projects.wrixton.xyz/api/calendar?key=<your-api-key>&all=1

​
Using the webcal:// scheme

Most desktop and mobile calendar apps recognise the webcal:// scheme, which tells them to treat the URL as a subscribed calendar and poll it automatically. Swap https for webcal when you paste the URL: 
webcal://projects.wrixton.xyz/api/calendar?key=<your-api-key>
Clicking or tapping a webcal:// link usually opens the right dialog in the system calendar app directly.

​
Adding the feed in common calendar apps

The exact steps vary by app, but the general pattern is the same everywhere:
1

Copy your subscribe URL

In the web UI, go to Settings and click the copy button next to the calendar URL. Or construct it manually using your API key from ~/.track/config.toml.
2

Open your calendar app's subscription dialog

Look for Add Subscribed Calendar, Add Internet Calendar, Subscribe to Calendar, or equivalent in your app’s account or calendar settings.
3

Paste the URL

Paste the webcal:// or https:// URL you copied. Most apps accept both.
4

Confirm and set a refresh interval

Give the calendar a name (e.g. “Wrixton”) and choose how often the app should re-poll. Every few hours is usually enough.
The subscription feed is read-only. Changes you make inside your calendar app — renaming events, moving them, deleting them — do not write back to Wrixton. Make edits in the CLI or web UI instead.

​
Getting your API key

Your API key is stored in ~/.track/config.toml after you run track config. You can also copy the full subscribe URL directly from Settings in the web UI, which inserts your key for you automatically.