vitofico/galley

AI-native document workspace built on
Typst .
▶ Try the live demo —
no signup, no API key. Everything runs in your browser. It's meant for the
built-in offline Demo agent — don't enter a real API key or GitHub token there.
A galley proof is the preliminary typeset version you check and correct before
final layout — which is exactly this app's core loop: compile → inspect →
correct → repeat.
Galley is, conceptually, "AI-enhanced ShareLaTeX, but Typst instead of LaTeX, open source,
and not locked to one vendor's cloud or model." The differentiation is three
bets a cloud-only, single-vendor product structurally cannot make:
1. Agentic, not autocomplete. Typst compiles in milliseconds and emits
structured, machine-readable diagnostics. That makes a tight
edit → compile → read errors → self-correct loop cheap. That loop is the
product.
2. Local-first. The Typst compiler runs in the browser via WASM
(typst.ts). Your document and
your compile stay on your machine. Server-side compile is an optional
enhancement, never a dependency. (See the honest local-first
definition — remote model
endpoints still receive your document.)
3. Bring-your-own-model. A provider abstraction runs the agent against any
OpenAI-compatible endpoint, Anthropic, or a local Ollama. Model choice is
config, never a fork.
## Status
Galley works end-to-end in the browser today: a CodeMirror editor with a live
SVG preview (typst.ts compiling in a Web Worker) and the human-in-the-loop
agent loop — request → self-correct → diff → Accept/Reject → re-render.
Bring your own model (any OpenAI-compatible endpoint, Anthropic, or a local
Ollama) or use the built-in offline Demo agent. Real-time collaboration is
opt-in — one-click Share upgrades a project to Yjs CRDT co-editing with the
agent as a peer, presence, and per-author attribution (ADRs
0005–0012). Multi-file projects and templates, named versions
with visual compare, broad import/export (Markdown, LaTeX, Overleaf .zip,
Zotero/.bib in; PDF/PNG out), and opt-in MCP access behind an explicit
consent gate round it out. Self-host with Docker compose or Kubernetes; the
whole test suite (typecheck + unit + Playwright e2e) runs in Docker. See
the CHANGELOG for the full feature inventory and the
roadmap for what's next.
### Default product & routes
Galley uses path-based routes (a tiny History-API router):
/ — the Projects page, the landing surface (create / open / import projects).
/p/ — a specific local-first project (auto-saved to the browser, reload-survivable).
/library — the project dashboard.
/join/ — share-link entry (joins a collaboration room; carries ?sync= / ?role=).
/settings — device-scoped settings.
Collaboration is an explicit Share action, never on by default. The only
editor-on-home hatch is ?seed=… (the seeded Einstein showcase, also the e2e entry).
## The core loop
User request
Agent proposes edits (search/replace blocks)
Apply to a SCRATCH copy ──► compile ──► read diagnostics
│ │
│ ◄── errors? revise (up to MAXITERS) ─┘
Clean compile → present a reviewable diff
User clicks Accept ──► apply to live document
or Reject ──► discard scratch
In the editor loop the human is always in control — the in-app agent never