Thank you for your clarifying questions. Yes, you have understood my request correctly.

Regarding completed task sessions in Morgen: When a task is completed in Morgen, I would like the corresponding event that Morgen created on the source calendar (e.g., Google Calendar) to be deleted. However, it is essential that Morgen retains the full task history within its own application for review, analytics, and reporting.

Regarding why I look at my source calendar and not Morgen: I frequently view my source calendar (Google Calendar, in my case) directly for several reasons:

Quick overview: It's often my default view on other devices or widgets (e.g., phone's home screen, desktop calendar app) that primarily pull from Google Calendar.

Sharing: I occasionally share my main calendar with others, and seeing only active commitments there provides a clearer picture for them without historical clutter.

Integration with other tools: Some tools or browser extensions I use integrate directly with Google Calendar, not Morgen.

Visual Clarity: The main reason is to have a clean, uncluttered calendar that only shows active, upcoming, or pending commitments. When completed task blocks remain, it makes it difficult to quickly distinguish what still needs attention versus what is already done, leading to visual noise and less effective planning at a glance.

Thank you again for looking into this.

Gem Great!

This is really interesting feedback, thank you for sharing.

I assume the calendar sets where you can hide groups of calendars together doens't suit your workflow here.

I also assume you want to see completed tasks in Morgen so don't hide them, but at a quick glance don't want to see them.

I too use the Google calendar month widget on my phone, but hide unwanted calendars, such as my tasks calendar.

Regarding the browser extension tools I am curious what they do. Could you share?

I ask as we are currently working on our web app for browsers and would love to get some insight into how different people work on web.

Thanks for your reply. Here's more detail on your questions:

You're right: hiding entire task calendars doesn't suit my workflow. I need active tasks visible on my Google Calendar for planning and quick overview. The issue is completed task blocks persisting, causing clutter and hindering quick distinction of what's still pending.

You're also right about completed tasks: I need them in Morgen for history/analytics, but not on my Google Calendar for clear, at-a-glance daily planning.

I understand your approach of hiding your task calendar. However, my need is to see active tasks directly integrated and visible on my main Google Calendar for comprehensive planning.

Regarding browser extensions, I use them for:

Quick calendar/task creation from any webpage.

Meeting scheduling/availability finding.

Time tracking integration from events.

General Google Calendar UI enhancements/customization.

Hope this helps with your web app development. Understanding quick actions and integrated workflows on web calendars is key for me. Thanks for seeking this insight.

Gem: This is great. Thank you.

Out of curiosity, quick calendar/task creation from any webpage. Is that done through highlighting text on a webpage to save or to save a page link as a task?

I use the global command bar in Morgen to create tasks and events using the global hotkey but it doesn't currently allow description information.

Thanks for getting back to me and for the insights. Let me clarify on the browser extension use for quick calendar/task creation from a webpage.

It's often both highlighting text and saving a page link, depending on the extension's capabilities. For instance, I use extensions that allow me to save the current page link as a task/event, or highlight specific text on the page to populate its description or title directly.

The goal here is seamless context capture directly from what I'm viewing online. After this, I then aim to use natural language within the extension's pop-up to quickly add all scheduling details (like a due date, duration, or reminder) and assign it to a category.

For my workflow, the value is in this entire chain: the quick, context-rich capture from a webpage, followed by an equally quick and comprehensive definition of the task's scheduling parameters. Any missing piece in that initial capture process adds friction and extra steps later on, which I aim to minimize for efficient daily planning.

Gem Thank you for sharing this.

I have added this FR: https://morgen.canny.io/feature-requests/p/add-tasks-from-webpages

With the new web app this could be something we develop in future.

Danny HatcherYou are welcome.