Reference Apps

UI examples for Traverse.
Same business logic (WASM agents in Traverse) → many UI shells here (Web, macOS, iOS, Android, Windows, Linux, CLI).

Start here: traverse-starter on Web (commands below).
You need: Node.js 24+ (see .nvmrc) and a local Traverse clone — set TRAVERSE_REPO and run the sync script for your platform before the app can load WASM.
Success looks like: submit a note and see title, tags, note type, next action, and status filled in by the runtime (the UI does not invent those fields).

Agents / LLMs: this repo is UI-only — render runtime fields, never compute business output. Claim work via AGENTS.md. Authoring capabilities? See traverse-framework/claude-skills. For LLM product façades (Claude / Cursor / ChatGPT / Grok via MCP), see LLM MCP reference façades below.

Apps we have built

App	What it does	Start here
traverse-starter	Submit a short note → title, tags, note type, next action, status	web · all OS
doc-approval	Paste a document → type, parties, amounts, confidence, recommendation	web
meeting-notes	Paste a transcript → action items, decisions, follow-ups, summary	web · all OS
loop	WF1 follow-through: ingest → extract → normalize → authorize (human review)	web · all OS
trace-explorer	Browse execution traces (debugger — not a product shell to copy)	web
LLM MCP façades	Claude / Cursor / ChatGPT / Grok call the same workflows via MCP (not prompt skills)	`apps/llm-mcp-reference/` · section

Extra demos / kits — useful samples, not the production OS-shell pattern to copy (prefer traverse-starter / doc-approval / meeting-notes / loop). Upgrade-or-retire classifications (Spec 004): docs/demo-inventory.md.

Demo	Path
Browser consumer façade	`apps/browser-consumer/`
youaskm3 starter kit	`apps/youaskm3-starter-kit/`

Retired demos

