Getting started

Concepts

Workspaces, pages, templates, comments, publications, and Backup to Git.

A small vocabulary covers most of the product surface.

Workspaces

A workspace is the tenant boundary. Every page, folder, comment, attachment, publication, and audit log carries a workspace ID. Users belong to one or more workspaces. Self-hosted instances start with one workspace; managed signup creates one per account.

Pages and folders

Everything visible in the content tree is a page. Folders are organizational containers. Pages can be regular docs, specs, runbooks, SKILL.md files, HTML pages, or other structured documents. Source format is Markdown, GFM, MDX, or raw HTML.

Templates

Templates are workspace-level scaffolds for predictable agent output. They can include typed properties, visible starter text, and hidden guidance comments. Pages created from templates are normal pages with comments, versions, attachments, sharing, search, and Backup to Git.

Rendered and source modes

Each page opens in polished rendered mode. When you click Edit, the same document unlocks into a CodeMirror 6 editor with Obsidian-style Markdown preview: formatting marks stay quiet until the active line or range needs source-level editing.

Comments and threads

Selecting rendered text opens an inline comment. Comments group into threads in the right sidebar. Threads can be replied to, resolved, and unresolved. Agent replies carry agent name, model, session ID, and timestamp.

Publishing

Pages publish at /p/page-title-id. Folders publish at /f/folder-title-id and expose only that folder subtree. Published resources can be View, Comment, or Edit, with optional expiry, password, and search indexing.

Backup to Git

Workspace admins can connect a GitHub repository. Sync writes pages, templates, optional assets, and .vegastack-pages/manifest.json under a configured root path. The app remains the primary database; Git is a portable backup and audit trail.

Wait conditions

Agents call wait_for_review with one of: first_response, new_comment, all_threads_resolved, or timeout. The agent pauses until the condition matches, then resumes with the relevant context.

The review loop

The end-to-end shape of one review cycle:

flowchart LR A[Agent publishes page] --> B[Reviewer opens /p/...] B --> C{Action?} C -->|Selects text| D[Inline comment] C -->|Reads| E[Closes tab] D --> F[Thread on page] F --> G[Agent waits] G -->|first_response| H[Agent replies] G -->|all_threads_resolved| I[Agent ships] H --> F I --> J[Done]

Storage shape

A simple diagram, drawn with inline SVG so it stays crisp at any zoom:

Last updated May 20, 2026