Project

repobs

Observe repositories and coding-agent activity on a shared timeline, track what needs attention, and keep review annotations locally without modifying Git repositories or agent files.

Period
Oct 2026 – Present
Status
Active
Type
Software · Engineering
Technologies
TypeScript · React · Node.js · SQLite · Vite
  • Developer Tools
  • Git Worktrees
  • Coding Agents
  • Local Software

Problem

When coding agents work across several branches and Git worktrees, repository history and session activity are scattered. It becomes difficult to tell which session belongs to which change, which agents need attention, and what still needs review.

The timeline: branches, commits and the agents that worked on themThe timeline: branches, commits and the agents that worked on them

See Every Branch

Branches, commits, and worktrees share one timeline, so you can follow forks, merges, pending changes, and unpushed work together. Switch between commit order and calendar time, zoom into activity, or fold quiet history.

An agent's details: its status, the evidence and the plan it keepsAn agent's details: its status, the evidence and the plan it keeps

Follow Every Agent

Follow Claude Code and Codex sessions on the branches where they work. Inspect status evidence, spawned agents, recent messages, and step-by-step plans. Missing observations remain Unknown, rather than being treated as idle.

An agent's checklist: the agent's plan first, then your own itemsAn agent's checklist: the agent's plan first, then your own items

Review on Your Terms

Keep review states, tags, notes, and personal checklists alongside each agent’s own plan. Annotation rules help surface sessions that need attention. Your review records stay in repobs, separate from source repositories and agent files.

Local by Design

Repository and agent files are observed without being modified. Review notes, annotations, and settings live in repobs’s own local database. Named views keep their filters and hidden items, and dockable panels let you arrange the workspace around your review workflow.

Technical Details

  • Shared contracts: TypeScript and Zod define the boundary between the Node.js service and React UI.
  • Live observation: file watchers and bounded polling feed a reconciled snapshot; Server-Sent Events deliver changes to the browser.
  • Local persistence: Node.js’s built-in SQLite support stores registered repositories, settings, annotations, and rules.
  • Source isolation: Git inspection uses an allowlist of read-only commands. The service runs on 127.0.0.1; a read-only GitHub pull-request overlay is optional and disabled by default.

Availability

repobs is open source under the MIT license, with Windows-first release packages. The documentation covers installation, a screenshot-based tutorial, status semantics, integrations, architecture, and the HTTP API. The project also includes synthetic demo data for exploring the interface.

Software