Everything around the card.
In the same window.
How it works follows one card from a sentence to a shipped change. This page is the rest of the app: what you reach for while cards are in flight. Every scene shows the app’s own screens, in its own words.
See the change running before you ship it.
Once the Builder has made a change, the card has a Try it button. Plyloft starts your app in the card’s own copy and shows it on the card: Starting your app…, then Running on localhost, with the page itself under it.
A diff tells you what changed; clicking through your app tells you whether it is right. Try it gives you that before anything reaches your main branch, with no second checkout to set up by hand. No AI is used for it, and your own files stay as they are.
Details
Ran "npm run dev" in the card’s copy · port 41003Claude, Codex and your shells, side by side.
Terminals is where you talk to Claude or Codex directly, try a command or keep your dev server running, in your project’s folder. Lay the sessions out one, two, four or six at a time; your cards’ sessions are listed beside them in the sidebar.
Not everything needs a card. A quick question, a one-off script or a long conversation belongs in a session, and with several open you need to see at a glance which one is waiting for you and which one has ended.
npx vitest run src/auth/login.test.ts
Do you want to proceed?
❯ 1. Yes
2. Yes, and don’t ask again for npx vitest
3. No, and tell Claude what to do differently
- ⌘TorCtrl+T
- A new session: a shell, Claude or Codex, as Settings chooses
- ⌘⇧TorCtrl+Shift+T
- A new Claude session
- ⌘⇧XorCtrl+Shift+X
- A new Codex session
- ⌘⇧RorCtrl+Shift+R
- Resume…
- ⌘⇧]orCtrl+Shift+] · ⌘⇧[orCtrl+Shift+[
- The next or the previous session
- ⌘⇧EnterorCtrl+Shift+M
- Expand the session you’re in, or show the grid again
- ⌘⇧WorCtrl+Shift+W
- Close the session you’re in
What needs you, and what already happened.
The Inbox gathers what waits on you in every project: a card ready to ship, a review that asks for changes, a session that finished its turn or asks you something, a check that failed. History keeps what ran, shipped and was checked in every workspace over the last 28 days.
With several cards and sessions going at once, you shouldn’t have to visit each project to find the one that needs you. And when you wonder whether something shipped, or which session that fix came from, History has the answer without digging through terminals.
5 things need you, 1 is working.
- Pushed to pull request #33. Its branch on GitHub has the fix now.just now
- Work saved. Your checks are running. The result goes back to the Builder.11m ago
- Planning finished. Dark mode for the invoice PDF18m ago
- Updated to 1.168.022m ago
What ran and shipped in every workspace over the last 28 days.
- Agent runs
- 2, 1 failed
- Builder rounds
- 13 on 9 cards
- Checks
- 5 of 6 cards passed their latest checks
- Shipped
- 5
- Typical agent run
- 4m
The Claude and Codex sessions you opened in Terminals over the last 28 days. Resume picks one up again in a new session.
- ⌘⌥1orCtrl+Alt+1
- Open the Inbox
- ⌘⌥5orCtrl+Alt+5
- Open History
- ⌘⇧HorCtrl+Shift+H
- Search History
Point the Reviewer at any open pull request.
Review a pull request…, in the Board’s ⋯ or in Search, lists the repository’s open pull requests: yours, a colleague’s, even one from a fork. Plyloft makes a card for it, and the Reviewer reviews it read-only, in a copy of its own, with the same findings and rounds as any card.
A second opinion is worth having on every change, not only on the ones Plyloft built. The findings stay in Plyloft, so you decide what to tell your colleague. On your own pull request, the Builder can fix what was found and send the fix to it.
Pull request #34 · by @alice · retry-upload → main · Retry failed invoice uploads · Reviewer: Codex
This is alice's pull request: the Reviewer only reviews it, and the Builder doesn't change it.
Pull request #33 · by @sam-rivera · csv-export → main · Export invoices as CSV · Reviewer: Codex
This is your pull request: Fix with the Builder works on this card's copy of its branch.
The fix's checks passed.
- ⌘KorCtrl+K
- Search, where Review a pull request… is one of the commands
Talk a card over before anything is built.
Every card has Ask about this card: ask its Builder, Claude or Codex, what the card means, which files it would touch or how to approach it, and give it a screenshot, a PDF, a Word or a text file. On a card that isn’t built yet, Plan with two AIs has one AI write the plan while the other critiques it.
A sentence on a card can hide a decision nobody made. Asking first costs less than a build that went the wrong way, and a plan two vendors have argued over gives the Builder fewer blind spots. Both are discussion only: nothing in your project changes.
Discussion only. The chat can read this card's title and notes, the files you add here, and the project, but it can't change anything. Code changes stay with the card's Builder.
- YouWhich files would this touch? The mock of the list is attached.invoice-list-mock.pngImage · 182 KB
- Claude used Read: src/invoices/InvoiceList.tsx
- ClaudeTwo files, going by the mock:
src/invoices/InvoiceList.tsx: the Previous and Next row under the table, and the page in the URLsrc/api/invoices.ts: passlimitand the cursor the API already returns
Tokens in this conversation: 6 in · 412 out · 18,204 read from the cache · 9,840 written to the cache.
Two AI sessions plan this card together: one writes the plan, the other critiques it, the first revises it. Discussion only: neither can change anything. You decide at the end.
- Claude proposesClaudePlan: pages of 50 in InvoiceList.tsx. Read page and filter from the URL (?page=2&status=unpaid), so Back and a shared link keep both. Ask the API for one page with limit and offset; show “Page 2 of 7” with Previous and Next.
- Codex critiques · round 1 of 2 · Verdict: changes neededCodexOffset pages shift when an invoice is added while you read: page 3 can repeat a row. The API already returns a cursor (next_cursor), so use it. And “of 7” needs a count query the API doesn’t have.
- Claude revises · round 1 of 2ClaudeRevised: cursor pages from next_cursor, kept in the URL with the filter. Previous and Next, no page count. Changing the filter goes back to the first page.
- Codex critiques · round 2 of 2 · Verdict: readyCodexReady. The URL keeps the cursor and the filter, and the first page is the default.
Claude (proposer): Tokens in this conversation: 14 in · 6,912 out · 88,410 read from the cache · 12,906 written to the cache.
Codex (critic): Tokens in this conversation: 13,288 in · 604 out · 52,117 read from the cache.
Your project’s files, one keystroke away.
Code is your project’s own folder in an editor: the file tree on the left, your files in tabs on the right. Go to file opens any file by part of its name, In files searches the text of all of them, and the tree’s right-click menu does the rest.
The Builder writes most of the code, but you still want to read a file, fix a typo yourself or look at what a card is about to change, without opening another editor. Code works on your project itself; a card’s work stays in its own copy until you ship it.
- ⌘PorCtrl+P
- Go to a file
- ⌘⇧ForCtrl+Shift+F
- Search the text in your files
- ⌘SorCtrl+S
- Save the file
- ⌘⌥SorCtrl+Alt+S
- Save all files
- ⌘⌫orDelete
- Move the file picked in the tree to the Trash (the Recycle Bin on Windows)
- ⌘=orCtrl+= · ⌘−orCtrl+−
- Larger or smaller text in the editor
Learn it on your own project.
Getting started takes you through your first card in your own project. It points at the real buttons and waits for you; it never presses anything for you. Help, the row above Settings in the sidebar, holds the tour, Tips, what’s new in your version, the user guide and Get help.
A tour of a sample project teaches you the sample. Doing your first card for real, with a pointer at each step, leaves you with a shipped change and knowing where everything is. Later, New in this version tells you what changed without reading a changelog.
- Nothing gets lost: quitting or closing a tab asks first when a file isn't saved or work would stop halfway, Done no longer archives a card, and every archived card can be restored.
- Sessions that continue: an ended Claude or Codex tile offers Continue, the sessions open when you quit come back, each tile takes its conversation's name, and New › Resume… picks up any conversation from the last 28 days.Open Terminals
- A clearer Board: five columns — Needs you, Not started, Working, On hold, Done — a tile needs you only when it asks, the card's next step is at the top, and you can move around the Board with the keyboard.Open the Board
- History in tabs — Runs, Ships, Checks, Sessions — with a workspace and a text filter, no dollar figures, and search results that open what they found.Open History
- Easier every day: text size and zoom for terminals and the editor, hidden files and file actions in Code, Check for updates, and Install when my work is done.Open text size
- ⌘/orCtrl+/
- Keyboard shortcuts (outside the editor; on a non-US keyboard, ⌘ with the key that types /)
- ⌘KorCtrl+K
- Search and commands
Every skill, and where it lives.
Library › Skills shows what the agents know in a project: skills in the repository, in the team library, on this computer and the four that come with Plyloft. All skills, in the sidebar, lists every skill on this computer and where each copy is used. My library keeps your own skills in a private repository on your GitHub account.
Skills pile up in folders nobody opens and get copied by hand between projects, until nobody knows which copy is current. Here each one says where it lives and whether it is up to date, and a copy into a project always goes through a card you see before it ships.
- ⌘⌥6orCtrl+Alt+6
- Open the Library
The same app on Windows 11.
Plyloft runs on Windows 11, 64-bit (x64), with the same features as on a Mac in every release. Tiles run PowerShell, Claude and Codex; shortcuts use Ctrl; closing the window can keep Plyloft running in the notification area.
A team rarely works on one kind of computer. With the same app on both, a card, a review and a skill look and work the same for everyone, and nobody waits for a Windows version that comes later.
- Ctrl+/
- Keyboard shortcuts
- Ctrl+K
- Search and commands
- Ctrl+Shift+M
- Expand the tile you’re in, or show the grid again
- Ctrl+Shift+Q
- Quit Plyloft