Warp: Git Context Chips Now Available in Remote SSH Sessions
WarpWarp extended its git context chips to remote SSH environments, bringing branch status, uncommitted file counts, and pull request information directly into the terminal prompt when working on remote machines. Previously these chips only worked in local sessions; developers on remote hosts had to run manual git status commands. The feature activates automatically for any repository accessed through Warp's SSH extension, with real-time git status streaming from the remote host to the client.
Sources & Mentions
2 external resources covering this update
Git Context Chips Come to Remote SSH Sessions
Warp has extended one of its most-used developer productivity features, git context chips, to work inside remote SSH sessions. The update brings live branch status, uncommitted file counts, and pull request information directly into the terminal prompt when working on remote machines, eliminating the need to run manual git status or git branch commands mid-session.
What Are Git Context Chips?
Git context chips are the small inline indicators that appear in Warp's terminal prompt, surfacing repository state at a glance. They show the current branch name, the number of staged and unstaged changes, and whether an open pull request is associated with the branch. Before this update, chips were computed locally and had no awareness of remote repository state when connected over SSH.
What Changed
Warp extended its internal GitHubRepoModel to support streaming git status from a remote host back to the Warp client. A new remote-aware git model queries the repository on the SSH host and sends structured state updates over the existing SSH extension channel. The PR chip, which surfaces open pull requests tied to the current branch, now also works when the remote repository has a configured GitHub remote origin.
The change required no new configuration. Any repository accessed through Warp's SSH extension automatically receives the updated git chip behavior.
Why It Matters for Remote Development
Developers who spend significant time on remote servers, whether staging environments, cloud dev boxes, or production-adjacent hosts, previously lost Warp's git context the moment they opened an SSH session. Switching between local and remote workflows meant losing prompt-level awareness of repository state.
With this update, the experience is consistent regardless of where the repository lives. A developer working on a remote EC2 instance or a cloud workstation sees the same branch name, dirty file count, and PR status chips as they would locally. This is part of a broader Warp effort to close the gap between local and remote terminal experiences, ensuring that SSH sessions are first-class citizens rather than degraded fallbacks.
No Configuration Required
The feature activates automatically when connecting through Warp's SSH extension. There are no new settings to toggle and no agent to install on the remote host. Existing SSH connections pick up the change on the next session refresh.