For humans
This path is for engineers, QA leads, and platform teams who operate Molar through app.molar.it — not for coding agents that bootstrap themselves via API.
What you can do today
| Area | Available now | Notes |
|---|---|---|
| Sign up & org | ✅ | Email/password at app.molar.it; onboarding creates a project and optional app URL |
| Dashboard | ✅ | Scenarios, runs, Guard, clones, traces, billing, settings |
| CLI | ✅ | npx molar-agent init, molar login, molar scenarios validate/compile, molar run (needs Guard runner — see molar doctor) |
| GitHub App & PR gate | ✅ | Install from Settings → Organization when GITHUB_APP_SLUG is configured on the deployment |
| Cartographer crawl → scenarios | ✅ | Scouts and discoveries in the dashboard; MCP tools for IDE agents |
| Clones (local) | ✅ | molar clone stripe --start and scenario clones: blocks |
| Trace replay | ✅ | Open any run from Runs (/runs) |
| SSO / SCIM | ✅ (Business+) | /settings/sso and /settings/scim when WorkOS is configured |
| Mender auto-fix PRs | ✅ | UI at /fixbots |
| Shadow-prod diff | ✅ | Shadow-prod diff |
1. Create your workspace
- Go to app.molar.it and sign up.
- Complete onboarding — name your project and optionally enter your app URL.
- Invite teammates from Settings → Members.
- Business plans: configure SSO at Settings → Single Sign-On and SCIM at Settings → SCIM Provisioning.
Billing and plan limits: app.molar.it/billing.
2. Connect your app and GitHub
| Task | Where | What to do |
|---|---|---|
| Register app URL | Onboarding or Cartographer project | Base URL for crawls and scenarios |
| Approve flows | Scouts (/scouts) / Findings (/discoveries) | Turn crawled flows into scenarios |
| Author scenarios | Scenarios (/scenarios) or .molar/scenarios/*.molar.md | Write or approve tests |
| Install GitHub App | Settings → Organization | Required for PR gating |
| Branch protection | GitHub repo settings | Require molar/guard status check |
3. Install the CLI (optional but recommended)
npx molar-agent init
# or: npm install -g @molar/cli
Create a Personal Access Token at Settings → API Tokens, then:
molar login --api-url https://api.molar.it --token molar_pat_xxxx
Run molar doctor — local molar run also needs the Guard runner (@molar/guard-runner). See Install & initialize.
4. Run your first scenario
Dashboard path: Scenarios → pick or create one → Run → open Trace on failure.
CLI path: Your first scenario — validate, compile, and molar run.
5. Operate day to day
| Area | Dashboard route | Docs |
|---|---|---|
| PR gating | /guard/pr-gate | Guard quick start |
| Production monitoring | /guard/monitoring | Production monitoring |
| Trace replay | /runs | Trace quick start |
| Clone fleet | /clones | Clones quick start |
| Auto-fix (Mender) | /fixbots | Mender auto-fix |
| API tokens | /settings/tokens | OAuth & authentication |
| BYOK model keys | See BYOK doc | Bring your own LLM provider keys |
Inviting agents on your team
Humans own the org. When a coding agent needs cloud access:
- Mint a service token at Settings → API Tokens (preferred for CI), or
- Let the agent use Agent self-serve signup and share the 6-digit verification code from the email Molar sends you.
There is no separate “approve agent” screen in the dashboard today — verification is via the code (or molar agent signup verify).
Related
- Choose your path — eval → install → operate
- For agents — MCP and self-serve signup
- All-in-one dashboard — navigation reference for app.molar.it