Git

A full git client beside the chat: stage, commit, branch, and read the history.

Source and History

Source stages and commits. Changes are staged by file or by hunk, so a commit can carry one part of a file and leave the rest, and commit messages can be written for you from the staged diff.

History draws the commit graph, and any line can be traced with blame to the commit that last touched it.

Branches, worktrees and conflicts

Branches are switched from the panel, and Worktrees lists every branch checked out beside the main one, each in its own folder. See Worktrees.

Work in progress can be stashed and restored. When a merge conflicts, the panel says so and shows the conflicted files rather than leaving you to find them.

With a provider connected

Connect a git provider and the panel gains PRs, Issues, Pipelines and Releases alongside the local views. A project that is not on a remote yet can be published to GitHub from here.

Reviewing changes

The Git panel shows all changed files with full diffs. After Panda makes edits, you can inspect every modification before deciding what to commit. This is your safety net: AI-generated code should always be reviewed, and having the diff viewer right next to the chat makes review frictionless.

You can also switch branches, pull upstream changes, and push commits, all standard Git operations available without leaving the workspace.

AI-generated commit messages

Writing good commit messages is one of those tasks everyone agrees is important and nobody wants to do. PandaOS solves this by reading the staged diff and generating a clear, conventional commit message that accurately describes what changed.

The generated message is grounded in the real diff, not a guess. It summarizes the actual modifications: "Add input validation to user registration form" instead of "wip" or "fix stuff." You can use it as-is or edit it before committing. Over time, this keeps your Git history readable and useful for future you and your teammates.

Publishing your work

Once committed, push your changes to the remote to share them with your team or trigger CI pipelines. The full Git workflow, from staging through pushing, lives inside the workspace alongside the chat, file explorer, and terminal.

For working with files and running commands alongside the Git panel, see Files, Terminal & Browser.