PinDeck 3.1 beta 1: several decks, screenshots from the chat

The first preview of PinDeck 3.1. It adds a deck menu, so one PinDeck serves several decks on one port, and screenshots you can open from the chat. It is on npm's beta channel; npx pindeck installs 2.10.0.

What's new since 3.0.0-beta.3

• Open another deck from the editor (#9): click the deck's name above the slide to see the .html files in the deck's folder and its asset roots, and one folder down. Choose one to open it in the same tab (⌘-click for a new tab). Files PinDeck cannot open are greyed out with the reason. Listing decks changes no file; a deck gets its element ids only when it is first opened.
  • Each open deck keeps its own chat, assistant session and Undo. pindeck now starts a small front that holds the port and the login, and runs one deck server per open deck. Over SSH, one tunnel serves every deck.
  • A deck with no editor open for 30 minutes closes (its Undo history goes, as on a restart) and reopens when chosen again.
  • A folder without index.html opens a page listing its decks instead of failing.
  • pindeck login talk.html prints a link that opens that deck.
• Open a screenshot from the chat (#10): a screenshot the assistant took shows as a small picture on its chat line; click it to see it large. A screenshot PinDeck no longer keeps says so.

Try it

npx pindeck@beta path/to/deck

Or from the v3-beta branch. Requires macOS, or Linux (beta), Node 20 or later, and Claude Code (claude auth login) or Codex (codex login). Then open the login link PinDeck prints. Settings, chats and backups stay in ~/.pindeck-v3, apart from v2.

Known limits

• Two named decks in one folder share files such as theme.css. With both open, Undo refuses to overwrite a file the other deck changed, as with two PinDecks today.
• Each open deck starts its own headless Chrome when it needs one.
• The Codex integration uses OpenAI's experimental dynamicTools app-server extension, so a future Codex update may need a PinDeck update.
• Try the beta on a copy of your deck.

Please report problems as issues and mention "v3 beta".