One tab for every repo, container and AI session on my machine
My working day spans about ten Git repositories. Here is where their state actually lived: which trees are dirty → forty terminal tabs which branches are behind → a Git client, pointed at one repo at a time which containers are up → docker ps the AI conversation I had yesterday about the retry policy → somewhere under ~/.claude/projects , in a folder named after a path So I built repo-control .…
I have built a tool called repo-control to help me manage my ten Git repositories more effectively. The dashboard it provides shows me what needs my attention across all of them. It lists unhealthy containers, failed automations, repositories that require pulling or committing, and the ones that need a push. Clicking on a row takes me directly to the relevant repository, already scoped within that context.
Each repository is given its own workspace with features like inline diffs, staging, committing, fetching, pulling, pushing, viewing branches with divergence, and opening a terminal that remains active even when I switch to a different repository. The tool also displays the state of Docker Compose files if there are any. For my AI sessions, repo-control reads the histories of Claude Code, Codex, and Gemini CLI from disk, keeps only those related to the current workspace, and resumes any of them in a real terminal within the correct directory, with the appropriate command-line interface.
All of this happens without any data being copied or sent to the browser. The browser sends only a repository ID, which the server uses to resolve the location against the root directory scanned by repo-control. This approach ensures that no sensitive information is exposed. Repo-control is not meant to replace team collaboration tools or handle complex tasks like rebasing or conflict resolution, as these are better handled within my preferred editor.
It does not interact with the GitHub API, as it relies solely on git, Docker, and the files present on my disk. The tool is open-source and available under the MIT license on GitHub at github.com/LorenzoVicino/repo-control. Now, I would appreciate hearing more about how I might improve my workflow. Across all my repositories, what state tends to slip my mind the most?
Is the one queue of "what needs you" an effective way to present this information on the front page, or would you suggest a different approach? Lastly, what feature would make me feel comfortable closing the repo-control tab within the first minute of opening it? I am eager to hear your thoughts, as I have already established a system for managing ten-plus repositories and would prefer to hear about your experiences rather than just a recommendation.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
