Do I still need the command line?

Innesta drives the same git binary your terminal does, so the two are not alternatives — they are two ways into the same repository, and you can switch between them mid-task without anything having to be reconciled.

What Innesta is better at

Reading. A diff with syntax highlighting and the changed range picked out inside the line, a graph that keeps each line of development in its own lane, a search across every commit message that runs against a local index, and blame with a way to step backwards through it. None of that is impossible on the command line and all of it is slower.

Also: the things that are safe here and are not there. Discarding, resetting and deleting a branch all take a backup first, and a force push is always --force-with-lease.

What the command line is still for

The operations Innesta does not have, listed under what Innesta does not do — interactive rebase, cherry-pick, submodules, git worktree. Innesta will show you the state of a cherry-pick or a rebase that something else started, and resolve its conflicts.

And anything scripted. A one-off is faster in an app; a hundred repositories is faster in a for loop.

Getting between them

The innesta command opens the repository you are standing in. Going the other way, a repository row can copy its path or reveal itself in Finder.