Sesh Docs
sesh.codes
↑↓ to move↵ to openesc to close
Guides › Review and push changes
Docs › Guides

Review and push changes

See what the agent changed, send feedback, and open a pull request without leaving Sesh.

Every session on its own branch has a Changes view: what the branch changed, its commits, and buttons to push it and open a pull request. It updates as the agent works.

Open Changes

Click Changes (±) in the session’s toolbar. Click it again to go back to the chat.

The Changes view, with changed files on the left and a diff on the right

The bar at the top says where the branch stands, like “3 commits ahead of origin/main · 1 behind · pushed”.

  • Files lists everything the branch changed, committed or not. Pick a file to see its diff.
  • Commits lists the branch’s commits. Expand one to see its files.
  • Use the icons to switch between a list and a folder tree, and between inline and side-by-side diffs. Sesh remembers both.

Send feedback to the agent

  • Select code in a diff and click Send to Agent. The lines go into your message, labelled with the file and line numbers.
  • Right-click a file and choose Send File to Agent to mention the whole file.

Either way Sesh switches back to the chat so you can finish your message.

Push and open a pull request

  1. Click Push to push the branch.
  2. Click Create Pull Request. It opens the new pull request page on GitHub, GitLab (Create Merge Request), Bitbucket, Azure DevOps, Gitea, Forgejo, Codeberg or Tangled.
  3. Its menu has Open Branch and Open Repository.

Pushing uses that machine’s own git login. If it fails, open File › New Terminal on the machine and run gh auth login, or add an SSH key there.

Catch up with the base branch

When the base branch has moved on, Sync appears. It merges the base into the session’s branch. It never rebases, so it’s safe after you’ve pushed.

Sync needs everything committed first.

If the merge has conflicts

Sesh stops and lists the files. Then:

  • Ask the Agent to Resolve sends the agent a message to fix them and finish the merge.
  • Open Terminal to fix them yourself.
  • Abort Merge to undo the sync.

Good to know

  • You can’t stage or commit from Sesh. Ask the agent to commit.
  • There are no inline review comments yet. Use Send to Agent instead.
  • Changes refreshes when the agent does something, not when you edit files yourself. Switch away and back to refresh.
  • Self-hosted Bitbucket Server isn’t recognized. Set the forge in .sesh/config.json.
  • Sessions that work in the folder, without New branch, show only uncommitted changes, and can’t push or sync.