Calendar visibility not respected in task/event creation dropdown (Google Calendar integration)

I’m running into a persistent issue with the Google Calendar integration that, at this point, feels less like a configuration problem and more like a structural bug or design oversight.

Problem

My Akiflow account is connected to Google Calendar. Over time, my Google account has accumulated many calendars (old projects, shared calendars, archived contexts, etc.). I’ve made extensive attempts to clean this up from a visibilitystandpoint:

• Calendars are unchecked / hidden in Google Calendar

• Calendars are hidden inside Akiflow

• Some calendars are fully hidden or effectively inactive in Google Calendar

• Calendars are reordered alphabetically in Google Calendar so active ones appear at the top

Despite all of this, when creating a task or event in Akiflow and selecting a calendar, every calendar that still exists in my Google account appears in the dropdown, seemingly in a random order. This includes calendars that are hidden, unchecked, or otherwise not visible anywhere in my calendar views.

The result is that every task creation requires scrolling through ~20 irrelevant calendars to find the correct one. This adds friction at exactly the moment where Akiflow is supposed to be fastest.

Suggested improvements

Any of the following would improve this:

1. Respect Google Calendar visibility

   Calendars that are unchecked or hidden in Google Calendar should not appear in the task/event calendar dropdown.

2. Respect Akiflow calendar visibility

   If a calendar is hidden in Akiflow, it should also be excluded from selection lists.

3. Explicit calendar scoping

   A setting where users can define which calendars are eligible for task/event creation.

4. Stable and predictable ordering

   At minimum, ensure the dropdown order is consistent (e.g. alphabetical or matching Google Calendar order).

Right now, the only real workaround is permanently deleting entire calendars from Google Calendar, which is an unreasonably heavy-handed solution for users with archived or shared histories.

Posting this because it has a real impact on daily usability and seems addressable with clearer UX rules around visibility and user intent.