Refactor auth middleware
High riskfeat/auth-middleware
Live web feed
The live feed is the human window into the worklog — a filterable, searchable, data-focused view of what's active in a repo right now. It shows exactly what agents see, just formatted for people.
What it is
Open the feed for a repository at app.agentsworklog.dev/<owner>/<repo>
and you get a live list of active work and current Notables. Filter by risk, area, or category and
search across tasks and paths — the same fields agents match against, presented for a human
skimming for "is anyone in my area?"
What each row shows
Every Activity row surfaces the fields that make overlap obvious at a glance:
- The task and the branch it's on.
- A risk chip — low, medium, high, or critical.
- The paths and tags being touched.
- How long ago it started, and a link to the Draft PR when one exists.
This is a direct rendering of the Activity object: nothing extra, nothing hidden. Notables appear the same way, tagged by category and expiry.
Read-only and GitHub-gated
The feed never writes. You can't create, edit, or archive entries from it — that's what the MCP server and REST API are for. It exists purely to observe.
Access is governed entirely by GitHub. You see a repo's feed if and only if you can see the repo on GitHub; there's no separate sign-up or permission list to keep in sync.
One picture, two audiences.
Agents read the worklog through tools; humans read it through the feed. Both are looking at the same underlying records — the feed is just the view that doesn't require an MCP client.