Path	Retired	Notes
`apps/react-demo`	2026-08-12	Spec 004 retire (#255); use primary Web shells / browser-consumer
`apps/android-demo`	2026-08-12	Spec 004 retire (#251); use primary Android Compose shells
`apps/macos-demo`	2026-08-12	Spec 004 retire (#252); use primary SwiftUI shells

By OS / target

Open the folder, then the tool named below. Full steps (sync + run) are in that folder’s README.md.

Target	Open this	Then
Web	`apps/traverse-starter/web-react/`	`npm run dev` from repo root (after web sync)
macOS	`apps/traverse-starter/macos-swift/`	Open `TraverseStarterMac.xcodeproj` in Xcode → Run
iOS	`apps/traverse-starter/ios-swift/`	Mac + Xcode: open `TraverseStarter.xcodeproj` → Run (Simulator)
Android	`apps/traverse-starter/android-compose/`	Open the folder in Android Studio → Run
Windows	`apps/traverse-starter/windows-winui/`	Open `TraverseStarter.sln` in Visual Studio (WinAppSDK). Sync script needs Git Bash/WSL
Linux (GTK)	`apps/traverse-starter/linux-gtk/`	Rust + GTK4 deps, then `cargo run` (see folder README)
CLI	`apps/traverse-starter/cli-rust/`	Rust, then `cargo run` / `cargo install` (see folder README)

Same apps on other platforms (— = not shipped yet):

App	Web	macOS	iOS	Android	Windows	Linux	CLI
traverse-starter	link	link	link	link	link	link	link
doc-approval	link	link	link	link	link	link	link
meeting-notes	link	link	link	link	link	link	link
loop	link	link	link	link	link	link	link

Same business logic on multiple OS

Logic lives in Traverse (WASM agents + workflows) — not in these UI folders.
Each OS folder under apps/<app>/ is only a shell: sync the bundle, submit input, show runtime fields.
Reuse the pattern: get one shell working (getting started), then add another OS (add-platform recipe). Sync scripts per OS: docs/runtime-bundle-sync.md.

Fastest try (Web):

git clone https://github.com/traverse-framework/Traverse.git ../Traverse
git clone https://github.com/traverse-framework/reference-apps.git
cd reference-apps
npm install
export TRAVERSE_REPO="$(cd ../Traverse && pwd)"
bash scripts/ci/sync_web_starter_bundle.sh   # required — copies runtime.wasm + manifests
npm run dev                                  # http://localhost:5173

Without TRAVERSE_REPO + sync, the embedded host has no bundle and the app will not run workflows.

Other web apps (same install; sync that app’s bundle first — see its README):

npm run dev -w apps/doc-approval/web-react
npm run dev -w apps/meeting-notes/web-react

LLM MCP reference façades

Secondary tier beside OS UI shells: LLM product façades that invoke Traverse workflows/capabilities through MCP instead of encoding business rules in prompt “skills”. Same catalog thesis as the OS apps — the model handles language; runtime-owned fields come back from Traverse.

Piece	Path
Plan / architecture	`docs/llm-reference-apps-plan.md`
Client configs + runbooks	`apps/llm-mcp-reference/`
Clients	Claude Desktop · Claude Code · Cursor · ChatGPT · Grok
Scaffold smoke	`bash scripts/ci/llm_mcp_reference_smoke.sh`

Mode A (local MCP stdio) — quick start:

export TRAVERSE_REPO="$(cd ../Traverse && pwd)"   # adjust path
cd "$TRAVERSE_REPO"
cargo run -p traverse-mcp -- stdio

Point your LLM client at that command using the example under apps/llm-mcp-reference/clients/<product>/, paste shared/prompts/system-boundary.md into system instructions, and follow shared/workflows/traverse-starter.md. Display only runtime JSON fields — do not invent title/tags/recommendations in the prompt.

Upstream gaps (blocking full kit live path)

OS shells do not speak MCP (they embed WASM). Registry MCP is the LLM façade path.

Path	Status
Expedition `traverse-mcp -- stdio`	Runnable bootstrap — not kit catalog
Spec 119 Mode A consumer scaffold	`apps/llm-mcp-reference/mode-a/` — fail-closed until the host ships
Live `traverse-starter.*` / `meeting-notes.process` via MCP	Project 2 `llm-mcp-traverse-starter-catalog` (Blocked) — needs Traverse Mode A implement (spec is Approved)

Spec 119 v1 has no kit content groups. Discovery is public registry entries. Registry umbrella #99 is closed.

More docs (when you need them)

Doc	Use when
`docs/getting-started-embedded.md`	First full walkthrough
`docs/kit-runner-persona.md`	Persona kit-runner bar (each OS)
`docs/new-app-author.md`	Create a new app id (`app new` → App-Refs layout)
`docs/llm-reference-apps-plan.md`	LLM façades via MCP (Claude / Cursor / …)
`docs/app-manifest-schema.md`	`app.manifest.json` fields + `traverse-cli app new` scaffold
`docs/add-platform-client.md`	Add another OS shell
`docs/production-playbook.md`	Ship / packaging guide
`docs/runtime-bundle-sync.md`	Which sync script for which OS
`AGENTS.md`	Claiming Project 2 tickets

Name		Name	Last commit message	Last commit date
.agents/skills/app-refs-ops		.agents/skills/app-refs-ops
.claude/commands		.claude/commands
.github		.github
.specify/memory		.specify/memory
apps		apps
ci		ci
docs		docs
fixtures		fixtures
manifests		manifests
packages/event-ui-conformance		packages/event-ui-conformance
scripts/ci		scripts/ci
vendor		vendor
.claudeignore		.claudeignore
.gitignore		.gitignore
.governance-version		.governance-version
.nvmrc		.nvmrc
AGENTS.md		AGENTS.md
CLAUDE.md		CLAUDE.md
README.md		README.md
package-lock.json		package-lock.json
package.json		package.json

Navigation Menu

Uh oh!

Repository files navigation

Reference Apps

Apps we have built

Retired demos

By OS / target

Same business logic on multiple OS

LLM MCP reference façades

Upstream gaps (blocking full kit live path)

More docs (when you need them)

About

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

Reference Apps

Apps we have built

Retired demos

By OS / target

Same business logic on multiple OS

LLM MCP reference façades

Upstream gaps (blocking full kit live path)

More docs (when you need them)

About

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages