Use Macrofold without running its API, workers, database, or sandbox infrastructure yourself. Give a supported agent a task, follow its progress, and keep its files for the next run. Your application calls the same API used by the dashboard and CLI.
Start with one workspace and one run. Saved agents, connected tools, and schedules can follow after your first result; ongoing agent work explains that progression.
Connect to Cloud
- Open the Cloud dashboard supplied with your account access. The SDK's default hosted origin is
https://app.macrofold.ai; if your access uses another origin, configure it explicitly. - Sign in, verify your email, and select your organization.
- Create a scoped key in API keys and store it as
MACROFOLD_API_KEYin your application's server environment. - Follow the API quickstart, use the dashboard, or copy the coding-agent setup prompt.
Cloud access is required to use the hosted endpoint. If you do not have access, you can try local simulation or deploy Macrofold yourself.
Run your agents
Choose an enabled harness and model. Managed model usage draws on your organization's credits. For BYOK, connect your model account and explicitly select that connection. Infrastructure and authorized tools may still use credits; see billing and limits.
A workspace owns a distinct file tree; its worktrees are checkouts. Reuse a worktree across runs. Different agents can take turns over the same worktree.
What you manage
You control workspaces, members, API keys, agent presets, tool grants, budgets, and cancellation. Review runs and persisted files in the dashboard. Cloud operates the underlying service; you do not need your own Vercel, Neon, or R2 account to call it.
Available models, integrations, and effective limits come from your deployment and organization. The shared feature guides describe product behavior for Cloud and self-hosting; self-hosting explains operating your own installation.