Your calendar should be everywhere.

In the 90s, my dad was an early adopter of what were then called PDAs. He called his Psion his ‘agenda’. Basically, that was the primary function it fulfilled for him.

In the 00s, when I was studying, I was a relatively early adopter of smartphones, using Windows Phone. One of my primary use cases was also the calendar. Once I started working, I got deeper and deeper into using my calendar as one of the primary sources of truth for what is happening in my life. If it's not in my calendar, I will forget it. I love getting things out of my brain and into my calendar—or my notes app, of which I am also a long-term user.

Over the years, of course, I have often looked for more and better from my calendar apps. The much-loved Sunrise calendar had amazing planning functionality. After it was acquired by Microsoft, it was killed. Fantastical worked okay for a while; at least it had natural language event creation and integration across multiple accounts. More recently, I have been a user of Vimcal, which is great as far as a calendar app goes.

But no matter how good a calendar app gets, changing dates and times on a phone just plain sucks. Typing on a phone sucks. Scrolling time and date wheels sucks. Dragging events with your finger sucks, especially if you have to move them to another day. Even with Vimcal, I keep having trouble.

AI agents are a UX for making changes to a calendar. They can even work in the background. When I started simply forwarding messages to my OpenClaw agent for scheduling, I was converted.

But even the best models are bad with times and dates. They hallucinate dates, miscalculate timezones, or miss key events. After several iterations and much tinkering, I figured out how to get OpenClaw to do a great job with my calendar. But the only way to connect multiple accounts was via a CLI. That still did not let me easily connect apps like ChatGPT to all my calendars.

My belief is that your calendar should be everywhere, like a metalayer. I want my calendar available on all my devices and in all the key apps I use: ChatGPT, Claude, OpenClaw, iPhone, Watch, and Slack. That's what Oggie is.

Copy and paste is not an app. It is a capability that exists underneath every app. Your calendar should work the same way.

Apple made that idea even more obvious with Universal Clipboard: you copy something on your phone and paste it on your Mac. You do not think about which device owns the clipboard. It is simply available where you need it.

You connect your calendars once, and after that they are available wherever you happen to be. The app or agent you are using is just the surface. Oggie is the layer underneath that makes the calendar available, keeps the context intact, and makes sure the change happens in the right place.

That is what I mean by a calendar metalayer.

Your calendar contains personal information, and that needs to be handled with care. Each connection to Oggie is authorized separately and can be revoked independently. Oggie's permission model supports narrower access per connection, such as letting an agent see availability without seeing event details or changing anything.

When a connection can make changes, Oggie marks edit and delete operations in its MCP metadata. ChatGPT or Claude can then apply the approval settings you chose there. Oggie relies on the agent's guardrails for confirmation.

Oggie reads calendar information directly from Google or Microsoft when an agent needs it instead of keeping a local copy of your events for ordinary calendar answers. It returns only the information needed for the request.

Your messages with Oggie's native agent, shared working context, durable memory, and screenshots are encrypted before they reach the database. Someone with access to the database alone sees ciphertext, not your conversations, memories, or images. Oggie's backend decrypts authorized content only when needed, and the keys never go to clients or Supabase.

The native agent only uses AI model providers that support zero data retention and no prompt training.

Read the complete details in Privacy and data handling.