Source-available app for the Cline coding agent

Run the Cline coding agent on your machine, drive it from your phone or desktop. Watch it work, jump in when needed.

Download for MacWeb App
All download options
Supports
+34 more
Sessions
A
acme/returns-app
main
+247-15
feat/dashboard
#142 · Open
P
acme/payments
main
fix/stripe-webhook
+38-4
#89 · Merged
I
acme/infra
main
feat/k8s-autoscale
+91-3
D
acme/design-system
main
MacBook Pro
mainacme/returns-app
Commit
+247-15
Orchestrator
Implement
Build me an internal dashboard for tracking customer returns

I'll break this down into planning and implementation.

Run plan-technicalcodex · plan-technical
Run plan-designclaude · plan-design
Wait for agentsplan-technical plan-design

Got the plans. Spinning up Codex for implementation.

Run implementcodex · 12 files changed

Implementation done. Requesting review from Claude.

Run reviewclaude · no issues found

All tasks complete. Dashboard is ready.

Message the agent, tag @files, or use /commands and /skills
Opus 4.6
npm run dev
$ npm run dev
> acme-returns@0.1.0 dev
> next dev --turbopack
▲ Next.js 15.3.1 (Turbopack)
- Local: http://localhost:3000
✓ Starting...
✓ Ready in 1.2s
○ Compiling /dashboard ...
✓ Compiled /dashboard in 340ms
○ Compiling /api/returns ...
✓ Compiled /api/returns in 120ms
Changes
Files
Uncommitted
dashboard.tsx src/pagesNew
+16-0
1
import { useState } from "react"
2
import { ReturnTable } from "./components"
3
4
export function Dashboard() {
5
const [returns, setReturns] = useState([])
6
const [filter, setFilter] = useState("all")
7
8
return (
9
<main className="min-h-screen p-8">
10
<h1>Customer Returns</h1>
11
<FilterBar value={filter} onChange={setFilter} />
12
<ReturnTable data={returns} />
13
<StatusChart data={returns} />
14
</main>
15
)
16
}
return-table.tsx src/components
+42-8
filter-bar.tsx src/components
+28-3
status-chart.tsx src/componentsNew
+19-0
returns.ts src/api
+12-5
index.tsx src/pages
+6-2

When you want to step away from your desk,
you can.

The native mobile app has full feature parity with desktop.

Pier sessions list
Pier agent chat
Pier diff view

Loved by developers

See what developers are saying about Pier.

Works with your tools

Run your agents from one interface. Pier uses each provider's native harness, so your subscriptions, skills, config, and MCP servers keep working.

Claude Code
Codex
OpenCode
Pi
Cursor
+34 more

Runs where you work

Start agents on your laptop, a VM, or a dev server. Use them from any device over a direct connection or the end-to-end encrypted relay.

Desktop
Web
Mobile
CLI

E2E Encrypted Relay

or

Direct Connection

MacBook Pro
Hetzner VM
Dev server

Review, preview, ship

Create branches, preview the app in the browser, review the diff inline, then commit, open a PR, and merge without leaving Pier.

fix-authworktree
WorktreePreviewReviewCommitPRMerge
web--fix-auth--my-app.localhost
Inline review3 files changed
src/auth/session.ts+42
src/auth/middleware.ts+18-9
tests/auth.test.ts+31
Ready to shipchecks passed
Commit
Open PR
Merge

Split panels

Open agents, browsers, terminals, diffs, and logs in the same workspace. Split them side by side or group them in tabs.

Agent
Browser
Terminal
Diff

Forget about ports

When agents work in parallel, they all run dev servers. Pier gives each one a URL based on the branch name, no port conflicts, no guessing.

my-app
fix-authnpm run dev
web--fix-auth--my-app.localhost
add-searchnpm run dev
web--add-search--my-app.localhost
upgrade-depsnpm run dev
web--upgrade-deps--my-app.localhost

Keyboard-first

Every action has a shortcut. Panels, splits, agents - all from the keyboard.

Switch panels
⌘1-9
Split vertical
⌘D
Split horizontal
⌘ShiftD
Close panel
⌘W
New agent
⌘N
Command palette
⌘K

Voice control, fully local

Fully local voice stack. Speech-to-text and text-to-speech run entirely on your machine, nothing leaves your network.

Fully scriptable

Everything you can do in the app, you can do from the terminal.

pier run "implement user authentication"
pier run --provider codex --worktree feature-x "implement feature X"
pier run --host devbox:6767 "run the full test suite"

pier ls                           # list running agents
pier attach abc123                # stream live output
pier send abc123 "also add tests" # follow-up task
Full CLI reference

FAQ

+How is this licensed?
Pier is distributed under commercial source license terms. You need Claude Code, Codex, Cursor, OpenCode, or Pi installed with your own credentials. Voice is local-first by default and can optionally use OpenAI speech providers if you configure them.
+Does my code leave my machine?
Pier doesn't send your code anywhere. Agents run locally and talk to their own APIs as they normally would. For remote access, you can use the optional end-to-end encrypted relay, connect directly over your local network, or use your own tunnel.
+What agents does it support?
Claude Code, Codex, Cursor, OpenCode, and Pi. Each agent runs as its own process using its own CLI or local integration. Pier doesn't modify or wrap their behavior.
+Do I need the desktop app?
No. You can run the daemon headless with npm install -g @usepier/cli && pier and use the CLI, web app, or mobile app to connect. The desktop app just bundles the daemon with a UI.
+How does voice work?
Voice runs locally on your device by default. You talk, the app transcribes and sends it to your agent as text. Optionally, you can configure OpenAI speech providers for higher-quality transcription and text-to-speech. See the voice docs.
+Can I connect from outside my network?
Yes. You can use the hosted relay (end-to-end encrypted, Pier can't read your traffic), set up your own tunnel (Tailscale, Cloudflare Tunnel, etc.), or expose the daemon port directly. See configuration.
+Do I need git or GitHub?
No. Pier works in any directory. Worktrees are optional and only relevant if you use git. You can run agents anywhere you'd normally work.
+Can I get banned for using Pier?

We can't make promises on behalf of providers.

That said, Pier launches each provider's local CLI or integration (Claude Code, Codex, Cursor, OpenCode, Pi) as a subprocess. It doesn't extract tokens or call inference APIs directly. From the provider's perspective, usage through Pier is indistinguishable from running the provider yourself.

I've been using Pier with all providers for months without issue.

+How do worktrees work?
When you launch an agent with the worktree option (from the app, desktop, or CLI), Pier creates a git worktree and runs the agent inside it. The agent works on an isolated branch without touching your main working directory. See the worktrees docs.

Pier is an independent source-available project for running coding agents across your own machines, phone, desktop, and CLI.

It's built around freedom of choice: use the provider you want, run it on your own infrastructure, and keep your workflow portable.

If you like Pier, starring the repository is the best way to support continued development while Pier-owned sponsorship accounts are being set up.

- Pier Team

Star on GitHub