7cdc0bc9b4
Customer-facing documentation site for Molecule AI. Built with Fumadocs (open-source MIT, Next.js 15 App Router native, Tailwind v4, MDX) so we own the deployment and aesthetic and can grow into custom doc components for our agent-canvas flows. ## Why Fumadocs (over Mintlify, Nextra, Docusaurus) - Open source, no vendor lock-in (vs Mintlify SaaS subscription) - Built on Next.js 15 App Router — matches our existing canvas stack - Less opinionated than Nextra; can grow into custom doc components - React/Tailwind first; team already on this stack - Ships search, dark mode, Shiki highlighting, MDX out of the box ## Initial structure - app/ — Next.js App Router (home + docs + search route) - content/docs/ — MDX source (3 hand-written + 9 stub pages) - lib/source.ts — Fumadocs loader bound to the MDX content - mdx-components.tsx — default + future custom MDX renderers - source.config.ts — MDX compile config ## Hand-written launch content - index.mdx — landing / what you can build / how it works - quickstart.mdx — clone repo → docker compose → import template → talk to PM - concepts.mdx — the five primitives: workspaces / plugins / channels / schedules / canvas ## Stub pages (Documentation Specialist agent fills these in on cron) - org-template, plugins, channels, schedules - architecture, api-reference, self-hosting - observability, troubleshooting ## Ownership The Documentation Specialist agent in the molecule-dev org template will own this repo end-to-end: - Watches PRs landing in the platform monorepo - Auto-opens docs PRs when public APIs / templates / plugins / channels change - Runs daily cron to backfill stubs and refresh stale pages Manual edits welcome. Agent picks up on next cron tick.
75 lines
2.2 KiB
Plaintext
75 lines
2.2 KiB
Plaintext
---
|
|
title: Quickstart
|
|
description: Spin up your first multi-agent org in under five minutes.
|
|
---
|
|
|
|
This guide gets you from zero to a running PM + Dev Lead + Engineer team
|
|
using the bundled `molecule-dev` template.
|
|
|
|
## Prerequisites
|
|
|
|
- Docker Desktop (or any Docker daemon) running locally
|
|
- Go 1.25+ and Node 22+ if you want to build the platform from source
|
|
- A Claude API key (`CLAUDE_CODE_OAUTH_TOKEN`) in your environment
|
|
|
|
## 1. Clone the monorepo
|
|
|
|
```bash
|
|
git clone https://github.com/Molecule-AI/molecule-monorepo.git
|
|
cd molecule-monorepo
|
|
```
|
|
|
|
## 2. Boot the platform
|
|
|
|
```bash
|
|
docker compose up -d --build platform canvas
|
|
```
|
|
|
|
This starts:
|
|
- **platform** (Go API on `localhost:8080`)
|
|
- **canvas** (Next.js 15 frontend on `localhost:3000`)
|
|
- **postgres** + **redis** for state and pub/sub
|
|
|
|
## 3. Import the dev template
|
|
|
|
```bash
|
|
curl -X POST http://localhost:8080/org/import \
|
|
-H 'Content-Type: application/json' \
|
|
-d '{"dir":"molecule-dev"}'
|
|
```
|
|
|
|
This provisions the 12-workspace dev team — PM, Research Lead and 3
|
|
researchers, Dev Lead and 5 engineers, plus Security/QA/UIUX auditors —
|
|
each as its own Docker container.
|
|
|
|
## 4. Open the canvas
|
|
|
|
Navigate to [http://localhost:3000](http://localhost:3000). You should
|
|
see your team rendered as a tree of nodes. Click any node to chat with
|
|
that agent directly.
|
|
|
|
## 5. Talk to PM
|
|
|
|
PM is the entry point. Send it a task:
|
|
|
|
> *"Add a 'Last seen' column to the user list table on the admin page."*
|
|
|
|
PM will break the request into specific assignments, fan them out to the
|
|
right leads in parallel, verify the results, and report back when the
|
|
work is shipped.
|
|
|
|
## What just happened
|
|
|
|
You spun up a self-organising engineering team in one command. They're
|
|
clones of real Claude Code agents — they can read your codebase, run
|
|
tests, open PRs to GitHub. Their schedules (security audit, UX audit,
|
|
template fitness checks) run hourly on their own.
|
|
|
|
## Next steps
|
|
|
|
- Customise the [Org Template](/docs/org-template) to match your team's
|
|
actual structure.
|
|
- Add [Plugins](/docs/plugins) to give specific roles new capabilities.
|
|
- Wire a [Channel](/docs/channels) so you can talk to PM from Telegram.
|
|
- Read about the [Architecture](/docs/architecture) under the hood.
|