Connect from Dayflow
- Open Settings → MCP / CLI in Dayflow.
- Find your installed assistant and click Connect. If it already says Connected, leave the connection in place.
- Restart the assistant so it loads the connection.
- Ask it to check Dayflow's status before reading your timeline. Use the specific date you want rather than an ambiguous “yesterday.”
Dayflow saves the connection in the client's user configuration, making it available across projects on this Mac. The bundled helper stays with the app; installing a separate npm package is not required.
What we verified
- Codex: the existing connection returned live Dayflow status and a weekly rollup.
- Claude Code: The existing connection successfully called Dayflow’s status tool. Use the weekly report workflow to prepare a reviewed draft.
- Claude Desktop, Cursor, and VS Code: Dayflow exposes connection options, but these clients were not tested end to end for this guide.
Read access and edits are different
For a report, turn Allow edits off. Read tools can retrieve the timeline, activity details, daily documents, and weekly totals. Enabling edits also lets supported tools change activity titles, categories, and day goals. Do not enable it merely to summarize your week.
Local storage does not make an assistant conversation local. Information retrieved by a cloud assistant enters its context. See what crosses that boundary.
Start with one useful question
Try: “Use Dayflow to list my work on [date]. Separate confirmed facts from uncertain outcomes. Do not edit anything.” For a longer update, use the Codex work-summary workflow.
If you prefer to choose exactly what to share, export Markdown and select the relevant text yourself.