Do I need GitHub CLI?

Not to commit and push. Pane uses the GitHub CLI (gh) to show pull request status on each pane and to watch a Session's pull requests, and agents use it to open them. Without it, open the pull request on your platform's website after pushing.

Can Pane open the PR for me?

Not with a button. Pane commits and pushes the branch, and the agent opens the pull request with gh pr create or an MCP tool. If you run the work from a Session, its bundled prepare-pr and babysit-pr skills open the pull request and watch its checks for you. Once a pull request exists, Pane's Changes panel can open it.

What about MCP-based Linear integration?

Claude Code supports MCP servers, including one for Linear that lets the agent read issues, update their status and link pull requests. Add it to your agent's MCP config if you want the agent to fetch the issue instead of you pasting it. See the MCP docs for setup.

Guide

Issue to PR

TL;DR

Take an issue from Linear, GitHub or Jira to a merged pull request in nine steps. Create a pane for the issue so the agent works on its own branch, give the issue to your agent, and let it write and test the change. Review the diff in Changes, send follow-ups until it's right, then commit, push and open the pull request. Pane has no tracker integration on purpose: your agent reaches Linear, GitHub or Jira through MCP.

The issue lives in Linear, GitHub Issues or Jira. The agent does the work on its own branch. The pull request ships from that branch. Here's the whole path, from triage to merged.

Walkthrough

Pane per issue, agent does the work, you review, commit, push, open the PR.

1Read the issue in Linear, GitHub or Jira, or let your agent fetch it through MCP.
2Create a pane with Ctrl+N, named after the issue, such as fix/auth-123. Pane makes a worktree on a fresh branch.
3Start Claude Code with Ctrl+Alt+3 (or Codex with Ctrl+Alt+4) and paste the issue as your first prompt. Acceptance criteria, repro steps and file paths save follow-up rounds.
4The agent reads files, writes code and runs tests. A desktop notification tells you when it finishes or needs input.
5Open Changes with Ctrl+Shift+B and click each file to review its diff.
6Gaps, such as missing tests, scope creep or a regression? Switch to the agent's tab and send a follow-up. Repeat until the diff looks right.
7Commit with Ctrl+Shift+K using a message that closes the issue, such as fix: handle empty state in auth form (closes #123), then push with Ctrl+Shift+U.
8Open the pull request: ask the agent to run gh pr create, or create it on the website.
9After review and CI pass, merge. GitHub closes the issue automatically when the pull request description or commit says Closes #123.

Pane showing a diff of src/index.js as a tab and the Changes panel listing three files with Commit and Restore buttons — Changes panel and diff tabsEvery touched file is listed with its line counts. Click one and its diff opens as a tab next to the agent.
1.Diff as a tab: The diff sits next to the agent. Drag it beside the agent to watch both.
2.Unified or split: Switch views in the corner.
3.Commit and Restore: Commit everything, or throw away uncommitted changes, from the list.
4.Open PR: Once the branch has a pull request, this opens it inside Pane.
Pane 2.4.155, after the agent finished

Let a Session do it

Hand a Session the issue, and it runs the steps above in a pane for you.

A Pane Session is an agent that runs other panes. Give it the issue link, and it creates the pane, starts an agent with the issue as its prompt, watches it, and uses its bundled skills to prepare the pull request and watch its checks. It stops and asks you before merging.

Why no first-party Linear integration

Your agent already talks to trackers through MCP; Pane doesn't duplicate it.

Pane isn't a project management tool. Your agent can reach Linear, GitHub or Jira through MCP, the same way it reads your code. To have it fetch the issue, mark it In Progress and link the pull request, add the tracker's MCP server to your agent's config.

When the agent fights you

Fresh session, tighter prompt, or a different agent on the same worktree.

If the agent can't crack the issue, because its context filled up, it took the wrong approach, or it's missing domain knowledge, you have two options. Start a fresh session in the same pane with a tighter prompt. Or switch agents: open a new panel in the same pane, start Codex or Aider with the same task, and let it pick up the partial work on the same branch. A different agent sometimes finds the way when the first one is stuck.

Pane after committing, showing a Ready to merge badge, the commit in history and push and merge buttons — Committed, ready to pushOne shortcut commits. The header shows where the branch stands; push and merge are one click each.
1.Ready to merge: The header tells you where the branch stands.
2.History: Your commit shows up straight away. Click it to see its diff.
3.Push and merge: Push shows how many commits are waiting. Merge to main squashes by default.
Pane 2.4.155, right after the commit shortcut

Sources

Corrections

If anything here is wrong or out of date, tell us and we'll fix it and update the date at the top. Open an issue on GitHub

Sources

frequently asked questions

Download*

Windows SmartScreen warningDirect downloads can show a SmartScreen warning while Pane is unsigned. Pane is fully open source, so you can audit the code and build from source yourself.1. Click More info2. Click Run anyway3. Continue the installerThe PowerShell install downloads the official release directly and avoids most browser download friction.npm global install

Paste that in PowerShell.Linux

By Parsa Khazaeepoul, co-founder of Pane. Last reviewed October 2026.