Tab · Knowledge

Brain reflection

● New · shipped 2026-05-29

The reason your second project goes faster. Every night at 2 AM — registered with your OS scheduler (Windows Task Scheduler, launchd, or systemd) so it runs whether or not the dashboard window is open — RepoOps reads the day's sessions, prompts, errors, and decisions, then proposes the lessons worth keeping. You review, accept, and the next morning your CLAUDE.md already remembers.

See it in motion

Where to find it

  • Localhost: http://localhost:4000/brain-reflection.html?repo=<id>
  • Hosted (team): repoops.ai/team/brain-metrics — the four KPIs across all bound devices.
  • Keyboard: ⌘ K then reflect. The > Reflect now palette verb forces an on-demand run.
  • Sidebar: Knowledge → Brain reflection (first item).

What it does for you

Your AI stops forgetting.The overnight reflector reads your sessions, prompts, errors, and decisions — then proposes lessons worth saving. Accepted lessons regenerate into a managed block in CLAUDE.md and AGENTS.md on the next run. The next session walks in already knowing.
You stay in the loop.Nothing lands automatically. Every proposal carries a confidence band and a triggering event, plus one-click accept / reject / edit. Accept-all-high handles the obvious ones in batch.
Recurring defects get rules.When the same error fingerprint hits twice in a week, the reflector proposes a prevention rule. Accept it once; you won't see that defect a third time. (This is how the "auto-promoted Lessons" entries in your CLAUDE.md got written.)

Configure

Reflection is opt-in and runs locally. It requires a BYOK Anthropic key (it's the only LLM call this tab makes) and a small amount of wall-clock at 2 AM local.

  • ANTHROPIC_API_KEY — required. The reflector uses Claude Sonnet for proposal drafts. With no key, it degrades to a deterministic fingerprint pass (recurring-defect rules still ship).
  • REPOOPS_BRAIN_DREAM — kill switch (set to 0 to disable). Or use the brain.dream.auto KV flag.
  • Settings → Brain pulse — toggle the 02:00 cron and the hourly check.
  • brain.last_dreamed_at:<repoId> — per-repo bookkeeping. Deleting it forces a re-run on the next tick.

Use it well

  1. Open Brain reflection first thing each morning.

    The Today cockpit's "Brain pulse" tile is your breadcrumb — it'll tell you when there's new material to review.

  2. Read the proposal, check the triggering event.

    Each card carries the event that fired it — an error fingerprint, a decision recorded, a pattern recurrence. Click it to see the raw signal.

  3. Accept what captures a rule you'd want a teammate to follow.

    For obvious wins (typo fixes, formatting rules, naming conventions), use Accept all high. Reserve manual review for proposals that touch architecture or process — those benefit from your edit.

  4. Rejected proposals are remembered.

    The reflector won't propose them again. If you reject by mistake, the proposal will reappear after the next event that fires the same fingerprint.

Examples

✓
A typical accept cycle
Morning: open Brain reflection. 3 proposals overnight. Two are high-confidence formatting rules — Accept all high. One is medium-confidence"migrate fetch calls to the new client" — edit the wording to add the boundary ("only inside app/api/"), accept. Close the tab. Next session, CLAUDE.md already carries all three.
⚠
When the reflector is wrong
Reject loud and early. The reflector reads what you reject to bias the next night's proposals away from the same shape. A noisy reflector is the symptom of a brain that needs pruning — open Patterns / Errors and clean the sources.

Read more