Skip to content

Fido

A branch name in. Your IDE open on it.

Fido scans your repos for every worktree and clone currently on a branch, lists them on one screen, and opens your pick in Rider, WebStorm, VS Code, Visual Studio or Zed.

Get started See it working

Windows, macOS and Linux · .NET 10 · Avalonia 12

Fido after a successful launch — the flight log reads "The Eagle has landed"

Home

What it does

  • Finds the branch, everywhere it lives

    Git enforces one worktree per branch only within a clone. Fido scans every search root and shows each location as its own card — worktree or main clone, labelled and ordered — so duplicates are visible instead of guessed at.

    Discovery

  • Opens it where you want

    A default tool on the big button, every other tool one Ctrl+1 … Ctrl+9 away — or any shortcut you give it, two-press chords included. Solution chips for .sln, .slnx and .slnf, or hand over the folder — plus a terminal and your file explorer.

    Opening a target

  • Configured by the repo itself

    Commit a .fido/cfg.yaml and Fido reads it off the branch — your uncommitted edit first, then origin, then this machine. A worktree made before the config landed still gets it.

    In-repo config

  • Cleans up after you

    Finished with a branch? Delete its worktree and local branch — and optionally the remote, unless an open PR says otherwise — from the same screen, behind an inline confirm that spells out exactly what goes.

    Deleting a worktree

  • Starts from the command line

    fido feature/new-ui rider resolves the branch and auto-opens — but only when it is checked out in exactly one place. Multiple locations are presented, never guessed between. A window already open on the branch is brought forward instead of a second one opening.

    Command line

  • Runs the branch's scripts here

    A Console tab beside the flight log: a real shell at the selected location, over a real pseudo-terminal. Pick a script from the branch's own config and watch it run — colour, Ctrl+C, and the output still there when it fails.

    The Console tab

  • Points out the leftovers

    The worktree folders a branch already has on disk are listed under the branch box — even when no repo has the branch. Last month's leftover is named the moment you type.

    Discovery

Why "Fido"?

A nod to the Apollo Flight Dynamics Officer — call sign FIDO — whose job was to track the spacecraft and compute its trajectory. Fido does the same for your code: a branch name in, its exact path on disk out. The flight log narrates each step as it goes around the horn, and when your editor comes up, the Eagle has landed.