Why reminder lists are global by default in GoWork

If you ask GoWork “what reminders do I have?”, the default answer should usually be a global list of active tasks, not just the subset bound to the current chat. The short answer is simple: this is not conversation leakage, and it is not a broken list. It happens because query scope and notification delivery are different layers. In most real workflows, “what reminders do I have?” means “show me everything still active,” not “show me only what belongs to this visible chat.”

That distinction matters in GoWork because the product is not just a pop-up reminder box. OmniGoAI's GoWork has to manage task triggering, execution context, notification targets, and list queries at the same time. Once those layers get mixed together, people start asking the wrong question: if a task was created here, why do I see other reminders in the list, or why is current conversation not the default filter?

If you have already read Where do GoWork scheduled-task notifications go? and Interval monitors vs daily reminders in GoWork, this article narrows the focus to the listing action itself: why is all the better default for reminder queries in GoWork, and when does current conversation become the right answer instead?

The short answer: reminder lists usually answer an account-wide inventory question

When users ask questions like:

1. “what reminders do I have?”
2. “how many scheduled tasks are still active?”
3. “which tasks are still running?”

what they usually mean is:

• show me everything still alive;
• do not limit the answer to one chat window;
• help me understand what automation is currently active across my setup.

That is why a global default is usually the more useful one. all answers an inventory question. current conversation answers a filtering question. Neither is universally better, but they solve different problems.

Why is current conversation not the default?

Because in many cases it is too narrow.

Imagine a very normal setup:

• you created a weekly reminder on the web;
• another reminder in Telegram;
• a monitor in a separate team conversation;
• then you return to the current chat and ask, “what reminders do I have?”

If the system only returns the one or two tasks bound to this chat, that usually feels incomplete rather than precise. A current-conversation default often looks like missing data, not good scoping.

That is why “what reminders do I have?” is usually best treated as a whole-account inventory query, while “what reminders belong to this chat?” is the version that should shrink to the current conversation.

Creating a task here does not mean the list should only show tasks from here

This is the most common mental trap.

Users often collapse these three things into one:

1. where the task was created;
2. where the result will be delivered;
3. which tasks should appear in a list query.

But in GoWork, those are separate on purpose:

• creation surface: where the user created the task;
• notification target: where the result is delivered after a run;
• query scope: whether the list should show all active tasks or only the ones bound to the current chat.

A single task can easily satisfy both of these statements:

• it delivers back to the current conversation by default;
• it still appears in a global reminder list.

That is not contradictory, because those statements answer different questions.

When does the global list feel most natural?

Scenario 1: the user is trying to inventory active automation

Examples:

• “how many reminders do I have?”
• “which scheduled tasks are still active?”
• “what follow-up automations are still running?”

These are not chat-local questions. They are system-wide state questions. A global scope avoids hiding tasks created somewhere else.

Scenario 2: the task and the delivery target are not in the same place

GoWork can create a task in one conversation and deliver the result somewhere else, for example:

• created on the web;
• delivered to a DingTalk room;
• or sent back to a fixed project conversation.

In that kind of workflow, filtering only by the current chat does not show the full picture. The global view is better for management. The current-conversation view is better for local inspection.

Scenario 3: some tasks are intentionally silent

Some tasks do not notify on every run, such as:

• polling every 5 minutes and only notifying on a match;
• periodic background summaries that only surface failures;
• tasks that mainly keep run history without pushing live messages.

If the user asks for an inventory of active reminders, the global list should include those silent tasks too. Otherwise users may incorrectly conclude that “no notification” means “no task.”

So when is current conversation actually the right answer?

When the user explicitly asks for the current chat.

Typical phrasings include:

• “what reminders belong to this chat?”
• “which scheduled tasks are bound to the current conversation?”
• “is the reminder we created here still active?”
• “show only the tasks for this conversation.”

In those cases, the user is no longer asking for an inventory. They are asking for a local filter. Current conversation is important, but it should not silently replace the global default for account-wide reminder questions.

Why do people confuse scope with notification delivery so often?

Because both are conversation-related, but they solve different problems.

Scope answers: which tasks should I see?

This is a list-query question. It determines which records are returned.

Notification delivery answers: where should the result go?

This is a task-output question. It determines which conversation receives the run result.

A common but incorrect assumption looks like this:

• the task result comes back to this chat;
• therefore the reminder list should also default to this chat.

That logic breaks because delivery and inventory are not the same dimension.

Why does a global default serve most users better?

Because when users ask “what reminders do I have?”, they are usually in management mode, not in local debugging mode.

They want to know things like:

1. did I forget to cancel something?
2. do I have duplicate reminders?
3. what automations are still running in the background?
4. did I create tasks in another conversation and forget about them?

Those are all better served by a complete view. If the system defaulted to current conversation, users would first need to know which chat to visit before they could reconstruct the whole picture.

A simple decision rule: is the user asking for inventory or location?

A quick rule of thumb works well.

Inventory questions: default to all

Examples:

• “what reminders do I have?”
• “how many scheduled tasks are active?”
• “which reminders are still running?”

These are account-wide inventory questions.

Location questions: use current conversation

Examples:

• “what reminders are in this chat?”
• “which scheduled tasks belong to the current conversation?”
• “what tasks are bound here?”

These are local filtering questions.

The three easiest mistakes to make

Mistake 1: making the default list too narrow

If the default only shows the current conversation, it often hides valid tasks created elsewhere.

Mistake 2: treating the creation surface as the query scope

A task may have been created here, but that does not mean every future inventory question should be limited to here.

Mistake 3: treating delivery logic as list logic

A result can return to the current chat without making the current chat the right default for reminder inventory.

FAQ

FAQ 1: Why do I see tasks from elsewhere when I check reminders in this chat?

Because “what reminders do I have?” is usually better answered as a global active-task listing. In most cases that is not a conversation mix-up. It is the intended inventory view.

FAQ 2: So what is current conversation for?

It is the right scope when you explicitly want to inspect only the reminders bound to this chat, for example when checking whether the task created here is still active.

FAQ 3: If results come back to the current chat by default, why is the list not also limited to this chat?

Because notification delivery and query scope are separate concepts. One decides where output goes. The other decides which records are returned in a listing.

FAQ 4: Why should silent tasks appear in the global list too?

Because they are still active automation. A task can be running without notifying on every cycle, and a proper inventory view should still show it.

The clearest way to understand GoWork reminder lists is to stop treating them like a simple message stream and start treating them as a task-management view. Once you separate creation surface, notification target, and query scope, it becomes obvious why all is the better default for reminder listings and why current conversation only becomes the right answer when the user explicitly narrows the question. For a deeper mental model, pair this with Where do GoWork scheduled-task notifications go? and the GoWork download page to walk through the flow end to end.