01
Native first
Agents run in their own native terminals. Pier doesn't wrap, proxy, or rewrite your toolchain — your existing accounts, subscriptions, and habits keep working.
macOS · Apple Silicon / Intel
The local AI dev workbench
Keep Claude Code, Codex, OpenCode and other native CLIs running in your local projects — watch status, return to the terminal, and review Git changes in one saveable workspace.
Your agents keep running in their native terminals — Pier is not another chat wrapper.
Runs the agent CLIs you already use
Claude CodeOpenClaudeCodeBuddyQoderCodexGrokGitHub CopilotOpenCodeMiMo CodeAntePiOMPGeminiAntigravityAiderGooseAmpKilocodeKiroCharmAuggieAutohand CodeClineCodebuffCommand CodeContinueCursorDroidKimiMistral VibeQwen CodeRovo DevHermesOpenClawDevin
01Why Pier
Not another chat wrapper
Pier doesn't repackage CLIs into a unified chat window. Agents keep running in their own native terminals; when several sessions run at once, Pier adds the cross-session state — in one saveable workspace.
02
Cross-session status
Running, needs you, and error sessions are visible in one place. No more hunting pane by pane to find out who is waiting on you.
03
Status is an entry point
Status isn't the destination. Click a session to return to its original terminal, and review the same project's Git changes right next to it.
02Core workflow
From launch to review, without leaving the scene
- 1
Launch
Start Claude Code, Codex, OpenCode, or another native agent CLI inside a project or Git worktree.
- 2
Watch status
Track running, needs you, and error states across every session in Pier.
- 3
Return to the terminal
Pick a session and jump back into its original terminal for input, confirmations, or follow-up work.
- 4
Review changes
Keep sessions alive while reviewing working-tree and staged Git changes — stage or unstage by file or by hunk.
03Performance & feel
Fast comes from the engine. Smooth comes from design.
The terminal kernel sets the floor; the paths your fingers take set the feel. Pier treats both as product capabilities.
Ghostty engine, native all the way down
Native rendering
Terminals are driven by Ghostty native (an XCFramework built from Swift / Zig) with GPU-accelerated rendering — heavy output stays smooth under load.
Sessions outlive the UI
After a UI reload or restart, running terminals remain usable.
Polished for agent TUIs
Pier maintains its own set of Ghostty patches for details that matter to agent work — cursor visibility, input focus handoff, and friends.
macOS · Swift / Zig / libghostty
Everything is ⇧⌘P away
⇧⌘P
Command palette
⌘P
Quick Open file
⌘T
New tab
⌘⇧Y
Jump to next needing attention
⌘D
Split pane
⌘F
Find in terminal
The command palette gathers every action: fuzzy search ranked by recent use, and official plugins can contribute commands. Search shortcuts in Settings and remap bindings freely.
04Core capabilities
Host terminals, surface status, organize the workspace
Native terminals
A native terminal built on the Ghostty engine with GPU-accelerated rendering. Run shells and CLI coding agents inside projects or worktrees — running sessions survive UI reloads.
Session status
See running, needs you, and error sessions in one place — click any of them to jump back to its terminal.
Parallel isolation
Create and manage Git worktrees so different tasks advance in independent branch directories without collisions.
Files & changes
Browse and preview project files, review working-tree and staged diffs, and stage or unstage by file or hunk.
Canvas
Keep plans, flows, diagrams, docs, or light prototypes as previewable pages saved with the project — content, not a task orchestrator.
Saveable layouts
Arrange terminals, files, and changes with tabs, splits, and floating panels. Layouts save automatically and restore on reopen.
05Local CLI & official plugins
Beyond the workbench, there's a command line
pier · control the Pier already running on your machine
Use pier to open projects, locate windows and panels, open terminals and send text or keys, and query agents and worktrees. It only connects to the Pier running locally — it's not a remote API.
Read the CLI manualOfficial plugins
Pier ships built-in plugins plus official plugins that are signed, verified, and version-managed. There is no third-party plugin marketplace — the trust boundary stays auditable.
Read the plugin docszsh — pier
# open the current project in Pier
❯pier open . --json
# query windows, panels, and agent status
❯pier status --json
# list panels in the current layout
❯pier panels list --json
❯
Product boundaries
What Pier deliberately doesn't do
Boundaries make a tool trustworthy. Pier hosts terminals, surfaces status, and organizes your workspace — nothing more.
No task orchestration
Pier never splits, dispatches, or schedules tasks, and there is no task ledger or kanban. How work gets assigned is between you and your agents.
No wrapping your agents
CLIs are never repackaged into a chat product. Canvas is project content saved alongside your code — not a task orchestrator.
No third-party plugin marketplace
Only built-in plugins and official signed, verified, version-managed plugins. No unauditable third-party code.
The test is simple: remove Pier, and your native tools still do the same job. Pier just keeps the scene clear.
Download
Dock your agents into the project
Free and open source. Download, pick a project folder, and start running agents, browsing files, and reviewing changes.
The desktop app currently supports macOS only (Apple Silicon / Intel).
The packaged app tries to put pier on your PATH at launch. If the command is missing, install it in Settings → Terminal.
Or run from sourcegit · pnpm
❯git clone https://github.com/runloom/pier.git
❯cd pier
❯pnpm bootstrap
❯pnpm dev
Requires Node ^24.15, pnpm ≥11.12, Xcode Command Line Tools, Homebrew, and zig@0.15.
FAQ
Frequently asked questions
Does Pier proxy or modify my model requests?
No. Agents run in their own native terminals, so your accounts, subscriptions, and configuration keep working as-is. Pier only hosts terminals, aggregates status, and organizes the workspace.
Which platforms are supported?
The desktop app currently supports macOS only, with Apple Silicon and Intel builds.
How is this different from a terminal multiplexer like tmux?
Pier is a desktop workbench: besides hosting stable terminals, it adds cross-session status, Git change review, file preview, Canvas, and saveable panel layouts.
Where does my data live?
Everything stays local: preferences and layouts are local JSON files, raw terminal output is written to local segment files, code changes are read live from Git, and secrets go to the system's secure storage.
Which terminal engine does Pier use?
The terminal runs on Ghostty's native core (Swift / Zig) with GPU-accelerated rendering. Pier maintains patches on top of it for agent-TUI scenarios; running terminals survive UI reloads.