Digest output may expose calendar information to the agent session and logs
Source references: 4The command reads and outputs the week's calendar agenda while summarizing unread Gmail. Meeting titles, participants, or schedules may be sensitive work information, but the documentation does not identify the calendar fields returned or offer a redaction option.
When run, digest content could appear in chat transcripts, terminal history, automation logs, or output visible to a calling service. The operation can broaden access to sensitive schedule information even if it does not modify Google data.
The documentation confirms that the command outputs a weekly meeting agenda and a Gmail triage summary, so its results may contain sensitive work information. “Read-only” only means it does not modify data; it does not constrain what is displayed. However, the supplied source neither defines the calendar/email fields nor shows that output is persisted in logs, so the claimed log exposure cannot be confirmed. Users can ask for an exact output schema and redaction/minimization controls, and restrict session retention and output sharing.
This assessment concerns the code and conditions shown, not proof that harm has occurred.Weekly summary: this week's meetings + unread email countShow 3 other places
```bashgws workflow +weekly-digest```- Read-only — never modifies data.- Combines calendar agenda (week) with gmail triage summary.- Read-only — never modifies data.- Combines calendar agenda (week) with gmail triage summary.