We just shipped calendar feed ingestion to Sabine. It's a capability we've been building toward since the beginning: giving Sabine the ability to understand your schedule, not just reactively answer questions about it.
The problem we're solving is straightforward. An AI partner that can't see your calendar is flying blind. It can't help you prepare for meetings, can't suggest when to focus on deep work, can't intelligently route inbound requests based on your availability. Calendar awareness isn't a feature—it's table stakes for any system that claims to work alongside you.
What We Built
This release adds two core capabilities: ICS parsing and Google Calendar sync. The ICS parser handles the standard calendar format—events, recurrence rules, time zones, all the details that make calendaring surprisingly complex. The Google Calendar integration pulls your schedule into Sabine's context automatically.
We implemented this as a skill in Sabine's repertoire. When you connect your calendar, Sabine gains the ability to read and reason about your schedule. It can see what's coming up, understand time blocks, and factor your availability into its responses. The skill runs through Strug Works orchestration, which means it inherits all the observability and error handling we've built for agent execution.
Why It Matters
Calendar integration is foundational because it unlocks proactive assistance. With calendar awareness, Sabine can prepare briefings before meetings, suggest optimal times for focused work, and help you protect your schedule from fragmentation. This is the difference between an AI that responds to questions and one that anticipates your needs.
This is version one. We're starting with read access and basic event parsing. We're not yet writing back to your calendar or handling complex scheduling negotiations. Those capabilities will come as we validate the underlying mechanics and gather feedback on how people actually want to interact with calendar data through an AI partner.
What's Next
The immediate priority is validation. We need to ensure the ICS parser handles the long tail of calendar formats correctly—recurrence rules get weird. We're also building integration tests that verify end-to-end sync behavior, not just unit-level parsing. Downstream, we're working on calendar write capabilities and intelligent scheduling assistance that uses this feed data to make proactive suggestions. The goal is Sabine that doesn't just know your schedule, but actively helps you manage it.