The workflow is simple: issue lives somewhere (Linear, GitHub Issues, Jira). The agent does the work. The PR ships from your branch. Here is the step-by-step from triage to merged.
walkthrough
→ Step 1. Read the issue. Open it in Linear, GitHub, or Jira — or have the agent fetch it via MCP. Copy the issue title and description.
→ Step 2. Open Pane and create a new pane. Pane automatically creates a git worktree on a fresh branch. Name the pane after the issue (e.g. fix/auth-123).
→ Step 3. Launch Claude Code in the pane. Paste the issue description as your first prompt. The more context you provide — acceptance criteria, repro steps, relevant file paths — the fewer follow-up rounds you will need.
→ Step 4. The agent reads files, writes code, and runs tests. Watch progress in the terminal. Desktop notifications fire when the agent finishes or needs input.
→ Step 5. Press ⌘D to open the diff viewer. Review the changes file by file.
→ Step 6. If the agent's output has gaps — missing tests, scope creep, a regression — switch to the terminal tab in the same pane and give it a follow-up prompt. Repeat until the diff looks right.
→ Step 7. Press ⌘K to commit. Write a conventional-commits message that closes the issue — for example: fix: handle empty state in auth form Closes #123. Push the branch.
→ Step 8. Open the PR. From the pane's terminal, run gh pr create, or open the platform's web UI and create it there.
→ Step 9. After review and CI pass, merge. The issue closes automatically if you used the Closes # keyword.
why no first-party linear integration
Pane is not a project management tool. Your agent can hit Linear, GitHub, or Jira directly via MCP — the same way it reads your code. We do not replicate features the agent already covers. If you want the agent to fetch the issue description, update the status to In Progress, and link the PR automatically, wire up the relevant MCP server in your Claude Code configuration. Pane stays out of the way.
when the agent fights you
If Claude Code cannot figure out the issue — context window filled up, wrong approach, missing domain knowledge — you have two options. First, start a new Claude Code session in the same pane with a tighter, more-specific prompt. Second, switch agents: Pane is agent-agnostic. Open the terminal, kill Claude Code, launch Codex or Aider with the same task spec in the same worktree. The branch and the partial work are still there. A different agent sometimes finds the right approach when the first one got stuck.
frequently asked questions
GitHub CLI (gh) is helpful for creating pull requests from the terminal, but it is not required. You can open a PR from your platform's web UI after pushing the branch. If you want to stay keyboard-first, install gh and run 'gh pr create' from the pane's terminal after pushing.
No. Pane commits and pushes the branch. Opening the PR is done by the agent (using gh pr create or a similar MCP tool call) or by you from the platform's web UI. Pane intentionally does not replicate features the agent or the platform already handle.
Claude Code supports MCP servers, including a Linear MCP server that lets the agent read issues, update statuses, and link PRs directly. If you want the agent to fetch the issue description automatically instead of you pasting it, wire up the Linear MCP server in your Claude Code configuration. See runpane.com/docs/mcp for setup instructions.