🦀🍝🦀 Pappardelle 🦀🍝🦀
A TUI for multi-clauding without losing your marbles.
You type a description, it reads or creates an issue in Linear/Jira, spawns a configured git worktree, builds a PR/MR, and starts a Claude Code session alongside a lazygit session — all wired together in a 3-pane tmux layout you can navigate with simple, customizable keystrokes.
Video:
https://github.com/user-attachments/assets/abeaf413-5a1e-448a-ac53-2956a8ada5bf
Table of Contents
- Installation and Getting Started
- Understanding tmux in Pappardelle
- Spawning New Sessions
- Spec-Driven Development Mindset
- Customizing Your Configuration
- Advanced: Doom-coding with Pappardelle
- Advanced: Wrangling Multi-Repo Changes
- Reference
1. Installation and Getting Started
The fastest way to get set up is with /init-pappardelle.
Add the marketplace:
claude plugin marketplace add chardigio/pappardelle
Install the plugin. This installs four skills — /init-pappardelle (setup wizard), /update-pappardelle (update to latest), /configure-pappardelle (interactive config editor), and /sous-chef (optional workspace coordinator):
claude plugin install pappardelle@pappardelle-marketplace
Run the setup wizard from any repo where you want to use Pappardelle. This installs pappardelle configures your .pappardelle.yml:
claude /init-pappardelle
For manual installation, see Section 8: Reference. For the full config format, see the configuration reference.
Launch Pappardelle:
pappardelle
2. Understanding tmux in Pappardelle
The 3-pane layout
When you launch pappardelle, it creates a tmux session with three panes:
- Left pane shows the ticket rail. This is where you navigate workspaces, create new ones, and trigger actions.
- Center pane shows the Claude Code session for whichever workspace is highlighted.
- Right pane shows lazygit for the highlighted workspace's worktree.
How nested sessions work
Each workspace creates two independent tmux sessions:
claude-{repo}-{issue-key}— runs Claude Codelazygit-{repo}-{issue-key}— runs lazygit
The center and right panes in the Pappardelle session are "viewers" — they run nested tmux clients that attach to these independent sessions. When you highlight a different workspace in the list, Pappardelle uses tmux switch-client to instantly swap which session the viewer pane displays.
This means:
- Workspaces are independent. Each Claude session runs in its own tmux session. If Pappardelle crashes, your Claude sessions keep running.
- Attach from anywhere. You can attach to any workspace's Claude session from a separate terminal:
tmux attach -t claude-stardust-labs-STA-631. - Switching is instant. After the first attachment, switching between workspaces uses tmux's fast
switch-clientpath — no process restart, no visible flash.
Recommended tmux config
Pappardelle works with any tmux configuration, but these settings improve the experience — mouse support, Ctrl+Shift+arrow pane navigation, and a clean status bar. See examples/tmux.conf and append to your ~/.tmux.conf. If you don't have one yet:
curl -fsSL https://raw.githubusercontent.com/chardigio/pappardelle/main/examples/tmux.conf -o ~/.tmux.conf
Exiting Pappardelle
Press q in the workspace list pane to quit. This kills the Pappardelle tmux session and all its viewer panes, returning you to your original terminal. Your Claude and lazygit workspace sessions are not affected — they run in independent tmux sessions and will keep going after Pappardelle exits. To reattach, just run pappardelle again.
To also kill all workspace sessions, use Delete on each workspace from the TUI before quitting, or nuke everything with:
tmux kill-server
3. Spawning New Sessions
From the TUI
Press n in the workspace list to open the prompt dialog.
What gets provisioned
When you create a workspace, Pappardelle runs through these steps: