Quickstart
Ten minutes, one repo, one worktree. Everything below happens on your machine.
Your first worktree
Open Strado. A fresh install asks you to name your first workspace and pick an accent color. The icon is derived from the name, and everything is editable later.
Add a repo. Paste the path to a git checkout — in the desktop app you can pick
the folder instead. The server inspects it and fills in the git root, the start
command, the dev-server port, and any .env profiles it finds, so you review a
prefilled form rather than typing one.
Create a worktree from the + that appears next to the repo in the sidebar
when you hover it. Give it a title and, if you use a
tracker, a ticket id. Both are combined into the branch name and the directory
name: ticket FD-12 and title fix header become FD-12_fix_header. Pick the
branch it starts from and Strado creates the worktree, links node_modules
from the source worktree, and registers it — with named progress steps as it
goes.
Open its hub. Clicking the row opens that worktree's hub with a shell in it. The hub carries a super-tab per worktree and sub-tabs for that worktree's sessions.
Start a Claude Code session from the + in the tab strip. It runs in the
worktree's directory and is owned by a daemon, not by the window — closing the
app leaves it running.
Start the dev server from the start button beside the run dot at the right end of the board row. The port is taken from the repo's default and moved up past any port another worktree has already reserved, unless the repo is pinned to a fixed port.
Open the diff. The Changes cell in the row shows files, additions and deletions; clicking it opens diff and commit, where you stage or discard down to the hunk and commit without leaving Strado.
What just happened
You made a git worktree, and Strado wrapped it in everything a branch needs to
be worked on independently: its own directory, its own node_modules, its own
dev-server port, its own agent and shell sessions.
Nothing was stashed and nothing was switched. The next worktree you create sits next to this one, on its own branch, running its own server. That is the whole model — the rest of the app is ways to see and drive it.
Where to go next
- Workspaces — what a workspace owns
- Repos and worktrees — the directory convention, linking, adopting, deleting
- The board — what each row is telling you
- The hub — tabs, the preview browser, embedded VS Code