> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/release-notes/2026/2026.35.0.md).

# 2026.35.0

September 1, 2026

## Google Calendar Sync

Thanks to everyone who tried Google Calendar Sync during Public Preview and shared feedback. With this release, we’re removing the Public Preview label—Google Calendar Sync is now stable and ready for daily use! Feature overview:

* Connect your Google calendars with Daylite and keep both in sync—appointments you create in either app show up in the other. You can choose to sync one Google calendar, or all of them.
* Bringing Google events into Daylite allows you to link them to your contacts, projects, tasks, etc., so they become part of your full history in Daylite.
* You can now share your Google schedule with your Daylite team, with the option to keep the details of your events private (share availability only).
* Available on Mac, iPhone, and iPad.
* To learn more, visit our [Google Calendar Sync](https://docs.daylite.app/help/mac-fundamentals/calendars/google-calendar-sync) article.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.daylite.app/help/release-notes/2026/2026.35.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.