you have access to screenpipe, a local tool that records everything i see, say, and
hear on my computer and makes it searchable. i want you to build and maintain a
"second brain" about me — a living memory of who i am, what i'm working on, and how
i work — by watching my activity through screenpipe in the background, so i never
have to re-explain my context. think of it as a digital clone of my working context.
## how to read my activity
if you have the screenpipe MCP tools (search-content, activity-summary, list-meetings,
update-memory), use them. otherwise query the local REST API at http://localhost:3030
(or http://SCREENPIPE_IP:3030 if i run screenpipe on another machine):
- recent activity: curl "http://localhost:3030/search?content_type=all&start_time=START&end_time=END&limit=100"
- light summary: curl "http://localhost:3030/activity-summary?start_time=START&end_time=END"
- meetings: curl "http://localhost:3030/meetings?limit=20"
START / END are ISO 8601 UTC timestamps. start with a small window (the last 1-2 hours)
so you don't pull too much. if screenpipe skills are available, load them first.
## what to do each run (about once an hour, or when i ask)
1. SEGMENT — pull my activity since you last ran and split it into distinct work
sessions. a session is a coherent block of related activity (e.g. "45 min in cursor
refactoring auth", "30 min reviewing investor follow-ups", "1h call about X").
note the app(s), the time range, what i was actually trying to do, and the goal.
2. SUMMARIZE — for each session write a short summary of the *process*: the steps i
took, the tools/inputs/outputs, the decisions i made, and whether it's repeatable.
if it looks repeatable, capture it as a numbered SOP i could hand off or automate.
3. REMEMBER — update my second brain with anything durable and reusable:
- who i am: role, goals, preferences, recurring tools
- people i interact with and about what (tag person:NAME)
- projects in flight, their status, open loops (tag project:NAME)
- workflows / SOPs i repeat (tag topic:NAME)
store only stable, reusable facts. never store secrets — passwords, API keys, tokens,
financial or health data, or anything clearly private. skip one-off noise.
## where to store the second brain
- if you have the screenpipe update-memory tool: write each durable fact as a memory
with namespaced tags (person:, project:, topic:) and importance 0-1. retrieve later
with search-content content_type='memory'. this is the same memory the screenpipe
digital-clone pipe builds, so it stays queryable from any agent.
- also (or instead, if you lack that tool) keep markdown files i can read:
second-brain/profile.md - who i am, goals, preferences
second-brain/people/NAME.md - one file per person
second-brain/projects/NAME.md - one file per project, with open loops
second-brain/workflows/NAME.md - repeatable SOPs
second-brain/log/DATE.md - the hourly session summaries (append-only)
second-brain/now.md - what i'm doing right now and over the last
~30/120 min, refreshed every run
always APPEND and DEDUPE: update existing entries instead of duplicating them, and
link related notes together.
## run on a schedule
set this to run automatically about once an hour using whatever scheduling you have
(claude tasks, codex automations, openclaw/hermes automations, a system cron job, or a
screenpipe pipe — `npx -y screenpipe@latest pipe install <path>` then `... pipe enable <name>`).
between runs, when i ask you anything, read now.md and the relevant project/person
files first so you already know what i was doing.
start now: do one pass over my last 2 hours, then tell me what you learned about me
and propose the schedule.