Your calendar, in your Omarchy bar. A month view with your real events on it, a bar that tells you what is coming before it starts, and a form to create or edit events without leaving the desktop.
Where your events come from:
- Google Calendar, read and write. See Sync your Google Calendar
- iCloud, Nextcloud, Fastmail or any other CalDAV server, read and write (community-maintained). See Sync from iCloud or CalDAV
- Any iCal feed, read only. See Sync from the secret iCal address
- Anything else: the widget reads a plain JSON file, so caldir, khal or vdirsyncer work just as well. See Sync from caldir and Use another source
It replaces the built-in clock rather than sitting beside it, so you keep one icon. Left click opens a month calendar with your real events on it. When something is close, the bar itself stops being just a clock and tells you:
The clock stays. This widget takes the desktop clock's place, so trading the time away for an event title would be a downgrade you pay for all day.
-
Three columns. The month grid you know on the left, the day's agenda in the middle, and the selected event's details on the right. The details column only opens when you click something
-
Your layout. Settings › Panel picks a preset or turns each block on or off: year progress, the shortcut legend (a keyboard icon beside the settings button), quick add, the next up card and the upcoming days. Standard shows them all. Minimal is one narrow column, the agenda under the calendar
-
Nothing cut off. Titles wrap instead of trailing off in an ellipsis
-
Deadlines and tasks look like what they are. Titles starting with
DEADLINE:/PRAZO:/Due:get a badge and come first. Rows from a task calendar (Todoist, Google Tasks) get a circle, and done ones (✓ …) are struck through -
A meeting button on every meeting, whatever the time. It turns into a filled Join from 15 minutes before the start. Links are found in Google's conference data, and also in the location or description of an invitation forwarded by email (Meet, Zoom, Teams, Webex, Jitsi, Whereby)
-
Next up card: what is next today, with a countdown and Join
-
Upcoming days under the selected day, so the week is one glance away
-
Quick add in plain English or Portuguese:
call with Ana tomorrow 2pm for 45m,dentista sexta às 15h,gym every monday 6pm,trip friday to sunday,call in 20 min. You see the parsed date and the words it understood before you press Enter, and the "?" lists what it reads. A day with no time is all day, and no day and no time is the next half hour. An email address adds a guest, and then Enter opens the form, so you check the address before anyone gets an invitation. Read-only sources open Google Calendar with the event filled in, except CalDAV, whose events are not in Google: with writing off, Enter says so and keeps the text -
Details on click: full title, when, Join, directions, description, reminder, and buttons to edit the event (writable calendars), open it in Google or delete it
-
Create, edit and delete from the panel, with a form like Google's: date picker, times in 15-minute steps, repeat, guests with suggestions, Google Meet, notifications, colour. Off by default, see Create and edit events
-
The bar escalates as a meeting nears: a quiet title, then the accent colour and a Join chip, then "Now" in the urgent colour until it ends, or for its first 2 minutes if you prefer. When the next event is due, it takes over, unless you keep the current one. A
+1shows when two things start at once. Middle click joins a Google Meet, Zoom, Teams, Webex, meet.jit.si or Whereby link. The sender of an invitation sets its link, so any other link opens the panel, where you see it before you open it -
Settings in four sections: Panel, Bar, Calendars and General, one at a time, each setting with a line that says what it does
-
Desktop reminders from your Google notification times (10 minutes for meetings without one). Clicking one opens the panel, also from the notification history. A shell reload never repeats them. See Reminders
-
Keyboard first, see Keyboard
-
English and Portuguese, following your locale or set by hand
-
Per-calendar visibility, week start, countdown lead time and a 24 h or 12 h time format
-
Google's working-location markers hidden by default, declined invitations struck through
-
Everything the built-in Omarchy clock does: label formats, right click to cycle them, the year and life progress bars if you want them back
-
Theme aware, light themes included, because it is a fork of the built-in clock
-
No Google Cloud project needed if you read your calendars from their secret iCal address (read only), through Evolution Data Server, caldir or CalDAV (all three community-maintained), or from any other source that writes the events file
Omarchy 4 with Quickshell. Google Calendar is optional, see Use another source. A Google Cloud project is optional too, see Sync from the secret iCal address or Sync without a Google Cloud project.
omarchy plugin add https://github.com/tmn73/omarchy-calendar.git --enableThis widget replaces the built-in clock in-place (clonedFrom: "omarchy.clock"). Installing with --enable automatically swaps omarchy.clock with this widget in your bar layout, preserving your existing formats and position.
In ~/.config/omarchy/shell.json, point bar.centerAnchor at tmn73.calendar:
{
"bar": {
"centerAnchor": "tmn73.calendar"
}
}Then:
omarchy restart shellInstalling is not the whole job. At this point you have a working clock and an empty calendar, because nothing is feeding it yet. Connect Google Calendar below, or point any other source at the file. The widget says as much when you open it, with the command to run.
Only need to read your calendar?
setup --icsskips Google Cloud and reads your calendar's secret iCal address instead. You cannot edit events from the panel that way. See Sync from the secret iCal address.
~/.config/omarchy/plugins/tmn73.calendar/sync/setupRun it in a real terminal. It pauses for input, and four steps have to be done by hand in the Google Cloud Console.
You need your own Google OAuth client. There is no shared one, and that is
not laziness. calendar.readonly is a Google sensitive scope, so a publicly
distributed client would need Google verification and is capped at 100 users
until it gets it. This is exactly why gcalcli's shared token is currently
restricted. Every user brings their own credentials.
The script automates what has an API:
- an isolated
gcloudconfiguration, so your other projects are untouched - creating the Google Cloud project
- enabling the Calendar API
- installing the downloaded client secret, with the right permissions
- the scoped login, and verifying the scope was actually granted
- the systemd timer
It stops and waits for the four things Google exposes no API for: the consent screen, declaring the calendar scope, publishing the app, and creating the Desktop OAuth client. Each one prints the exact URL and the exact values.
Two of those steps are traps, and the script says so at the time:
- Declaring the scope under Data Access is not optional. A scope that is
not declared there is never offered on the consent screen, so there is no box
to tick, Google silently grants only your email address, and every sync then
fails with
403 insufficient scopeswhile the login reports success. - Publish the app. While it sits in Testing, Google expires refresh tokens after seven days and your calendar quietly stops updating. Unverified production apps show a one time warning screen and then work indefinitely.
When it finishes, events land in ~/.local/state/omarchy/calendar-events.json
every five minutes and the widget picks them up without a restart.
Off by default. Turn it on and the panel gets a + next to the day's
agenda (or press n), and a pencil and a trash can when you hover one of
your own events.
It needs one more Google scope, calendar.events. That scope can see and
edit events. It cannot change sharing or delete a calendar.
New setup: answer yes when sync/setup asks, or run sync/setup --write.
Already set up:
-
In the Cloud Console, under Data Access, add
calendar.eventsnext tocalendar.readonly. -
Log in again with both scopes. The
rmdrops the cached token, which gws would keep serving without the new scope:rm -f ~/.config/gws-omarchy-calendar/token_cache.json GOOGLE_WORKSPACE_CLI_CONFIG_DIR=~/.config/gws-omarchy-calendar gws auth login \ --scopes https://www.googleapis.com/auth/calendar.readonly,https://www.googleapis.com/auth/calendar.events
-
Set
"write": truein~/.config/omarchy/calendar-sync.json.
Only calendars you own or can edit get the pencil and the trash can. The
form follows Google's: start and end dates with a date picker, times in
15-minute steps in your eventTimeFormat, all day, repeat, guests, Google
Meet, location and description. Under "More options": notifications, busy
or free, visibility, colour and guest permissions.
With guests, the panel asks whether to send invitation emails. For a recurring event, it asks whether the change is for this event or all events. To move an event to another calendar, use Google Calendar. A repeat rule the menu cannot show, or a notification it has no entry for, stays as it is unless you pick another one.
The EDS backend cannot write yet, so the panel shows none of this there.
A save goes straight to the Google Calendar API over HTTPS, with a token
made from the sign-in gws already holds. The event, its description and its
guests never appear in the arguments of a process, so the other users of
the machine cannot see them through ps. Reading your calendar still goes
through gws.
The least setup of all, and read only. Google publishes every calendar at a private iCal address, so the sync can read that instead: no Google Cloud project, no OAuth client, no consent screen, no Evolution. Suggested in #32.
~/.config/omarchy/plugins/tmn73.calendar/sync/setup --icsIt asks for the address (Google Calendar on the web: Settings > your calendar >
Integrate calendar > Secret address in iCal format), runs a test sync, then
writes it to ~/.config/omarchy/calendar-sync.json with mode 600 and installs
the timer. If the test sync fails, your current config stays as it was. Or by
hand:
{
"backend": "ics",
"identity": "you@example.com",
"ics": [
{ "url": "https://calendar.google.com/calendar/ical/.../private-.../basic.ics" },
{ "url": "webcal://example.com/other.ics", "name": "Other", "color": "#33b679" }
]
}Needs python-icalendar and python-recurring-ical-events (the setup installs
them). Any https or webcal iCal feed works, not only Google's.
The trade: no creating or editing events, and Google refreshes the feed on its
own schedule so a change can take a while to show up. The feed carries no link
to an event, so for a Google feed the sync builds one from the event's UID and
the calendar id in the address; an occurrence of a repeating event opens the
series, and an event from any other feed opens nothing. Descriptions and
pop-up reminders (VALARM) come through. Treat the address as a password;
reset it in Google Calendar if it leaks.
To go back to the Google Cloud sync, run setup again without --ics.
Community-maintained. The author does not run Evolution Data Server, so the people who use this backend are the ones who test it. When you open an issue about it, say that you are on the EDS backend.
The setup above needs a Google Cloud project because calendar.readonly is a
Google sensitive scope, so a publicly distributed client would need
verification. There is a way around that: read the calendars out of
Evolution Data Server, which signs in with GNOME's already-verified OAuth
client. No project, no consent screen, no scope declaration, no
client_secret.json, and no Testing-mode refresh token expiring after seven
days. Just a browser sign-in.
The trade is roughly 20 packages, and a GUI is needed once to sign in.
sudo pacman -S evolution-data-server evolutionDescribe the account in ~/.config/evolution/sources/google.source:
[Data Source]
DisplayName=Google (you@example.com)
Enabled=true
Parent=
[Collection]
BackendName=google
Identity=you@example.com
CalendarEnabled=true
ContactsEnabled=false
MailEnabled=false
[Authentication]
Method=Google
User=you@example.com
Host=www.google.com
RememberPassword=trueWriting that by hand is not laziness either. Evolution's Collection Account wizard resolves a custom Workspace domain to Google's mail servers and then asks for a password to discover CalDAV, rather than reusing the Google OAuth2 provider it already ships. It offers no calendar at all, and the wizard is a dead end. The file skips it.
Then sign in once:
evolution -c calendarIts credential prompter opens Google's sign-in, EDS discovers the calendars over CalDAV, and the refresh token goes to your keyring. Evolution is not needed again unless Google later wants a re-auth and needs a window to ask in; the data server keeps running headless.
Finally point the sync at it in ~/.config/omarchy/calendar-sync.json:
{
"backend": "eds",
"identity": "you@example.com"
}identity is the address whose invitation answers count as yours, which is
what makes "hide declined events" work. Leave it out and responseStatus is
left unset rather than guessed from the first attendee.
The same systemd timer drives it, calendars.include/exclude and window
behave identically, and the file written is the same contract, so switching
backends changes nothing the widget can see.
One known limit: clicking an event opens nothing on this backend, because CalDAV does not carry Google's link to the event.
Community-maintained. The author does not run caldir, so the people who use this backend are the ones who test it. When you open an issue about it, say that you are on the caldir backend.
Already using caldir? It keeps your calendars as plain
.ics files and signs in to Google, iCloud or CalDAV itself, so the sync can
read from it with no Google Cloud project and no second sign-in. Read only,
like the iCal address.
{
"backend": "caldir",
"calendars": { "include": ["work", "personal"] }
}include and exclude take caldir's calendar slugs (caldir calendars) or
names. Without them you get every calendar caldir syncs, which for a Google
Workspace account often means coworkers' calendars and meeting rooms too.
caldir's default_calendar counts as your primary one when the same event
shows up in two calendars.
The sync runs caldir pull before reading. If something else already keeps
caldir up to date, set "caldirPull": false and it only reads the local files.
As with gws, a systemd user service does not see your shell PATH, so when
caldir lives somewhere unusual set "caldirPath" to its absolute path.
Community-maintained. The author does not use iCloud or another CalDAV server, so the people who use this backend are the ones who test it. When you open an issue about it, say that you are on the CalDAV backend.
Reads and writes iCloud, Nextcloud, Fastmail or any other CalDAV server directly, with a username and an app password. No Google Cloud project, no Evolution, no second program. An event made or changed in the panel shows up on your phone, and one made on the phone shows up at the next sync.
~/.config/omarchy/plugins/tmn73.calendar/sync/setup --caldavFor iCloud, do not use your Apple ID password: make an app-specific one at account.apple.com under Sign-In and Security
App-Specific Passwords (two-factor authentication must be on), and keep the default address. The username is your Apple ID. For another server, give its CalDAV address, such as
https://your-server/remote.php/dav/for Nextcloud orhttps://caldav.fastmail.com/for Fastmail.
The setup runs a test sync first. Only when it passes does it keep the
password in your keyring with secret-tool, under the server and the
username, then write ~/.config/omarchy/calendar-sync.json and install the
timer. If the test fails, your current config and its password stay as they
were.
Or by hand:
{
"backend": "caldav",
"write": true,
"identity": "you@icloud.com",
"caldav": {
"url": "https://caldav.icloud.com/",
"username": "you@icloud.com",
"passwordCommand": ["secret-tool", "lookup", "service", "omarchy-calendar-caldav-account", "url", "https://caldav.icloud.com/", "username", "you@icloud.com"]
}
}passwordCommand is any command that prints the password, such as
["op", "read", "op://Private/iCloud/app-password"] for 1Password or
["pass", "show", "icloud-caldav"]; it runs without a shell. "password"
works in its place, in a file you keep at mode 600. The password goes to
the server in url, and to the servers it names for your calendars only
when they are on the same host or domain over https (iCloud keeps each
account's on a host of its own, such as p42-caldav.icloud.com). Plain
http is only for a url on this machine, and then only to that address. A
request that a redirect would take anywhere else is refused. caldav also takes a
list of accounts. Calendar ids are the calendars' URLs, so
calendars.include/exclude take those or the names. iCloud's Reminders
lists are left out, and so are calendars shared with you read only, from
the edit buttons. The calendar iCloud uses for new events comes first.
Needs python-icalendar and python-recurring-ical-events (the setup installs
them). What the form offers and CalDAV cannot store is left out of the form
for these calendars: Google Meet, Google's event colours, and guests. A
CalDAV server sends invitations itself, so the panel could not honour "don't
send", and it does not add guests; invite them on your phone or Mac. An event
you were invited to keeps its guests when you edit it. "Default"
notifications mean none, since CalDAV has no calendar default. Clicking an
event opens nothing, because CalDAV carries no link to it.
Each save sends the event with the version the panel read, so a change made on another device in the meantime is refused rather than overwritten. Wait for the next sync, then try again.
The widget has no idea Google exists. It reads one file and renders it:
~/.local/state/omarchy/calendar-events.json
Anything that writes that file works: khal, vdirsyncer, Nextcloud, an ICS feed,
a shell script, a cron job of your own. No credentials, no network, no gws.
{
"version": 1,
"syncedAt": "2026-08-10T16:42:00+00:00",
"source": "whatever produced this",
"events": [
{
"id": "any-stable-id",
"calendarId": "work@example.com",
"calendarName": "Work",
"color": "#f83a22",
"dateKey": "2026-08-10",
"start": "2026-08-10T19:15:00-05:00",
"end": "2026-08-10T20:15:00-05:00",
"allDay": false,
"title": "Tax filing",
"location": ""
}
]
}These extra fields are optional. Omit them and everything still works:
| Field | Effect |
|---|---|
meetingUrl |
Shows the Join button around the event's time. Must be https, anything else is dropped |
eventUrl |
Opens the event in its calendar. Must be https |
eventType |
workingLocation is hidden by default, outOfOffice is labelled |
responseStatus |
declined is struck through, and can be hidden entirely |
description |
Shown in the event details. Plain text only, never rendered as markup; the bundled sync strips HTML, decodes entities and caps it at 1500 characters |
reminders |
List of whole minutes before the start, e.g. [10, 60], at which to raise a desktop notification. [] or absent means none given. The bundled sync takes Google's pop-up reminders (the calendar's defaults when the event uses them) or an iCal feed's DISPLAY/AUDIO alarms counted from the start; e-mail reminders are left out |
A top-level writableCalendars list (id, name, color) turns on the
panel's edit buttons for those calendars. An optional lacks list on each
(guests, meet, color) leaves those fields out of the form. Only the bundled sync should write
it: the panel sends its edits to the bundled event command, not to your writer.
Rules a writer has to follow:
dateKeyisYYYY-MM-DDin local time, and it is what the grid keys on.- A multi-day event is emitted once per day it covers, each row with its own
dateKey. Those rows share anid, so the unique key for a row isid + dateKey. allDayevents are excluded from the countdown, since counting down to midnight tells you nothing.- Write the file atomically, temp file then rename. The widget watches it.
- Unknown fields are ignored, so you can add your own.
tests/fixtures/calendar-events.json is a valid two-event file to start from.
Writers other people have built:
- Thunderbird by @marijn070. A Nushell script that reads Thunderbird's local calendar, so every source you already aggregate in Thunderbird shows up in the widget.
With the panel open:
| Key | Does |
|---|---|
← → / ↑ ↓ |
Previous / next day, previous / next week |
[ ] |
Previous / next month ({ } for years) |
t |
Today |
j k |
Next / previous item of the selected day |
Enter |
Show or hide the selected item's details |
n |
Quick add |
e |
Edit the selected event |
m |
Join the selected meeting, else the next one |
o |
Open the selected event in Google |
w |
Toggle the week start |
Esc |
Back out one step: dialog, form, details, selection, then the panel |
omarchy-shell tmn73.calendar join joins the next meeting from anywhere, for
a Hyprland binding. Like the middle click, it opens only a known video
service and shows any other link in the panel.
The bar widget sends them, so they work with the panel closed.
- When: at the times set in Google (popup reminders). A meeting with a link but no reminder gets one 10 minutes before. All-day events only remind when they have their own reminder, counted back from midnight like Google does
- What they say: "Event in 10 min", the time, and the video service when there is one. Omarchy passes the text of every notification through process arguments, which other users of the computer can read, so by default a reminder names no event and no place
- Event names: the Bar settings can turn them on ("Name the event in reminders"). The reminder then shows the title and the place, and clicking it joins the call or opens the event. Only turn it on when nobody else uses the computer
- Clicking one: opens the panel
- Late or repeated: if the laptop slept through a reminder, it still fires on wake, as long as the event has not started. Reminders already sent are remembered for the session, so restarting the shell never repeats one
- Snooze: for 15 minutes after a reminder, the next-up card and the event's details offer "Snooze 5 min"
- Turning them off: set
"reminders": falsein the widget's entry inshell.json
Click the clock, then the gear icon in the panel header.
One section at a time, from the menu on the left. Every setting has a line under it that says what it does.
| Section | What it holds |
|---|---|
| Panel | A preset: Minimal or Standard. Where the agenda sits: beside or under the calendar. A switch for each block: year and life progress, shortcut legend, quick add, next event card, upcoming days |
| Bar | Your own clock format, with a live preview, on one line or one per line of the clock on a vertical bar. It joins the formats the format button goes through (right click by default), and a format that is already one of them is pointed out. A format written by hand in shell.json is kept the same way on the first right click. How early the bar announces what is next: never, 5, 15, 30 or 60 minutes. How many characters of the title it shows before the ellipsis. How long "Now" stays on during an event, and whether the next event takes over. Desktop reminders, and whether they name the event. A preview puts your choices in words. What each mouse button does on the clock: open the panel, join the meeting or change the format, with at least one button on the panel |
| Calendars | Show or hide each calendar, with its event count. The list comes from your own events, so it needs no configuration. Then working location events (Google's work-from-home markers, hidden by default) and declined invitations (struck through when shown) |
| General | Language: Automatic follows your locale, or English, or Português. The first day of the week. Whether the panel can create and edit events. Lunar dates under each day, by Vietnamese, Chinese or Korean rules, from 1976 to 2050, off by default. The sync state: event count, source and last sync time |
Event times follow eventTimeFormat in shell.json, a Qt date-time format
such as HH:mm or h:mm AP.
Hiding a calendar is instant and does not change what the sync fetches, so bringing one back does not wait for the next run.
Sync behaviour lives in ~/.config/omarchy/calendar-sync.json:
{
"profile": "~/.config/gws-omarchy-calendar",
"gwsPath": "/absolute/path/to/gws",
"calendars": { "include": [], "exclude": [] },
"window": { "pastDays": 7, "futureDays": 60 }
}include: [] means all of them. Names and ids both match. gwsPath has to be
absolute: a systemd user service does not inherit your shell's PATH, so a
gws installed by bun, cargo or pipx is invisible to it under its bare name.
A calendar source is someone else's server, so one sync holds only so much, whatever it sends:
- 20 MB per answer, and 60 s to receive it. An error answer is read up to 64 KB, for its message.
- 10,000 events and 20,000 rows (one row per day an event covers). A calendar that would pass either is skipped with a line in the journal, and the others still sync. So is one whose repeat rules could give more than 10,000 events in a single day, checked before they are expanded.
- 512 MB of heap for the sync and for each change from the panel,
however they start: the timer, the setup's test, the panel or a
terminal. Helpers such as
gwskeep their own limits. - 120 s per sync, 55 s per change from the panel, and 60 s for a helper
such as
gws,caldiror apasswordCommand. The systemd unit addsTimeoutStartSec=180andMemoryMax=512Min case the sync cannot stop itself. The setup copies the unit, so an install from before 0.9.5 gets those two by running the setup again; the limits above apply either way. - The secret iCal address goes over https only, or plain http to this machine, because the address is the password.
journalctl --user -u omarchy-calendar-sync -f
systemctl --user list-timers omarchy-calendar-sync.timer| Symptom | Cause |
|---|---|
403 insufficient scopes |
The calendar scope was never granted. Check gws auth status; if it only lists openid and email, declare the scope under Data Access in the console, then run sync/setup again |
401 invalid_grant |
The refresh token expired. Almost always an app left in Testing, which caps refresh tokens at seven days. Publish it, then log in again |
gws is not installed or not on PATH from the timer, but it works in your terminal |
gwsPath is not absolute. sync/setup writes it for you |
| "Write access not granted" in the event form | The token has no calendar.events scope. See Create and edit events |
refused the sign-in on the CalDAV backend |
For iCloud, the password must be an app-specific one, not your Apple ID password. Revoking it at account.apple.com also ends here. Run sync/setup --caldav again |
redirected to … which gets no password on the CalDAV backend |
The address in url redirects to another server, often from /.well-known/caldav. Put the server's own CalDAV address in url |
passwordCommand did not answer from the timer |
The keyring is locked. It unlocks with your login; check secret-tool lookup service omarchy-calendar-caldav-account url https://caldav.icloud.com/ username you@icloud.com in a terminal |
| "Google refused the change: Shared properties can only be changed by the organizer" | The event is an invitation. Only its organizer can change its title, time or guests. Your own colour, notification and busy or free still change |
cannot parse gws version from the timer, with exec: node: not found |
gwsPath is absolute but points at an npm wrapper that needs node on your shell PATH. With mise, use its shim: ~/.local/share/mise/shims/gws. sync/setup checks this and records the shim for you |
Not in a workspace during setup, or setup says gws is not the Google Workspace CLI |
Another program named gws comes first on your PATH, for example the git workspace helper. Pass the right one: GWS=/absolute/path/to/gws sync/setup |
| The panel says "No calendar synced yet" | The events file does not exist. The sync has never completed |
| The panel says the calendar may be out of date | The file exists but syncedAt is old. Check the journal above |
| An event shows up twice | Two of your calendars both carry it. Hide one in settings. The sync already drops exact duplicates by iCalUID and start time |
The project ID you specified is already in use during setup |
Fixed in 0.1.1. Google Cloud project ids are unique across all of Google, and older versions hardcoded one. Update the plugin, or pass your own: PROJECT_ID=something-unique sync/setup |
| Clicking an event opens your calendar but not the event | The link resolves only for the Google account the sync authenticated as. If your browser opens it in a profile signed into a different account, Google falls back to the calendar root. Route google.com/calendar to the profile holding that account |
| The Join button never appears | It only shows from 15 minutes before the start until 15 minutes after the end, and only when the event has a video link |
| Events are off by a day | Report it. Timezone handling resolves a named IANA zone precisely to avoid this, and there is a regression test for daylight saving transitions |
systemctl --user disable --now omarchy-calendar-sync.timer
rm ~/.config/systemd/user/omarchy-calendar-sync.{service,timer}
systemctl --user daemon-reload
omarchy plugin remove tmn73.calendarThen put omarchy.clock back in shell.json and omarchy restart shell.
Your Google credentials live in the gws profile directory and are not touched
by any of this. Delete that directory to revoke locally, and remove the project
from your Google Cloud console to revoke properly.
cd sync && PYTHONPATH=. python3 -m unittest discover -s ../tests -t .. -v
node --test tests/*.test.jsNo dependencies, no dev dependencies. The Python sync is standard library only
and the QML logic lives in Model.js and QuickAddParser.js, which load under
Node precisely so they can be tested.
Panel.qml and BarWidget.qml are not unit tested. Quickshell widgets need a
live shell to render, and building that harness would cost more than it catches.
Anything worth testing was deliberately pushed down into those two files.
MIT. Derived from Omarchy's built-in clock plugin, whose copyright notice is
kept in LICENSE.
vendor/Calendariale.js is a bundle of calendariale 0.7.0 by Carlo Dapor. Its BSD
license is in vendor/calendariale.LICENSE.



