repo-control

A local-first command center for multi-repository workspaces.

When work spans several repositories, the important state is scattered across terminal tabs, Git clients, Docker commands and local AI-agent sessions. repo-control turns one workspace folder into a live operational view: what is clean, what is drifting, what needs attention and which action is safe to run next.

Dashboard → repository catalog → Ctrl+P search → repository overview → branches → persistent terminal → Task Engineering. Captured from the live v0.7.0 application with local paths normalized; click the GIF for the full-quality video.

The problem

A normal multi-repository workflow creates three recurring costs:

• State is fragmented. Dirty trees, ahead/behind branches, recent activity, running containers and agent conversations live in different tools.
• Context switching is expensive. Routine work means repeatedly finding a folder, opening a terminal and reconstructing the repository context.
• Automation can become unsafe. Broad scripts are fast, but a command executed in the wrong directory can be destructive.

repo-control keeps the convenience of a dashboard without moving control to a remote service.

Without repo-control	With repo-control
Inspect repositories one at a time	Triage the entire workspace from one live health view
Rebuild context before every command	Open Git, branches, terminal and Docker already scoped to a repository
Search each AI