Many agents.
One clear direction.
A focused home for your favorite coding agents.
Build in parallel. Preview your app. Bring feedback into focus.
- Local-first
- Your agents & accounts
- Your code, your control
I’ll split the independent API, test, and copy work, then validate the combined result.
- ✓Plan
- ✓Spawn
- ✓Work
- ✓Merge
- 5Review
Pick up right
where you left off.
Search across workspaces and tasks. One quick switch brings you back to the work that matters.
⌘K in the desktop appNo matching tasks. Try “checkout” or “feather”.
Less clutter.
More headspace.
Hide a task when you’re done with it. Find it in Hidden whenever you need it. Your work stays yours.
Try hiding and restoring a task.No hidden tasks. Everything is in view.
Your favorite agents. Right at home.
New A closer connection to your work
See it. Refine it.
Keep moving.
The app you’re building. The feedback that makes it better. The space to think. Now closer to your agent, and closer to hand.
Your app,
beside your agent.
Open the app you’re building inside Feather. Point at a detail and turn your feedback into a draft with the right context attached.
- ↗ Page and element context
- ↔ Desktop and mobile viewports
- ✓ Review the draft before sending
Try it: choose Select element, then the shop button.
A little more
ordinary magic.
Thoughtful objects.
Made for the moments in between.
Draft prepared in this demo. Nothing has been sent.
Feedback in.
A clear next step.
See the pull request for your branch, its CI checks, and reviewer conversations. Bring unresolved feedback straight into an agent draft.
- ↗ The PR beside your work
- ◉ Checks and review threads
- ✓ You choose what gets sent
Uses your GitHub CLI sign-in. Try the thread filters and prepare a draft.
Give the storefront room to breathe
Ready to review. No message sent or GitHub thread changed.
A little atmosphere.
A lot of focus.
Soft glass when you want depth. Solid surfaces when you want simplicity. Your chat, terminal, and code stay easy to read.
- ◐ Glass or Solid appearance
- ↔ Desktop scale and accent controls
- ✓ Respect for system preferences
Try a material below. Your choice applies to this website and is saved in this browser.
Make room
for the good work.
Choose the surface that feels right.
Your next task, ready.
Reorder waiting work, pause dispatch, set prerequisites, and retry failed attempts. Schedule recurring runs while Feather is open.
Your usage, in view.
Recorded tokens, cost breakdowns, and available provider quotas. Set alerts and pin a floating usage widget.
The work, revisited.
Step through recorded agent activity in Replay. Follow the conversation and tool events at your own pace.
NEW / Queue & review
From your next task
to a reviewed result.
Choose what runs next. Keep the outcome of every attempt. Bring the changes, local verification, and GitHub feedback together when it is time to review.
A queue that
keeps its place.
Move waiting tasks up or down, pause new dispatch, and retry a failed attempt in a fresh worktree. Add a prerequisite when one task needs to finish first.
- Unrelated tasks can pass a blocked item
- Room reserved for a collaborative worker
- Every failed attempt stays inspectable
Dependencies control start order. Code is reviewed and merged separately. Scheduled work requires Feather to be running.
Dispatch on · 1 place reserved for a worker
- 1Improve checkout validation CollaborateNeeds room for a lead + worker
- 2Refresh the setup guideReady when a task slot is available
- 3Check the checkout journeyStarts after checkout validation succeeds
Try moving a task up. Its prerequisites still apply.
The result.
And the evidence.
The Review tab brings the task brief, changed files, saved local test and agent-review reports, and GitHub feedback into one overview.
- See the tree and base behind local checks
- Spot stale evidence after another edit
- Turn unresolved feedback into a chat draft
Local verification and GitHub CI show their own versions. Missing or skipped checks are never presented as passed.
Configured checks passed.
Recorded tree 3de91afNo blocking findings.
Recorded tree 3de91af2 reported checks passed.
PR commit 72bd810Current tree 3de91afLocal checks cover the current worktree. The PR still has feedback to address.
01 / Better together
Parallel work.
A shared finish line.
Give one goal to a lead. Let the right agents take on independent work, each in its own worktree. Bring it all back to one result you can review.
-
01
Plan
The lead reads the goal and decides whether parallelism will actually help.
-
02
Spawn
Up to four direct workers receive complementary, non-overlapping briefs.
-
03
Work
Each worker runs with its own branch, worktree, model, and live status.
-
04
Merge
Edits are committed, ancestry checked, and failed merges are aborted cleanly.
-
05
Review
You inspect one integrated diff and validate the combined change once.
Claude Code · checkout-reliability
feather/7f1a
Integratedfeather/8c2e
Integratedfeather/9d3b
IntegratedEnough parallelism without runaway fan-out.
Workers cannot create workers of their own.
The lead is restored when integration fails.
Done means the worker change is integrated.
02 / In your element
From first thought
to final diff.
A workspace that keeps up with your ideas. Brief your agents, follow their progress, and review the details, all in one place.
The workspace, in motion A guided recreation of the desktop experience.
Brief, then dispatch
Create a task with its goal attached. Choose your agent and environment, then follow the work from its first turn.
Queue the next move
Build a task backlog, choose a concurrency limit, and set recurring schedules while Feather Terminal is running.
Route the right model
Choose the harness and model per task, or let Smart Models match the work to an available option.
export function validateAddress(values) {
- if (!values.country) return true;
+ if (!values.country) return invalid("country");
+ if (values.country === "CA") {
+ return validatePostalCode(values);
+ } return validateZip(values);
Review cleanFocused tests passed · no blocking findings
✓03 / Confidence, built in
Every change.
In the clear.
One branch. One combined diff. A clear view of what changed, and the checks to help you move forward.
-
01
Inspect the combined diff
Review every integrated change with syntax-aware, file-by-file context.
-
02
Run the configured gates
Tests and a second-agent review can feed findings back into the task.
-
03
Keep a way back
Save checkpoints and restore worktree files. When you’re ready, merge into the base branch or prepare a pull request.
04 / A little more freedom
Out of office.
Still in the loop.
Pair the whole workspace or share one task with a server-enforced scope. Continue through the encrypted web companion when an agent needs a decision.
-
⌁
Share the right scope
Choose full control or a task-scoped link before showing the QR.
-
◇
The right controls
Use chat, terminal, and diff for one task; add fleet, queue, and usage with full control.
-
⌾
Encrypted bearer link
The relay sees ciphertext. The QR is the key, and Stop Sharing revokes it for everyone.
The three worker branches are integrated. The configured checks pass.
Open the combined diff before merging?
05 / Thoughtfully equipped
The little things.
Already thought through.
The tools around your agents matter, too. Keep your environment, your time, and your next move under control.
Real Git worktrees
Start tasks in isolated branches and working directories, or add another agent to an existing workspace.
FILES & COMMITSA terminal that stays close
Move between structured chat and a real terminal. Search output and navigate command blocks in supported shells.
CHAT & TERMINALRuntime visibility
Track ports, processes, app-wide services, and per-worktree SQLite isolation.
RUNTIME & SERVICESQueues and schedules
Keep a backlog, set concurrency and task budgets, and schedule recurring work while the desktop app is running.
AUTOMATIONA clearer view of usage
Check available account quotas, recorded tokens, and cost breakdowns. Token-priced estimates are identified separately from provider-reported costs.
MODELS & USAGELocal MCP control
Expose core task, terminal, diff, review, queue, and agent operations on localhost.
AUTOMATABLEAt home on your machine
Your code. Your space.
Feather Terminal runs on your Mac. Your repository stays in local worktrees, with no upload to a Feather backend. Your coding agents use their own providers and data terms. Remote access is always optional.
A few things to know
Good questions.
Clear answers.
Feather Terminal is currently a macOS developer preview. Here’s what to expect.
Public release in preparationWhich coding agents are supported?+
Feather Terminal includes Claude Code, Codex, Gemini CLI, OpenCode, Cursor CLI, GitHub Copilot CLI, and a plain shell. Structured chat and collaboration depend on each harness’s headless and tool-bridge support.
How is worker integration kept safe?+
Workers start from a recorded commit in isolated worktrees. Feather Terminal commits their edits, verifies branch history, merges serially, confirms the worker commit landed, and aborts failed merges while restoring the lead.
Does Feather Terminal send my repository to a backend?+
No Feather Terminal backend receives your repository. The app and worktrees run locally. The coding-agent CLI you choose may send prompt or code context to its own provider under that provider’s terms.
What can I do from the remote companion?+
A task link exposes that task’s chat, terminal, diff, and permission replies. Full control adds workspace-wide task, queue, fleet, and usage surfaces. The desktop enforces the API scope, but a shared terminal still has your local user’s filesystem permissions.
Can agents automate Feather Terminal itself?+
Yes. A localhost MCP control plane exposes core workspace operations including tasks, terminals, diffs, reviews, queues, and bounded worker delegation.
How does visual feedback work?+
Open your running app in the task’s Preview tab, select an element, and describe your change. Feather adds the element’s page, text, and layout context to a chat draft for you to edit and send. Desktop and mobile-width previews are available.
Can I review GitHub pull requests here?+
Yes. Sign in with the GitHub CLI to see the current branch’s pull request, CI checks, and review threads. Selected feedback becomes an editable agent draft. You decide when to send it; preparing a draft does not post or resolve GitHub comments.
Can I turn off the glass effect?+
Yes. Choose Glass or Solid in the desktop appearance settings, alongside accent color and display scale. The interface also respects supported system preferences for reduced motion, reduced transparency, and increased contrast.
Will scheduled tasks run if I close Feather?+
Schedules run in the desktop app, so Feather must remain running on your Mac. Queue items can have their own task budgets. When a schedule has a budget, each occurrence starts with a fresh budget.
Where can I download it?+
Feather Terminal is in active developer preview for macOS. Public builds and source distribution are being prepared. Download details will be available here when the public release is ready.
Developer preview
Big ideas deserve
a little headspace.
Bring your agents. Find your focus. Build what’s next.
macOS developer preview · Public release coming soon