Logic64
Start
GuidesAPI ReferenceExamplesPricingHelp Center
Get StartedQuick Start

Quick Start

Need unlimited generations and frontier models? Architect Pro — unlimited validated workspaces, Claude Opus, and priority queue for $20/month. See plans →

Logic64 turns a plain-English project description into a fully validated, hallucination-constrained codebase bundle. The Engine generates your workspace server-side, validates every file against strict schemas, then packages everything into a bundle.zip that you pull directly onto your machine with one command.

This guide walks you through generating your first workspace — from creating an API key to pulling the bundle locally — in under five minutes.

Getting Started

1Get an API Key

Personal API keys are available on Developer and Architect Pro plans. Each key is scoped to your account and never shared.

  • Go to Logic64 Studio and register or log in.
  • Open Billing and activate a Developer or Architect Pro plan.
  • Generate a key from Settings → API Keys.
  • Copy the key — it is displayed only once. Keys follow the format l64_xxxxxxxx_xxxxxxxx….

Logic64 Studio

Sign up or log in to the workspace dashboard.

API Keys

Create and rotate your personal API key.

2Install the CLI

Install the logic64-cli package globally with npm, then authenticate using the API key you just generated. The --api-url flag points the CLI at the Logic64 backend — required on first setup.

bash
$ npm install -g logic64-cli
$ logic64 auth --api-key l64_YOUR_API_KEY --api-url https://api.logic64.com
# ✓ Authenticated. Key stored in ~/.logic64/config.json

3Create your first workspace

Logic64 Studio runs a two-phase flow: plan first, then generate. The plan phase locks your stack and architecture decisions before a single file is written.

  • Open a new project in Studio and describe your goal in plain English.
  • Logic64 produces an architecture plan — review it, adjust scope, framework, or constraints, and approve it.
  • Click Generate. The Engine runs in an isolated server process and streams live progress events to Studio.
  • Every file passes an 11-step schema validation chain. When all checks pass, you receive a bundle_id.

4Pull it locally

Run logic64 pull with the bundle ID shown in Studio. The CLI downloads the ZIP, reads manifest.json inside it, and routes each file to the correct destination — project root, global config, or skills directory.

bash
$ logic64 pull a3f2bc89-4d1e-47a0-b8c6-2e5f91340abc
# ↓ Downloading bundle a3f2bc89
# ✓ 23 files written — project scaffold, CLAUDE.md, memory.md, MCP configs
# ✓ Config merged into ~/.config/claude-code/config.json
# ✓ resolution_log.json written to project root
# → Next: cd my-workspace && pnpm install

Every pull is fully transparent: resolution_log.json records every file written, every config merge, and every port or name conflict that was auto-resolved. Global config files are backed up before any change so you can roll back with logic64 rollback <bundle_id> at any time.

What's next

Once you have your first workspace running locally, the next step is to understand how Logic64 enforces consistency across generated code — and how to use the API to integrate Logic64 into your own tooling.

Core Concepts

How the plan → generate → pull flow works and what the Hallucination-Constrained Architecture means in practice.

CLI Reference

Every command and flag: pull, rollback, auth, status, and export.

API Reference

REST endpoints for bundle download, project management, and ACK confirmation.

Validation Report

Understand the 11-step validation chain and why a bundle may be rejected before delivery.

NextIntroduction