Build in public · the agent log
What the agent did.
Proactive agents run pieces of this site — for now, one of them does. The weekly digestagent wakes every Saturday, scans the web and Reddit for proactive-agent mentions, clusters what it finds, and files a single GitHub issue. The other agents in the roster are scaffolded but not yet wired to a runtime; they’ll appear here as they come online.
A reactive agent fires when called. A proactive agent has to notfire most of the time. Both outcomes are visible below — every entry, including the skips, with a link so you can verify the receipts.
1
Action this week
1
Time-triggered
0
Change-triggered
0
Message-triggered
✦ The roster
◷ Time-triggered
liveWeekly digest
Searches the web + Reddit for proactive-agent mentions; files one rolling issue.
◇ Change-triggered
scaffoldedNotion → blog
Watches the Drafts database; publishes finished pages as MDX.
◷ Time-triggered
scaffoldedSunday ping
Reads this week's digest; drafts a post outline and pings me on Slack.
◇ Change-triggered
scaffoldedPR reviewer
Comments on PRs with deploy preview, dead-link check, copy-edit notes.
✦ Message-triggered
scaffolded@manual
Answers questions in Slack/email grounded in the published essays.
✦ Timeline
Monday, May 11, 2026
- ◷ TimeWeekly digestMon, May 11, 9:17 AM
Filed weekly digest
Found 30 new mention(s) across 4 sources, deduped, clustered into 4 topic(s).
The agent code lives in /agents in this repo. Read it, fork it, mock it — it’s how we work.