Session panel
The panel beside your terminals: changes, pull request, review, ticket, app and files for the session you are in.
The session panel is the tabbed panel on the right of a project. It follows the session you are working in: the worktree of the terminal you have focused, or the worktree you selected in the sidebar when no terminal has focus. Switch terminals and the panel switches with you.
Toggle it with the File Changes button in the tab bar or with Ctrl+Shift+F. It is open by default. Drag its edge to resize it, and double-click the edge to go back to the default width.
Tabs#
| Tab | What it shows |
|---|---|
| Changes | The worktree's changes, staging, commits, push and pull. See File changes. |
| PR | The branch's pull request: checks, review, comments, conflicts and merge. |
| Review | The AI reviewer's verdict and findings. See AI review. |
| Ticket | The ticket the session was started from. |
| App | Your build & run configs: start, stop and read the log. |
| Files | The worktree's file tree. See Files and the in-app editor. |
Choose which tabs you see with the + button at the end of the tab row. Tick the tabs you want, drag them to reorder (or use Alt+Up and Alt+Down), and turn on Icons only for a narrower row. Files is hidden until you tick it. Your choice, the order and the panel's width apply to every project.
A tab can carry a status of its own: PR has a red, amber or green dot for the state of the pull request, Review has a dot while a review runs and when it is in, App turns green while an app runs, and Changes counts the changed files.
PR#
With no pull request yet, the tab offers Create PR on GitHub, which opens GitHub's compare page, and Ask the agent to create it. If the branch has commits that are not pushed, Push and create on GitHub does both.
With an open pull request, the tab sums up whether it is ready to merge, and lists what stands in the way:
| Row | What it tells you |
|---|---|
| CI checks | Failed, running, passed, or none. |
| Review on GitHub | Approved, changes requested, or not yet. |
| Comments | How many review threads are unresolved. Show lists them, with outdated threads marked and a link to each. |
| Branch | Conflicts with the base branch, behind it, or up to date. |
The pull request's description is at the bottom of the tab.
Asking the agent
Where a row needs work, a button hands it to the agent: Ask the agent to fix for failing checks, Ask the agent to address it for review comments, Ask the agent to resolve for conflicts and Ask the agent to update for a branch that is behind. Tegment types a prompt into the agent's terminal and sends it. The buttons show only when the focused terminal runs an agent.
The same fixes are in the right-click menu of a session in the sidebar, as Resolve conflicts, Update branch and Fix failing checks, when its pull request needs them.
Merging
Merge from the tab with the methods the repository allows: Squash and merge, Create a merge commit or Rebase and merge. Tegment asks you to confirm first, since a merge can't be undone, and warns you when checks that aren't required have failed. The merge applies to the commit the tab shows, so a push that lands while you confirm isn't merged unseen.
Merge is unavailable, with the reason beside it, while the pull request is a draft, has conflicts, is behind, is blocked, or is still being checked. If GitHub is set to delete branches after a merge, the tab says so.
Ticket#
The ticket the session was started from, with Open at source to open it in GitHub or Jira.
Mark done checks the ticket off your project's To do list, and Move back puts it back. For a ticket that isn't on the list, or a session without a ticket, the same button marks the session itself done. A session marked done stops showing pull request notes in the sidebar.
App#
Start any of the project's apps in the session's worktree, and follow a running app in a card with Stop, Restart and its log. With no apps set up yet, the tab offers to add one, including commands it found in the project.
In the sidebar#
A session in the sidebar says when its pull request needs you, on the line under its name: Conflicts with the base branch or The checks failed. Conflicts win, since the checks often can't run properly until they are resolved.