Skip to main content
Keep one short project brief where you already work, such as a private Markdown folder or Obsidian vault. Screenpipe supplies recorded context; your chosen AI turns that evidence into a brief that you and other assistants can read tomorrow. This recipe works best for a defined project. Start with one source and one file before adding email, Slack, or a task database.

​
Decide which tool does what

You can keep using Claude, Codex, or another assistant for your main work. Connect it through MCP to retrieve history, or generate the brief in Screenpipe and open it in your existing workflow. The brief does not restore a model’s hidden conversation state.

​
Create one manual brief

Replace the placeholders and paste this into an assistant that can access Screenpipe history. A file-capable assistant can save the result; otherwise copy the returned Markdown into your notes.

​
Example brief

This is fictional data showing the expected structure:

​
Add email or Slack only when needed

Recorded messages show what was visible at particular moments. They do not establish complete mailbox or channel history. For current communication status, use an available connection and check the original conversation.
Verify the integration before adding it to a recurring task. A failed connector should produce a visible gap, not an invented “no reply” conclusion.

​
Make the next update incremental

After reviewing a manual brief, test a second update over a later interval:
Reopen the brief and check that the same decision or task was not appended twice. For hourly updates, process the new hour; for a morning brief, choose the prior workday or another explicit source window. Do not assume the time a report runs is the period it should summarize.

​
Schedule after it works

Use reliable reports to create the recurring scheduled task, select its timezone, verify its first scheduled output, and add a completion receipt. Review AI usage before increasing frequency. For Obsidian, choose a folder inside the existing vault and verify that the file appears there. Check whether that vault or folder syncs elsewhere before treating a saved note as local-only. Keep internal evidence separate from anything you share with a client. For a longer-lived knowledge base used by several agents, continue with local agent memory.