Changelog.

Cloud Sandboxes (beta)

Every paid plan now includes dedicated VM sandboxes. Assign a scoped task, the agent runs it inside the sandbox, and you get a pull request back. Pause a sandbox to free the slot for another project.

• Connect Claude Code or Codex to run tasks in the cloud, no local setup required.
• Live tracking in the Command Center: statuses, comments, and flags update as the run progresses.
• GitHub integration: link a repo to the project and the sandbox opens its pull request against it.

Also shipped

• Token Analytics: per-operation token usage and spend across every project, in one usage dashboard.
• Preset Library: reusable module and feature presets that drop straight into a scope, so common builds start most of the way done.
• Export anywhere: clean JSON or Markdown export of any scope, ready to hand to any tool or agent.

A major repositioning. Scope Architect is now the missing planning layer between your idea and the AI agents that ship your code.

What's new

• Agent Handoff exports — generate a clean JSON or Markdown spec tuned for the LLM context window of Cursor, Claude Code, Devin, or Windsurf. Copy to clipboard, paste into your agent, watch it ship without follow-up clarifying questions.
• Builder Profile (replaces Studio DNA) — calibrate the engine to your tech stack, target agent, code style, and estimate unit. Same recursive engine, your defaults.
• Architect Chat as a first-class feature — refine your scope by talking to AI. Diffable change plans you preview and apply in one click.
• Dual views — Builder + Agent Handoff — full engineering surface for you, clean self-contained spec for your agent. Same source of truth, two perfect contexts.
• All AI agents supported — Cursor, Claude Code, Devin, Windsurf, plus a generic format for anything else.

What's gone

• eSign, invoicing, Stripe payment flows, polished client-facing proposal PDFs — all retired with the agency positioning. If you were using these on the old Solo/Studio/Agency plans, your lifetime access is grandfathered to the equivalent new tier.

Why

The recursive engine, structured JSON output, chat-based edits, and dual-view filtering were built for a different audience but always made more sense for AI builders. We were building this product all along — we just had the wrong target user on the box.

Architect Chat — diffable change plans

Every chat turn now produces a structured change plan you can preview before applying. No drift, no half-applied edits, no broken state.

• Preview before apply — see exactly which modules, features, and tasks will change.
• One-click apply — accept the whole plan or reject and iterate.
• Undo — full revert if you change your mind.

Recursive engine — deeper decomposition

The engine now generates acceptance criteria and dependency graphs alongside atomic tasks.

• Per-task acceptance criteria — every generated task ships with explicit "done when" conditions.
• Dependency mapping — tasks know what they depend on, surfaced for review and for export.
• Complexity flagging — high-complexity tasks get flagged for splitting before they hit your agent.

Beta access is open.

Core features

• Recursive scoping engine — turn a vague idea into modules, features, and atomic tasks.
• Project + task management — lightweight statuses (To Do, In Progress, In Review, Done).
• Dual views — different rendering modes for different audiences.
• Real-time team collaboration — multiple editors, field-level locks.
• BYOK — bring your own keys for Anthropic, OpenAI, Google, or xAI.

What's next

Architect Chat (talk to AI to refine your scope), Agent Handoff exports (one-click handoff to Cursor / Claude Code / Devin / Windsurf), and a comprehensive Builder Profile system.