Saggar: a terminal built around the work
I've been building Saggar, a standalone terminal app shaped around projects rather than a pile of disconnected windows.
The video is a little out of date, and some of the language has changed, but it's still the quickest introduction to how Saggar works.
The small things I keep using
Saggar has plenty of features, but my favorites have turned out to be three of the smallest:
- Quick Command (
Cmd + P) runs a command, then disappears if it succeeds. - Monitor view (
Cmd + Shift + M) runs a command and sticks around, so I can keep an eye on it. - Run next queues another terminal to open when I close the current one.
None is revolutionary on its own. Together, they remove a surprising amount of friction from the loop of starting something, checking it, and moving on.
Why a standalone terminal?
The integrated terminal in an IDE is convenient. That's the bar Saggar has to clear.
My bet is that a dedicated app can earn its place by treating the repository as the project, keeping related terminals together, and making common terminal jobs faster to start and easier to follow. The question is whether that extra focus is useful enough to pull you out of the IDE.
I know my own answer because I've been using Saggar for a while. I'm much more interested in yours.
What I want to learn
If you try it, I'd particularly like to know:
- Does the core model feel intuitive, especially the idea that a repository is a project?
- If you usually use your IDE's integrated terminal, does Saggar offer enough focus or speed to justify a separate app?
- Should Saggar have first-class Git features, or is ordinary terminal Git support enough?
I'm currently working most on the remote control experience, so feedback there is useful too.
Try Saggar and let me know how you get on. You can also send feedback through this short form.