Daily Command Center
Prepare a bounded cross-app read of the user's current Gmail, Google Calendar,
and Todoist state. Keep the brief strictly read-only, including manual
invocations: never send, draft, label, archive, trash, or delete email; create,
update, delete, or respond to Calendar events; or create, update, complete,
delete, or reschedule Todoist records.
Source ownership and tool choice
- Gmail is incoming context, Todoist is the durable source of truth for
actionable tasks, and Google Calendar is the source of truth for time
commitments. Conversation history is not a task database.
- Prefer connected apps. For Todoist only, use the official hosted MCP as a
fallback when the app is unavailable; choose exactly one Todoist surface per
run.
- Resolve the current date and timezone from connected profiles. If the profiles
disagree materially, report the mismatch and use the Calendar timezone for
schedule rendering.
- For a later explicit mutation request, stop this daily brief and route to the
relevant service workflow.
$todoist-task-planning continues to own task and
time-block mutations.
Read the bounded sources
- Search Gmail with exactly
newer_than:2d in:inbox -category:promotions -category:social -in:spam -in:trash.
Cap the initial search at 30 messages, group results by thread, and expand at
most five likely-action threads. Do not treat Gmail labels alone as proof of
importance. Prioritize direct requests, deadlines, financial or security
notices, service interruptions, and application or administrative
consequences.
- Query Calendar with explicit timezone-aware bounds from the start of today
through the next seven days. Show today in detail and flag notable upcoming
commitments or conflicts. Page only inside that same bounded window when
necessary.
- Query Todoist for the authenticated current user's overdue, today, and
seven-day upcoming tasks. Report an empty state without inventing work.
Write the brief
Use these sections in this stable order:
Today at a glanceAttention nowCalendarTasksFYISuggested actionsCoverage and caveats
Keep scheduled output concise. Limit Attention now to five items and FYI
to three. For every attention item, state its source, time or date, why it
matters, any known deadline, and the recommended next step. Number suggestions
and phrase them as proposals for an interactive follow-up.
Redact verification codes, credentials, full account identifiers, and
unnecessary sensitive details. For financial or security alerts, recommend
direct verification rather than taking action.
Coverage failures and recurrence
If one connector fails or is unavailable, still finish a partial brief, name the
missing source, and do not substitute web search. State the bounded coverage and
avoid unsupported claims such as "the only urgent email." Re-read live sources
on every run; repeated unresolved items are acceptable. Never suppress an item
solely because conversation history says it was previously seen.
1---2name: daily-command-center3description: Use for read-only daily or morning briefs, daily planning, and scheduled command-center runs across Gmail, Google Calendar, and Todoist.4---56# Daily Command Center78Prepare a bounded cross-app read of the user's current Gmail, Google Calendar,9and Todoist state. Keep the brief strictly read-only, including manual10invocations: never send, draft, label, archive, trash, or delete email; create,11update, delete, or respond to Calendar events; or create, update, complete,12delete, or reschedule Todoist records.1314## Source ownership and tool choice1516- Gmail is incoming context, Todoist is the durable source of truth for17 actionable tasks, and Google Calendar is the source of truth for time18 commitments. Conversation history is not a task database.19- Prefer connected apps. For Todoist only, use the official hosted MCP as a20 fallback when the app is unavailable; choose exactly one Todoist surface per21 run.22- Resolve the current date and timezone from connected profiles. If the profiles23 disagree materially, report the mismatch and use the Calendar timezone for24 schedule rendering.25- For a later explicit mutation request, stop this daily brief and route to the26 relevant service workflow. `$todoist-task-planning` continues to own task and27 time-block mutations.2829## Read the bounded sources30311. Search Gmail with exactly32 `newer_than:2d in:inbox -category:promotions -category:social -in:spam -in:trash`.33 Cap the initial search at 30 messages, group results by thread, and expand at34 most five likely-action threads. Do not treat Gmail labels alone as proof of35 importance. Prioritize direct requests, deadlines, financial or security36 notices, service interruptions, and application or administrative37 consequences.382. Query Calendar with explicit timezone-aware bounds from the start of today39 through the next seven days. Show today in detail and flag notable upcoming40 commitments or conflicts. Page only inside that same bounded window when41 necessary.423. Query Todoist for the authenticated current user's overdue, today, and43 seven-day upcoming tasks. Report an empty state without inventing work.4445## Write the brief4647Use these sections in this stable order:48491. `Today at a glance`502. `Attention now`513. `Calendar`524. `Tasks`535. `FYI`546. `Suggested actions`557. `Coverage and caveats`5657Keep scheduled output concise. Limit `Attention now` to five items and `FYI`58to three. For every attention item, state its source, time or date, why it59matters, any known deadline, and the recommended next step. Number suggestions60and phrase them as proposals for an interactive follow-up.6162Redact verification codes, credentials, full account identifiers, and63unnecessary sensitive details. For financial or security alerts, recommend64direct verification rather than taking action.6566## Coverage failures and recurrence6768If one connector fails or is unavailable, still finish a partial brief, name the69missing source, and do not substitute web search. State the bounded coverage and70avoid unsupported claims such as "the only urgent email." Re-read live sources71on every run; repeated unresolved items are acceptable. Never suppress an item72solely because conversation history says it was previously seen.
jialuohu