Calendar tool
The canonical version always lives at https://tavina.ai/docs/friendly/tools/calendar
Calendar tool
Calendar is a Standard tool: it sits in the default toolbar from the first login (toolbar label Calendar), and if you hide it while customizing the toolbar you can re-enable it yourself from Settings โ Appearance โ Toolbar โ no request or grant is needed.
Tavina’s Calendar tool gives you a full-width schedule workspace inside the Tavina app. In the dev channel, it supports visual month and agenda planning, event search and jump-to-date navigation, a review-first day-at-a-glance view, native event management, sub-calendar organization with color-coded views, ICS import and export, sub-calendar sharing, optional connected calendar sources, and permission-aware schedule context Tavina can use in chat without requiring Google Calendar. Tavina can also set up sub-calendars and schedule, edit, and delete events for you in chat, using the same safe approval flow described below.
Use it when you want to see your schedule at a glance or manage events directly from the Calendar screen. Google Calendar is no longer a separate Calendar work panel; when connected, it appears inside this Calendar as an optional read-only source.
Layout and navigation
The Calendar tool uses a full-width layout with a compact toolbar that sits directly above the calendar grid, so your schedule starts near the top of the screen. There is no separate large Calendar header.
The toolbar includes:
- month or agenda period navigation with a Today button;
- New event for creating a native event;
- Search for finding events and jumping to a date;
- Filter for controlling which sources are visible;
- Settings (gear icon) for sub-calendars, sharing, import/export, display density, and your clock display preference.
Source filtering lives entirely in the sources drawer โ there is no external sub-calendar or source pill strip under the toolbar, at any screen width. Open the drawer with the Filter button to toggle sources, sub-calendars, and shared calendars on or off; your visibility choices persist exactly as before.
The Filter button opens a slide-out sources drawer where you can see the full list of sources, including shared calendars with owner and permission details.
The Settings button (gear icon) opens a Settings modal organized into four tabs: Sub-calendars for creating, editing, and deleting sub-calendars and managing sharing; Preferences for display density, your time-zone note, and your 12-hour or 24-hour clock display preference; Import/Export for ICS imports and exports, and Recently deleted for reviewing and restoring deleted sub-calendars and events within a 30-day recovery window.
What you can do
The Calendar tool can help you:
- view your schedule in a month view or mobile-friendly agenda view;
- click any day for a review-first day-at-a-glance modal with weather, tasks, events, and routines for that date;
- create a native event or a real dated Tavina task straight from that day view;
- search events by title, description, or location across a date range you choose, and jump to a specific date;
- choose a Comfortable or Compact display density and a 12-hour or 24-hour clock display, both saved per subscriber;
- create, edit, delete, and view native Tavina Calendar events;
- when deleting a recurring event in the app, choose exactly what to remove โ only that date, or the entire series โ before anything is deleted;
- choose all-day or timed events;
- create, edit, delete, and toggle native sub-calendars such as Personal or Work;
- share a native sub-calendar with another mapped Tavina subscriber using free/busy, view, suggest/comment, or edit access;
- see shared calendars in the sources drawer with owner and permission metadata;
- review, accept, leave, or revoke Calendar shares from Calendar and Settings โ Account โ Shared Tools;
- preview an ICS calendar file before import, then explicitly import safe native Tavina copies into a selected sub-calendar;
- export native Tavina sub-calendars to ICS when your permission allows it;
- filter visible sources, sub-calendars, and shared calendars in the sources drawer โ every visibility toggle is one tap away and your choices persist;
- see recurring Routine occurrences projected into Calendar without turning them into native Calendar events;
- mark a Routine occurrence complete or skip one occurrence from Calendar when that action is available;
- let Tavina read a unified schedule context for chat, including native events, task deadlines, unscheduled tasks, Routine occurrences, Weather advisories, conflicts, free blocks, and permission details;
- ask Tavina for safe schedule suggestions or approved Calendar actions without allowing silent multi-event changes;
- ask Tavina to create a native sub-calendar for you โ with a name, color, and optional icon โ as an approved Calendar action;
- ask Tavina to create a native event into an existing sub-calendar as an approved Calendar action;
- ask Tavina to edit an existing event โ its title, description, location, or times โ as an approved Calendar action;
- ask Tavina to delete an event for you โ one event, a single occurrence of a series, or a whole series โ as an approved Calendar action;
- recover deleted sub-calendars and events from Recently deleted for 30 days after deletion;
- start with a blank, writable Main Calendar already set up for your account, so event planning works right away (no manual first-calendar setup);
- still get clear next-step guidance from Tavina in the rare case where no writable sub-calendar exists, instead of a silent failure;
- read color-coded event pills with source type, status, and link cues.
The Calendar tool is designed to match Tavina’s theme, so the calendar grid, the sources drawer, modals, and event pills should adapt with the rest of the app.
Native events and sub-calendars
Native events are events owned by Tavina Calendar. They can be created and managed without connecting an outside calendar account.
Sub-calendars help group those native events. For example, you might use one sub-calendar for personal plans and another for work plans. Each sub-calendar has its own color. Every account starts with a blank, writable Main Calendar ready to use โ you never have to create a first calendar manually. You can delete it like any other sub-calendar if you organize your own calendars instead, and Tavina will not silently recreate it once you have made that choice โ Calendar protects your last remaining native sub-calendar, so you always keep a place for events, and any deletion can be undone from Recently deleted for 30 days. Toggle sub-calendar groups on or off in the sources drawer (toolbar Filter button) when you want a cleaner view โ the drawer lists every source with its color, and your visibility choices persist. You can create sub-calendars yourself in the Settings modal, or ask Tavina in chat to create one for you with a name, color, and optional icon.
The Holidays sub-calendar
Every account also includes a shared Holidays sub-calendar, visible by default as the second entry after Main Calendar. It is curated and managed by Tavina โ not a generic third-party holiday feed โ so it includes the holidays you expect, including floating ones like Mother’s Day (second Sunday of May), Thanksgiving (fourth Thursday of November), and exact-date entries like Black Friday, Good Friday, and Easter Sunday.
You can hide and show Holidays with the same visibility toggle you use for any other sub-calendar in the sources drawer. Hiding it only changes your own view; it never removes the calendar or affects anyone else. Because Holidays is system-managed, you cannot rename it, change its color, delete it, or edit its events โ it stays consistent for everyone, and later corrections are applied centrally.
Client appointments and booking foundation
The dev Calendar includes behind-the-scenes groundwork for future client booking and appointment features. This is not visible as a separate panel or screen โ it is backend preparation only. There is no public booking page yet, and it does not send automatic reminders or confirmations.
The groundwork lets Tavina represent booking-related records without misusing generic event fields:
- Appointment events are confirmed or owner-approved client appointments. They count as busy time.
- Booking hold events are temporary holds while a request waits for owner approval, intake, payment, or expiration. They also count as busy time until released.
- Availability window events describe owner-approved time that may be bookable. They indicate candidate free time, but they do not expose private event details.
- Booking blackout events block booking for holidays, buffers, service exceptions, or manual blackout dates.
If you want to keep client work separate, create a native sub-calendar such as Client Appointments and store appointment-related events there. Tavina manages all native events in one consistent system.
Booking metadata can include client/contact references, service type, booking status, owner approval state, location or video details, intake-form state, cancellation state, and future confirmation/reminder hooks. Those hooks are metadata only for now; the email, SMS, or notification automation is intentionally deferred.
Privacy boundary: future public booking screens would show availability and free/busy status only. They should not expose private event titles, notes, locations, linked records, or client/contact metadata. Calendar sharing already redacts free/busy-only views server-side, and the booking foundation follows that same rule.
Importing and exporting calendars
Calendar interoperability is copy-based unless Tavina says otherwise. Native Tavina Calendar is the primary home for events and sub-calendars you manage in Tavina. External calendars, connected sources, and uploaded calendar files do not silently replace your native data.
Importing an ICS file
Use Import/Export in the Settings modal when you have an .ics calendar export from another product, including Google Calendar. The import flow should:
- ask you to choose an editable native Tavina sub-calendar;
- let you paste the ICS text or upload the
.icsfile directly โ both follow the same steps; - preview the events before anything is saved;
- show validation errors or phased features, such as unsupported recurrence exceptions;
- import only the events that Tavina can safely copy into native Calendar after you choose to apply the import.
Imported items are Tavina-owned copies. Tavina keeps source metadata such as the original ICS UID and source label where available, but the uploaded ICS file or external provider does not stay linked as the live owner. Import is intentionally non-destructive: it should not delete existing Tavina events or rewrite an external calendar.
The dev-channel importer handles common all-day events, timed events, standard time zones, basic recurrence rules (including ordinal weekday rules like the second Sunday of a month, and last-weekday selections), skipped recurrence dates, and events that carry more than one recurrence rule by importing each rule as its own event. More advanced calendar constructs may be shown as phased or blocked until a later implementation supports them safely. Imports are bounded to keep the preview responsive: an ICS import is capped at 1 MB of calendar text and 500 events per import.
You can also ask Tavina in chat to import an .ics file you have attached to the conversation. Tavina shows you a preview of what would be imported โ importable events, blocked items, and any errors โ and only applies the import after you approve it, like other Calendar actions.
If you want to bring Google Calendar events into native Tavina Calendar, the current path is to export an ICS file from Google Calendar, preview it in Tavina, and then import native copies. This is separate from the optional Google Calendar connected source, which remains a read-only overlay.
Exporting to ICS
Use Export ICS from the Settings modal when you need a portable copy of a native Tavina sub-calendar. Export respects Calendar permissions:
- owners can export their own native sub-calendars;
- recipients with view, suggest/comment, or edit access can export the shared calendar details their permission allows;
- free/busy-only shares cannot export private event details.
ICS exports include native Tavina Calendar events from the selected sub-calendar. They do not include Google Calendar overlays, task deadlines, Routine occurrences, Weather advisories, or other projected sources.
Migration guidance
House FraeLea dashboard calendar patterns may be useful UX inspiration, especially for approachable schedule views and clear source labels. They are not a legacy dependency. Tavina should not port the old Radicale filesystem-bypass architecture or treat CalDAV storage as the native Calendar database.
CalDAV server compatibility is explicitly deferred unless a later product decision approves it.
Sharing sub-calendars
Calendar can share a native sub-calendar with another Tavina subscriber when that person is connected to you through the approved identity and relationship flow. Tavina keeps ownership of the Calendar data and manages the access grant.
Supported Calendar sharing levels are:
| Permission | What the recipient can do |
|---|---|
| Free/busy only | See scheduling blocks such as busy, tentative, or out-of-office time. Titles, notes, locations, linked details, and private metadata stay hidden. |
| View only | See event details allowed by Calendar privacy rules, but not change the shared calendar. |
| Suggest/comment | Use suggestion-oriented access when available, without directly changing the owner’s events. |
| Edit | Create, update, and delete native events inside the shared sub-calendar. Tavina enforces edit access on the server, not only in the app interface. |
Manage-sharing authority stays owner-only in this dev-channel release. Public calendar links and anonymous sharing are not part of this flow.
When someone shares a sub-calendar with you, it appears in the sources drawer after acceptance, showing metadata such as who shared it and which permission you have. You may hide a shared calendar locally by toggling it off in the drawer without leaving the share. Leaving a shared calendar or the owner revoking it removes access from Calendar views, API feeds, and assistant context.
Tavina chat, schedule context, and safe actions
When Tavina uses Calendar in chat, it should work from a unified schedule context rather than guessing from screen text. That context can include native Calendar events, shared Calendar events you are allowed to use, task deadlines, unscheduled tasks, Routine occurrences, Weather advisories, detected conflicts, free blocks, and source/permission metadata.
Calendar context is source-aware. Tavina should distinguish native Calendar events from task, Routine, Weather, Google-style, and shared projections so you know which tool owns each item and where real edits should happen. Task deadlines and Routine occurrences remain owned by their original tools unless you deliberately create a Calendar event or time block.
Calendar context is also permission-aware. Server-side access checks apply before Tavina can read or act on a shared calendar. Accepted shares can be used by the assistant only while assistant access is enabled for that share. If access is revoked, denied, suspended, expired, or turned off for assistant use, Tavina should stop including that shared schedule in future context.
For free/busy sharing, Tavina should only see scheduling blocks such as busy, free, tentative, or out-of-office time. Titles, descriptions, locations, linked task or Routine details, and private metadata stay hidden.
Travel-aware event heads-ups
For events with a location, Tavina can work out realistic travel time and tell you when to leave โ early enough to actually make it โ instead of relying on a fixed reminder alone. Far-away events get an earlier heads-up than errands around town, outdoor events can include the expected weather, and every event nudge carries an Open in Maps link. This behavior follows your Proactivity settings and can be tuned or turned off there. See Proactivity and proactive moments.
Safe Calendar actions use approval modes:
| Mode | What to expect |
|---|---|
| Inform | Tavina explains schedule information without preparing a change. |
| Suggest | Tavina proposes a change you can review before anything is saved. |
| Draft | Tavina prepares a draft plan or draft event details, but does not commit them. |
| Commit single action | Tavina may apply one approved Calendar action, such as creating, rescheduling, editing, or deleting one event. |
| Commit plan | Tavina may apply an approved multi-step plan after explicit approval. |
| Configured auto-act rule | Tavina may act automatically only within a rule you have deliberately configured. |
Tavina should not silently make multiple Calendar changes from an ordinary suggestion. Agent-initiated or agent-suggested Calendar changes should leave an audit trail with the actor, source, reason, approval mode, result, and affected events or related items.
Creating a sub-calendar through Tavina works the same way. In Suggest or Draft mode, Tavina only proposes the new sub-calendar โ its name, color, and optional icon โ for your review. The sub-calendar is actually created only under a commit mode you have approved. Creating an event into an existing sub-calendar follows the same approval rules as other Calendar writes.
Editing an existing event works the same way: in Suggest or Draft mode, Tavina shows the proposed changes โ title, description, location, or times โ and applies them only under a commit mode you have approved. Deleting an event follows the same rules, whether you mean a single event, one occurrence of a recurring series, or the whole series. Deletions Tavina makes on your behalf are recorded in Recently deleted and can be restored like any other deletion. Tavina cannot edit or delete events on a shared calendar unless you have edit permission there, and it can never edit or delete the system Holidays calendar.
Your account already starts with a writable Main Calendar, and Calendar protects your last remaining native sub-calendar from deletion, so this situation should not arise through normal use. If you ask Tavina to schedule something and no writable sub-calendar exists, Tavina will not fail silently. It explains the problem and offers clear next steps โ such as creating a new sub-calendar first โ so you can finish the task in one conversation.
Calendar and Tasks together
Calendar and Tasks now follow a defined integration contract, so task deadlines and time-blocking work together without one tool overwriting the other:
- tasks with due dates appear on your calendar as read-only task deadline overlays โ the task itself still lives in Tasks;
- you can ask Tavina to time-block a task, which creates a native Calendar event linked to that task; completing or rescheduling the task still happens in Tasks, and the calendar block is just its scheduling surface;
- Tavina can also see your unscheduled tasks as context, so it can suggest realistic time blocks for real work instead of guessing;
- you can create a dated task directly from the Calendar’s day-at-a-glance modal โ it becomes a real Tasks item with a due date on the chosen day, not a duplicate event.
Source filters
All source filtering happens in the slide-out sources drawer, opened from the toolbar Filter button โ the calendar surface itself carries no external source pill strip at any width. Each source row shows its color and name, and includes shared calendars with owner and permission details. Toggle any source on or off; your visibility choices persist across sessions, so the calendar comes back the way you left it. Use the Reset filters control in the drawer whenever you want the default all-sources view back.
| Filter | What it represents |
|---|---|
| Native events | Tavina-owned Calendar events |
| Personal / Work-style sub-calendars | Native sub-calendars you can manage in Tavina |
| Tasks | Task deadlines or scheduled work blocks |
| Routines | Recurring Routine occurrences projected from Routines/Clock; Routines still owns the definition |
| Weather | Weather-related schedule advisories |
| Google Calendar overlay | Optional connected Google Calendar items shown as read-only overlays |
| Shared calendars | Native sub-calendars shared with you by another Tavina subscriber |
Only real sources appear in the drawer โ your sub-calendars, live projections from Tasks, Routines, and Weather, a Google Calendar you have actually connected, and calendars genuinely shared with you. Projection sources are read-only views of their owning tools (edit a task in Tasks or a routine in Routines/Clock), and there are no sample or demonstration sources: a fresh calendar starts empty besides your Main Calendar and system Holidays.
Routine occurrences in Calendar
Routine items shown in Calendar are projected occurrences. The Routine definition still belongs to Routines/Clock, not Calendar. This means you can use Calendar to see when a Routine is expected to happen, but editing the Routine itself still happens in the Routines/Clock tool.
Routine occurrence pills should look different from native events and task deadlines. When possible, they should show a link or label for the originating Routine so you know which Routine owns the item.
From Calendar, available Routine occurrence actions may include:
- Open routine โ go to Routines/Clock for Routine details and edits;
- Mark complete โ record that one scheduled occurrence was completed;
- Skip occurrence โ skip only that scheduled occurrence without deleting the Routine.
Completion and skip state apply to the occurrence you selected. Skipping one occurrence should not remove the whole Routine, and editing the Routine’s recurrence in Routines/Clock should update the projected Calendar occurrences.
Reviewing a day: the day-at-a-glance modal
Clicking a day opens a review-first day-at-a-glance modal instead of assuming you want to create something. The modal shows the full selected date โ its eligible weather summary, dated tasks, events, and other enabled sources such as routines โ in clear sections.
From the modal header you can act explicitly:
- Add event opens the New Event form with that date preselected;
- Add task creates a real Tavina task (see below);
- Close returns to the calendar without changing anything.
The modal respects your current source filters and permissions: it lists everything you are allowed to see for that date within the sources you have enabled, and it tells you when items are hidden because a source is toggled off. All-day events are grouped ahead of timed events. On desktop, hovering a day gives a quick preview before you commit to a click.
Creating and editing events
Creating and editing events happens in compact modal dialogs โ no page navigation needed. Use New event in the toolbar or Add event in a day’s modal to open the New Event form; click an event pill to open its detail modal. From the detail modal you can edit or delete the event.
The New Event form keeps everything on one screen:
- a clear title and destination sub-calendar, with an All day option;
- side-by-side Start and End fields that show dates only for all-day events and dates plus times for timed events, with the effective timezone shown unobtrusively. In 12-hour mode each time field is paired with a compact AM/PM toggle tucked just beneath it, so noon can never be saved as midnight by accident, and the form shows a resolved-time confirmation line such as Wed, Oct 28 ยท 12:00 PM โ 1:00 PM (MDT) before you save โ the same resolved time appears on the event card;
- Repeat controls for common recurrences โ collapsed out of the way until you need them: a compact toggle expands the repeat editor, and its collapsed summary always reflects the active rule. Choose an interval such as weekly or every two weeks, pick weekdays with simple chips when relevant, and read a plain-language summary like Every 2 weeks on Tuesday so you always know what will be scheduled. Monthly and yearly repeats can anchor either to the date (the 15th of each month) or to a chosen weekday such as the second Sunday or the last Monday, with summaries like Every year on the second Sunday of March. Daylight-saving transitions are handled so recurring times stay on the intended clock time;
- optional Location and Description fields.
If a field is missing or invalid, Tavina shows a friendly validation message next to the field before saving. If the server cannot save the event, Tavina keeps your draft in the form and explains what went wrong.
How event times and time zones work
New events prefill your current Routines time zone, and each event remembers the zone it was saved with. An event keeps its wall-clock time in that zone: if you later change your time zone, existing events do not silently move โ a 12:00 PM Denver event stays at 12:00 PM Denver and, when you view it from another zone, Tavina shows both times labeled, like 12:00 PM MDT (9:00 AM your time). All-day events are anchored to the date itself, so they never shift when you travel. When Tavina shows you a schedule in chat or briefings, it reads the event’s local display time, never a raw stored timestamp (tavina/tavina#2743).
Adding a dated task from Calendar
Add task in the day-at-a-glance modal creates a real Tavina task โ not a duplicate calendar event. You give it a title and the selected day becomes the task’s due date, with the board and list the Tasks tool expects. Because it is a genuine task, it appears in the Tasks tool and projects back onto the calendar through the Tasks source, keeping one source of truth. Editing, completing, or deleting it later happens in Tasks, not in Calendar.
Finding events: search and jump to date
Use Search in the toolbar to find an event without paging month by month. Search matches titles, descriptions, and locations, ignoring letter case.
You control the scope:
- the date range is explicit and adjustable โ it defaults to the next 90 days, and you can point it at past or future periods up to a year at a time;
- your current source filters and permissions apply, so results only include what you are allowed to see, and the panel states which sources were searched;
- if a connected source such as Google Calendar cannot be fully searched, the panel says so instead of reporting a misleading no events found.
Results are listed chronologically with title, date and time, and source, and loading more results is explicit. Selecting a result takes you to that event’s date and opens its detail view. If the event belongs to a source you have hidden, Tavina offers to reveal it rather than silently changing your saved filters.
Jump to date in the same panel navigates directly to any date you enter โ handy for planning ahead or checking a past week.
Deleting events or sub-calendars
Deleting an event or sub-calendar uses a confirmation step so you do not remove something accidentally, and the confirmation is honest about what will happen: it states exactly how many events will be removed with a sub-calendar, that the deletion can be undone, and for how long. Deleting a sub-calendar that still holds 25 or more events asks you to type its name before it will proceed.
Deletion is recoverable. Before anything is removed, Calendar captures and verifies a recovery snapshot โ if that capture fails, nothing is deleted. Deleted sub-calendars and events then wait in Settings โ Recently deleted for 30 days, where you can review them and restore them; restoring a sub-calendar brings its events back too. Events Tavina deletes for you in chat follow the same confirmed, recoverable path and appear in Recently deleted as well.
A few things are deliberately protected: the system Holidays sub-calendar cannot be deleted, your last remaining native sub-calendar is kept so you always have a place for events, and shared sub-calendars offer Leave share rather than delete. Both deletions and restores are recorded in the Calendar audit trail.
External and projected sources are not managed through this native sub-calendar delete flow.
Visual design and views
The calendar uses a full-width layout with a compact toolbar, so the month grid starts near the top of the screen. Events appear as color-coded pills โ each pill carries a left-border accent in its sub-calendar’s color so you can quickly identify which group an event belongs to, with consistent time, source, and title hierarchy.
In month view, each day cell leads with a clean date row: the date number, a crisp marker for today, and โ only for today and future dates with a forecast available โ one subtle weather summary with a small condition icon and the high and low temperatures. Wind, precipitation details, and advisories live in the day view rather than crowding the grid, and past dates show no forecast clutter.
When a day cell has room, event previews arrange in two tidy columns; on narrower cells they fall back to a single column. Weekends and outside-month days stay quietly distinguishable without shouting. If a day has more events than fit, an accurate +N more link appears โ click it to open the day-at-a-glance modal for the complete picture.
If a busy month feels cramped, open Settings (gear icon) and switch Display density from the default Comfortable to Compact to fit more events per screen. The preference is saved for your account, and it changes spacing only โ never which events are visible.
Times can read the way you expect, too: in the same Settings modal, the Preferences tab offers a Time format choice between 12-hour and 24-hour. New accounts start on 12-hour, and the choice applies everywhere the Calendar shows a time โ month grid previews, the agenda list, event details, search results, and the day-at-a-glance view. It only changes how times are displayed; events are stored the same way either way (tavina/tavina#2350).
The calendar adapts to phones and narrow screens, supports keyboard navigation and screen-reader labels for its controls, and uses more than color alone to convey source and state information.
Use agenda view when you want a list-style plan for upcoming days. This is especially useful on phones and narrow screens. Clicking an event in any view opens its detail modal.
What is still in progress
The Calendar workspace has grown into a complete planning surface, but it is not the final Calendar system.
Still planned or intentionally out of this version:
- drag-and-drop or resize saving for events;
- Google Calendar live write-back from the native Calendar screen;
- CalDAV server/client compatibility unless separately approved;
- irreversible or destructive live migrations;
- delegated manage-sharing flows, public links, and anonymous sharing if later approved;
- public booking pages, staff, room, or resource scheduling;
- advanced recurrence editing in the Calendar screen itself, such as changing a single occurrence of a series โ Tavina can already update or delete a single occurrence for you in chat.
If you need a change that the Calendar screen does not support yet, use Tavina chat or the connected app/tool that already owns that action.
Recommended expectations
The Calendar tool is now useful for dev-channel native event planning, day-by-day planning with tasks, event search, client-appointment preparation, import/export testing, and schedule review. Treat connected and projected sources as overlays unless you intentionally import native copies, and use native sub-calendars for events you want to manage today.