VegaStack Pages
GitHub 1 Log in Open app

Open source · Agentic Knowledge Base

Pages your agents can write. Review your team can trust.

VegaStack Pages gives agents a real knowledge base to work in: templates, Markdown/MDX/HTML pages, source edits, anchored comments, wait conditions, version history, public links, and Backup to Git.

Works with

Agents

Works with every agent you already run.

One workspace, one permission model, one review loop. Any MCP-compatible client can create, publish, wait, patch, and close threads on the same page.

Templates

Structured output without nagging the agent.

Workspace templates define sections, typed properties, and guidance comments. Agents get the shape before they write, so a PRD, RFC, runbook, launch plan, or meeting note lands in the format your team expects.

vpg pages create --template prd --title "Search redesign" CLI
create_page (template_id) MCP
Settings / Templates Browser
guidance: State why this matters now Agent instruction

Review loop

From draft to resolved, in one loop.

Agents publish a page, reviewers leave anchored comments, the agent resumes when a wait condition matches, then patches exact source text with the current version id.

Sharing

Clean, globally unique review URLs.

Every page and folder gets a short, readable public URL. Workspace permissions and publication scopes are checked on every read, write, comment, edit, and search.

/p/agent-handoff-a8f31c000000 workspace docs · comment
/p/release-checklist-7b29e1000000 public · password protected
/p/run-postmortem-4f02d3000000 workspace runbooks · edit
/p/skill-md-1c9a5b000000 preview · noindex

Keyboard-first

Every action is one shortcut away.

Search, find, save, switch modes, close. The browser surface is built for repeated review, not one-off previews.

Editor

Source and rendered, both first-class.

Switch with one icon. CodeMirror 6 underneath, polished rendering on top. Markdown, MDX, and HTML stay source-first so agent-authored content survives round trips.

Programmatic

Agent-native MCP and CLI.

Same review semantics from a Rust CLI, an authenticated MCP session, or both at once. Create from templates, wait for review, read anchored selections, reply to threads, patch source, close the loop.

vpg mcp events
# Store explicit API auth for CLI use.
$ vpg login --workspace wks_docs --token "$VPG_TOKEN"

# Create structured output from a workspace template.
$ vpg create --workspace wks_docs --template prd --title "Search redesign" --set owner=platform

# Generate a comment-only review link with a 30-day expiry.
$ vpg publish-page pg_8f31c --permission comment --expires-at 2026-06-12T00:00:00Z

# Wait for a reviewer. Resume the agent when conditions match.
mcp.call("wait_for_review", { workspace_id: "wks_docs", page_id: "pg_8f31c", until: "first_response", timeout_ms: 600000 })
mcp.call("update_thread", { thread_id: "thr_8f31c", body: "Patched in v3", resolve: true })
Full MCP & CLI reference

FAQ

Frequently asked.

Is VegaStack Pages open source?

Yes. MIT licensed, with both managed hosting and self-hosting built from the same code. Issues and PRs live on GitHub.

Is it free?

The open-source distribution is MIT licensed. Self-hosting cost depends on your Cloudflare or Docker environment. Managed hosting at pages.vegastack.com is operated separately.

Can I self-host on Node or Docker?

Cloudflare Workers is the primary target. Node and Docker are first-class for portability, with SQLite metadata and filesystem-backed object storage. The install/cloudflare and install/docker directories ship runnable setups.

Do agents need separate accounts?

No. Agents authenticate as the workspace member who connects them. Browser MCP clients run OAuth 2.1 + PKCE against /mcp; headless tools paste a workspace-scoped token from Settings → My Connections or vpg login. Every issued token is revocable and enforced through normal workspace permissions.

What are templates for?

Templates give agents a stable structure: typed frontmatter fields, repeatable sections, and guidance comments. Built-ins cover PRDs, RFCs, runbooks, launch plans, meeting notes, and more.

Can it back up to Git?

Yes. Backup to Git syncs pages, templates, optional assets, and a manifest to a GitHub repository through a GitHub App.

Where does my data live?

Source and attachments live in R2 on Cloudflare or filesystem object storage on Node/Docker. Metadata, permissions, comments, sessions, and search live in D1 or SQLite.

How do public review links work?

Every page has a globally unique /p/page-title-id URL and every folder can publish at /f/folder-title-id. You pick view, comment, or edit, plus optional expiry and password. Public pages default to noindex.

Can guests comment without an account?

Yes. Guest reviewers enter a display name once and can comment or edit if the link permits. Their identity is recorded on the thread so agents can attribute replies.

Get started

Pick a path. Ship the first page today.

Both modes share the same app, renderer, comments, permissions, MCP endpoint, and CLI. Managed is a configuration, not a fork.

Cloud

Managed at pages.vegastack.com

Sign up, get a workspace, ship the first review page in under a minute. MCP is available at /mcp.

  • Public signup with magic-link auth
  • Workspaces seeded with starter pages
  • Templates, comments, public links, search, and MCP included
Self-host

One command on Cloudflare or Docker

Cloudflare Workers is the primary target. Node and Docker are first-class for portability. Everything else lives in MIT-licensed code.

  • install/cloudflare with Workers, D1, and R2
  • install/docker with SQLite and filesystem storage
  • Filesystem-backed object storage on the Node side