pi-studio

A browser workspace for Pi. Write and run prompts, read responses with rendered math and diagrams, edit and annotate documents, and follow what Pi is doing, side by side.

Screenshots

The Prompt, with a section added from the Document:

The Document:

Zen mode, in rose-pine-dawn:

Watch the demo (1m36s, 2× speed, no audio). It shows browsing linked documents and bringing a Document selection into the Prompt.

Features

• Prompt and Document — the default, dual editor mode. The Prompt holds what you send to Pi; the Document holds the file you're working on. Each keeps its own edits, preview and place. See Single and dual editor mode.
• Run, critique, annotate — run the Prompt, ask for a critique, or annotate a response with [an: ...] markers and send it back.
• Response history and Working — step back through earlier responses and the prompts behind them, and follow Pi's thinking and tool use as it happens.
• Rendering — Markdown and LaTeX with math, syntax highlighting, Mermaid diagrams, CSV tables, interactive HTML and embedded PDFs, themed to match Pi.
• Files and Changes — browse folders you've allowed, open or preview files, and see the current git diff.
• Comments and scratchpad — comments anchored to lines or selections, and a scratchpad per document.
• Side questions and quizzes — ask about the text, a folder or the repository in a separate thread that stays out of the main conversation, or quiz yourself on it.
• REPL — send code to tmux-backed Shell, Python, IPython, Julia, R, GHCi or Clojure sessions, shared with pi-repl.
• Export — PDF (Pandoc and LaTeX) or standalone HTML, from the preview, a file or the last response.

Requirements

• Pi
• Pandoc for full previews and exports (brew install pandoc on macOS), and LaTeX (TeX Live or MacTeX) for PDF export
• Optional:
  • tmux for the REPL;
  • quarto for Quarto previews;
  • Mermaid CLI 11.12+ for diagrams in exported PDFs;
  • pdftotext so side questions can read PDFs;
  • BRAVE_API_KEY for side-question web search.

Studio is developed on macOS. It should work on Linux, which has had less testing.

Install

pi install npm:pi-studio

Or from GitHub, pi install https://github.com/omaclaren/pi-studio, or once without installing, pi -e https://github.com/omaclaren/pi-studio.

Usage

Studio opens in Muxy's or cmux's built-in browser when Pi runs there, and otherwise in the system browser. Press ? in Studio for keyboard shortcuts.

Pi's agent can also use these tools:

Single and dual editor mode

Dual editor mode is the default. The left pane has a Prompt, which is what Run sends to Pi, and a Document, the file you're working on. Switch with the tabs or Cmd/Ctrl+Shift+1 and 2. Selecting the Document never changes what Run sends.

• Add to Prompt copies the Document's selection, or all of it, into the Prompt as a labelled snapshot, with Undo.
• File opens a file in the Document, or in a new Document window. Each file has one editor; opening a file that's already open finds that editor.
• Unsaved Prompt and Document text survives reloads and dropped connections. If you close the tab, /studio reopens the same workspace, asking first if the tab didn't close cleanly. This isn't a backup: save work you want to keep.
• If Studio opened somewhere you can't find, such as another browser, /studio-replace moves it here, or open its URL and choose Move it here.
• /studio-current, editable /studio-editor-only and Office-to-Markdown conversion aren't available in dual editor mode.

Single editor mode is the one-editor Studio of earlier versions, where Run sends the editor's text.

To switch, use the footer button or /studio --single and --dual. Studio restarts and reopens the tab with the Prompt's text, and remembers the choice. If switching would lose anything, it says so first.

Details

Local files

Studio reads files in the opened document's folder and in folders you allow from Files. A link or image elsewhere asks first, offering that file or its folder, for the rest of the session.

Embed a PDF in a Markdown preview with a studio-pdf block. path is relative to the document; the other fields are optional:

```studio-pdf
path: attachments/paper.pdf
title: A title
page: 3
height: 760
watch: true
```

To view a PDF, run /studio report.pdf; it opens read-only, and #page=N picks the page. /studio --watch report.pdf also reloads it when the file changes; it waits until the file stops changing, so it doesn't reload half-written LaTeX output. (/studio-pdf is different: it exports to a new PDF.)

Mermaid icons

Diagrams can use lucide:* and logos:* icons; the icon packs load only when a diagram uses them.

```mermaid
flowchart LR
  source@{ icon: "lucide:file-code-2", form: "rounded", label: "Source", pos: "b", h: 56 }
  github@{ icon: "logos:github-icon", form: "rounded", label: "GitHub", pos: "b", h: 56 }
  source -->|publish| github
```

Icons in exported PDFs need Mermaid CLI 11.12+ (npm install -g @mermaid-js/mermaid-cli, or set MERMAID_CLI_PATH).

Pi's input editor

Load from pi editor (Cmd/Ctrl+Shift+L) copies the draft in Pi's terminal input into Studio, which suits tools like pi-nvim-context that build that draft up. When Studio runs that text, it clears the terminal draft only if the draft hasn't changed since.

REPL

The REPL pane runs code in tmux sessions. It can start its own, and it shares a record of submissions and output with pi-repl when both use the same session. Pane echo (Off, Summary, Full) controls how much submitted code appears in the raw tmux history; Full writes your code into that history. The record format is in shared/REPL_SESSION_RECORD_PROTOCOL.md.

Side questions

Review → Side question, or Cmd/Ctrl+Option/Alt+Q, opens a separate thread. It starts from the selection, the section at the cursor or the whole text, and can read the document's folder, the repository or another folder you allow, including PDF, DOCX, ODT and EPUB text. Its tools are read-only. With BRAVE_API_KEY set, it can also search the web; queries go to Brave Search. Nothing enters the main conversation unless you choose Bring to main conversation.

Network and SSH

Studio listens on 127.0.0.1 only, and every URL carries a token. Over SSH, forward the port and open the printed URL with its token; /studio --no-browser --port <port> gives a stable port to forward.

For a container, /studio --no-browser --listen-all --port 4321 listens on all interfaces. Anyone with the full URL can control Studio, including running prompts and reading or writing files, and there's no TLS. Treat the URL like a password, never expose the port to the internet, and bind the host side to loopback (-p 127.0.0.1:4321:4321). Quarto previews use a second port, which must be forwarded too.

Environment variables

Installing pi-studio also adds pi-studio-dark and pi-studio-light to Pi's themes, without changing your current theme.

Acknowledgements

Thanks to Hal Gumbert / CampSoftware for Pi Studio Activity, which inspired Follow activity and the stacked layouts.

License

MIT