Git and worktrees

Open the files and changes pane from the chat header and select Changes. It shows repository status, changed files, and working-tree diffs. File changes reported during an agent turn link to the same review surface so you can inspect the resulting patch without leaving the chat.

Stage a whole file or an individual diff hunk, then create a commit from the staged changes. You can ask Pi to draft commit wording before you confirm it. NativePi does not create hidden commits or checkpoints.

Push the current branch from the Git surface, or fast-forward it from its remote before pushing. The commit graph shows local and remote history. When the GitHub CLI is installed and authenticated, NativePi can open a GitHub pull request through gh.

For the current branch's pull request, NativePi also shows its description, checks, comments, linked issues, and comparison against the base branch. GitHub authentication belongs to your installed CLI.

GitLab projects can display merge requests and issues through an authenticated glab installation. The app's pull-request creation action is for GitHub; create a GitLab merge request with your usual GitLab tools. A branch containing an issue number can show that issue when there is no pull or merge request.

Switch to or create a branch from the files and changes pane when the working tree is clean. Choose Worktrees… from the project actions menu beside the sidebar project filter; NativePi pins that worktree as a separate project so its chats and terminals remain scoped to the correct folder.

Choose Revert on an unstaged tracked file and confirm to restore its working-tree contents from the index. Staged changes remain intact; untracked files are not deleted. This discards that file's unstaged edits and cannot be undone by NativePi.