Fido is a launch manager for your IDE — JetBrains Rider, WebStorm, VS Code, Visual Studio, Zed, or any custom editor.
Give it a branch name; it scans your repos for every worktree and clone currently on that branch, lists them right on the main screen — clearly labelled — and opens your pick's solution or folder in your editor. Set a default tool for the big Open button; every tool is a Ctrl+1 … Ctrl+9 away. It can also drop you into a terminal or open the folder in your file explorer — on Windows, macOS, and Linux. Finished with a branch? Delete its worktree and local branch from the same screen, with an inline confirm.
Fido? GO! — branch resolved, worktree located, editor launched. The Eagle has landed.
Fido pre-fills its form from the command line, and giving it a branch starts discovery immediately — the same flow as typing the branch. Name a tool too and Fido auto-opens it, but only when the branch is checked out in exactly one place; multiple locations are presented for you to choose, never guessed between:
fido feature/new-ui # scan for the branch and show every location
fido feature/new-ui rider # …and auto-open in Rider if there's exactly one
fido feature/new-ui -s MyApp # …with the solution chips filtered to MyApp
fido feature/new-ui term # open a terminal on that branch (files = file explorer)
fido -b feature/new-ui -s MyApp -t vs # the same, with explicit options
Each tool has a short slug (built-in: rider, vsc, vs, zed, plus term for a terminal and
files for the file explorer) that you can pass as the second argument — or explicitly with -t /
--tool (also -e / --editor) — and the built-in kinds answer to aliases like vscode or
explorer too. The named tool becomes the run's default (the hero button); --tool none shows the
equal-weight grid instead. Slugs are editable in Settings; an unknown id is called out in the
flight log rather than silently using the default. See Features for the
full reference.
Fido ships with matching dark and light themes. Browse the full set — the home screen with its inline discovery results, the delete confirm, and settings — in the screenshot gallery.
When you're juggling a massive project spread across concurrent Git branches, hopping between context switches can feel like navigating through deep space. Finding the right local folder, verifying the worktree, and booting up your IDE takes manual steps you'd rather spend actually coding.
This application completely automates that trajectory. You give it a branch name; it automatically calculates the correct local Git worktree path, figures out if it needs to open a solution or a folder, and instantly fires it up in JetBrains Rider.
When looking for a name that captured that exact feeling of calculating a fast path and clearing a launch, we took inspiration from one of mankind’s greatest engineering achievements—and a legendary track that celebrates it.
The name Fido is a direct tribute to the high-voltage track Go! by Public Service Broadcasting (check out the lyrics here).
The song beautifully samples the original NASA archival audio from July 20, 1969. Just minutes before Apollo 11 was scheduled to touch down on the lunar surface, legendary Flight Director Gene Kranz poll-checked his elite White Team of flight controllers to clear the spacecraft for its tense powered descent.
He went "around the horn," calling out the shortened acronyms of the room's console positions, asking if their systems were ready to land:
"Retro? GO! Fido? GO! Guidance? GO! Control? GO!..."
In Mission Control, FIDO stands for the Flight Dynamics Officer.
[Your Branch] ────► [FIDO App] ────► [Rider IDE]
│
(Computes Worktree Trajectory)
The FIDO desk didn't watch a video feed or look out a window. They stared at dark cathode-ray screens filled with real-time mainframe data. Their lone, critical job was to plot the exact path of the spacecraft through space, track its positioning nodes, and compute the vectors required to safely reach the destination.
That is exactly what this tool does for your development workflow:
- The Trajectory Check: It takes your target branch name.
- The Flight Path Vector: It acts as your personal Flight Dynamics Officer, scanning your local directory infrastructure to map out the exact path to the matching worktree folder.
- The Clearance: It verifies whether to spin up the specific
.slnfile or the root directory. - The Launch: It reports back
Fido? GO!and hands off the controls to Rider instantly.
Instead of fighting the terminal or hunting through finder folders to switch contexts, you're just one quick command away from landing safely right inside your code.
"Eagle, we've got you on the data. You are GO for PDI."