The cursor blinked.
The terminal waited.
And there it was — git rebase frozen mid-flight, demanding:
Stopped at <commit>.
You can amend the commit now, with
git commit --amend
Once you are satisfied with your changes, run
git rebase --continue
Then:
error: cannot run vi: No such file or directory
error: cannot run editor: No such file or directory
could not start the editor
Or worse —
fatal: cannot run interactive rebase without a tty
If you’ve ever seen Git Rebase TTY errors, you know they break the flow. You were halfway through cleaning history, rewriting commits, or fixing a pull request, and suddenly you’re dealing with TTY sessions, shell environments, and editor configs.
Let’s break it down.
What the Git Rebase TTY Error Means
When you run an interactive rebase, Git tries to open your configured text editor inside a TTY — a terminal session Git can control directly.
If Git runs in an environment without a TTY, the command stalls or fails. That often happens in CI pipelines, automated scripts, or remote executions that don’t allocate interactive shells.
Interactive rebases require user input. Without a TTY, Git can’t prompt you to edit commit messages or resolve conflicts, so it bails out.
Common Causes
- Running
git rebase -i inside a script without --no-tty - SSH connections without
-t or -tt to force allocating a pseudo-terminal - CI/CD systems where standard input is not interactive
- Misconfigured
$EDITOR or $GIT_EDITOR variables - Using Docker containers without
-it flags for interactive terminals
How to Fix It
1. Allocate a TTY in SSH
ssh -t user@host git rebase -i HEAD~3
2. Force a TTY in Docker
docker run -it repo-container /bin/bash
3. Specify an Editor Without Prompting
GIT_EDITOR=true git rebase -i HEAD~3
(This will skip opening an editor and use defaults — works for automated flows.)
4. Non-Interactive Rebase
When rewriting history automatically:
git rebase --no-interactive
Best Practices for Avoiding Git Rebase TTY Errors
- Always test scripts locally with
--no-tty when targeting headless CI environments - Use
--autosquash and --exec for automated history cleanups without manual edits - Lock in
$GIT_EDITOR to a known bin path instead of relying on environment defaults - For containers, always combine
-it flags to preserve shell interactivity
git rebase is one of the sharpest tools in modern version control. When it halts with a TTY error, momentum slips away. With the fixes above, you can keep moving — whether in a dev shell, CI pipeline, or container runtime.
The moment your workflow clears that friction, commits rewrite clean, branches merge fast, and code moves to production without wasted motion.
If you want to see what no-friction workflows feel like, where every rebase, merge, and deploy happens in clean, interactive terminals in the cloud, check out hoop.dev. You can be live in minutes.