Studio Overview

What is Logic64 Studio

Studio is your control plane for the entire generation lifecycle. From a single browser tab you describe your project, review the architecture plan the generation engine produces, approve it, watch files stream in real time as they are generated, and receive a bundle ID the moment all checks pass. You never run a build tool or install a dependency inside Studio — that happens on your machine after you pull.

• Describe your project in plain English — no special syntax required.
• Review and edit the architecture plan before committing to generation.
• Watch live generation progress streamed directly to the Studio interface.
• Receive a bundle ID when validation passes, then pull locally with one CLI command.
• Revisit any past project from the Project Library to re-pull or re-export.

The two-phase flow

Logic64 deliberately splits workspace creation into two sequential phases: Plan and Generate. This split is not a UI convenience — it is the core mechanism that constrains hallucinations.

When you approve the plan, you lock the decision space: the framework, the architecture pattern, the file structure, the constraints. The generation engine cannot deviate from those decisions during file creation. Any output that contradicts the locked plan is caught by the validation chain and rejected before the bundle is released to you.

• Plan phase — the engine reasons about your description and produces a structured architecture plan for your review.
• Generate phase — once approved, every file is generated in an isolated server process, streamed live to Studio, and validated against the locked plan.
• No code is written speculatively. Generation only begins after explicit developer approval.

The plan phase

When you submit your project description, the generation engine enters Plan mode. It analyzes your intent and produces a structured architecture document covering the project goal, chosen framework and language, directory layout, key files to generate, and any AI assistant configuration it will include in the bundle.

You see this plan in Studio before anything is generated. You can adjust scope, swap a framework, add constraints, or clarify requirements. Only when you click Approve Plan does the engine move to generation — your approval is the gate.

• Project goal and scope summary
• Framework and language selection
• Top-level directory and file structure
• AI assistant rules file and memory file that will be included
• Any MCP server configurations or custom skills the bundle will contain

The generate phase

After you approve the plan, Logic64 dispatches generation to an isolated server process. Each generation request runs in complete isolation — no shared state with other requests, no leftover context from previous runs. The engine follows the approved plan as its single source of truth.

Studio streams live progress events as each file is produced. You can watch the workspace take shape in real time without polling or refreshing. Events include individual file completions, memory updates, tool activity, and the final bundle-ready signal.

• token — raw generation output as it streams
• state_update — phase transitions (generating, validating, complete)
• memory_update — the engine updating its working context
• tool_status — file writes and manifest operations in progress
• bundle_ready — all files generated and queued for validation
• cost_summary — generation token usage for the session
• error — any failure that stops generation early

a3f2bc89-4d1e-47a0-b8c6-2e5f91340abc

When generation completes and validation passes, Studio displays the bundle ID shown above. Copy it — you will pass it to the CLI to pull the workspace to your machine.

The validation gate

Every bundle passes an 11-step validation chain before it is released. This is Logic64's primary hallucination constraint: outputs that deviate from the locked plan, fail schema checks, or contain structurally invalid files are caught here and never reach your machine.

If any step fails, Studio surfaces a validation report explaining exactly which check failed and why. You can adjust your description or plan, then re-trigger generation. A bundle ID is only issued when all 11 checks pass.

For the full list of validation steps and how to read a failed report, see the Validation Report page.

Your projects persist

Every workspace you generate is saved to your Project Library in Studio. You can return at any time to re-pull a bundle, export it again, or review the original plan and generation events. Nothing expires between sessions.

• Re-pull any past bundle with logic64 pull <bundle-id> — the bundle remains available on the server.
• Review the original architecture plan alongside the generated files.
• Duplicate a project as the starting point for a new generation.
• Track generation cost history per project.

See the Project Library page for filtering, search, and export options.