<aside>

roadmap

Phase 1 — GitHub abstraction (no AI yet)

Activity feed, notifications digest, “attention” panel, deep links to GitHub only when action is needed.

Phase 2 — AI brief + Q&A

Weekly summary + NL queries over metrics via AI Gateway; one model, structured prompts, rate limits per user.

Phase 3 — Proactive monitoring

Rules + AI: stale PRs, inactivity nudges, regression alerts on cycle time / commit frequency.

Phase 4 — Multi-remote (optional)

GitLab/Bitbucket if you want “not GitHub” literally — same sync pattern, different adapter.

</aside>

1. Activity inbox (not another dashboard)

A single feed across tracked repos:

• commits, PRs opened/merged, reviews requested, CI failures (later)
• grouped by “needs you” vs “FYI”

This is the clearest “I don’t want to open GitHub” win. Your webhook + sync worker architecture already supports it; you’d add event models and a feed API.

2. AI weekly brief (best first AI feature)

Use Vercel AI Gateway for a structured weekly summary from data you already compute:

• “You merged 8 PRs; cycle time down 22%”
• “Most active repo: X; quietest: Y”
• “3 PRs waiting on review > 48h”

Ground it in Mongo aggregates (metrics.js, commit/PR collections), not open-ended repo browsing. That keeps cost down and reduces hallucinations.

3. Natural-language questions over your metrics

Examples:

• “Am I shipping faster than last month?”
• “Which repo has the worst review turnaround?”
• “When was my last commit on project X?”

Translate to your existing aggregation queries (or a small set of query templates). AI maps question → query → narrative answer. Much more reliable than “ask anything about my codebase.”

4. Focus / attention layer

For vibe coders context-switching between repos: