Quickstart · Pro
Register an AgileBuilder account, host templates and docs in a cloud space, then sign in from the CLI to sync them across devices
Pro adds cloud spaces on top of the open-source CLI: templates and doc resources are hosted in the cloud, and signing in on any device gives you the same library. This guide covers the full journey from registration.
Step 1: Register an account
Open the console and register:
- China console:
https://app.agilebuilder.cn - Global console:
https://app.agilebuilder.net
AgileBuilder uses pure SSO authentication — there is no standalone password. Supported sign-in methods:
- Email + verification code
- WeChat scan
- GitHub / Google accounts
On first sign-in, your account is created automatically along with a personal space — no manual setup required.
Step 2: Add resources in the console
After signing in, open your personal space. You can manage two kinds of resources online:
- Template: points to a Git repository (with optional branch and subdirectory), used to generate projects
- Doc: Markdown or plain-text content that serves as standards and context material, exposed to AI tools over MCP
Once your team's standards are recorded as doc resources, MCP-configured AI tools (such as Cursor or Claude Code) can read them in real time — see MCP Integration.
Step 3: Sign in from the CLI
In your terminal:
ag login
The CLI opens your browser to complete SSO authorization: it listens for the OAuth callback on 127.0.0.1 (starting at port 51280, probing up to 10 ports forward), then returns you to the terminal.
On machines without a browser (servers, CI), use an API key instead:
ag login --api-key <your-api-key>
Check auth status or sign out:
ag auth status # show current auth state
ag logout # clear local credentials
Step 4: Switch to your cloud space
ag space list # list every space you can see (local + cloud spaces)
ag space use <space-id> # switch to your personal space
ag space current # confirm the current space
The current space determines which resources res commands operate on, and which space create <resource-id> resolves from.
Step 5: Create a project from cloud resources
ag res list # list templates and docs in the current space
ag create <resource-id> --target ./my-app --var appName=my-app
The commands are identical to the open-source edition — the only difference is that resources come from a cloud space. Sign in on another machine with the same account and the same template library is there.
You can also add resources to a cloud space straight from the CLI:
ag res add template \
--name service-template \
--git-url https://github.com/example/service-template.git \
--branch main \
--tags "node,service"
Free, Trial, and Pro
| Free | Trial | Pro | |
|---|---|---|---|
| Sign in, view cloud spaces, use resources | ✅ | ✅ | ✅ |
| Create/edit/delete resources in cloud spaces | ❌ (read-only) | ✅ | ✅ |
| Duration | Unlimited | 14 days | Per subscription years |
| Price | ¥0 / $0 | ¥0 / $0 | China: ¥199/year; Global: $49/year |
- Each account and space can activate the 14-day Trial once, with full cloud write capability during the trial.
- After expiry (or without a subscription), a space becomes read-only: existing resources remain viewable and usable, but cannot be added or modified.
- China region accepts WeChat Pay and Alipay; the Global region accepts PayPal and Paddle. All paid orders are eligible for a refund within 14 days — see the Refund Policy.
Multi-device: run ag login separately on each machine. Use ag device list to see signed-in devices, and ag device revoke <device-id> to revoke a device remotely.
Next steps
- Quickstart · Team — shared template libraries and permissions for multiple members
- Cloud Spaces — spaces, resources, and permissions in depth
- Billing & Subscription — plans, payment, and invoices