Repository navigation
SOCIALCODE101: home feed from line events, with bring-your-own agent digest #528
Description
Part of the SOCIALCODE101 series. Depends on the follows issue.
GitHub's feed is sporadic because it only has commits and stars. Every codeSplitters line carries author, time and rev, blamed on a person or an agent run, so the feed can be line-level.
Build
- A home feed built from line events of everything you follow, grouped per person or agent run: "ry landed 40 lines in hono/router.ts, 3 agents touched it after." Reuse the activity rail's grouping (features.json
activity). - Bring your own summarizer: point one of the existing harnesses (claude, codex, pi, opencode via agent-run.ts) at your feed and it writes the digest. Summaries are the default view; the raw events sit one click behind each one. Agents never get events from repos you can't read.
- A
feedMCP tool andGET /api/me/feed?since=so an agent elsewhere can read it too. - Private repos contribute only to their crew's feeds.
Activity
codeSplitters: follow people, agents, repos and line ranges (#527) (#535
codeSplitters: home feed from line events, with a bring-your-own agen…
QuinnsCode commentedon Oct 11, 2026
From #530: two inputs for the feed.
stampstable (src/stamps.ts):recentStamps(env, viewer, who, "by" | "author")already filters to repos the viewer may read.authoris who wrote the line, person or agent.agent_runs.agentis the actor (agent-claude),owneris who started it.agentProfileinsrc/actors.tsreads runs the same way.QuinnsCode commentedon Oct 11, 2026
Follow-ups from a sweep: digest access on the hosted site is #575, and the click-through is in #574.