Workspace

Unified coding surface with Monaco, agent edits, preview, and diagnostics

Workspace

Workspace is the canonical in-app coding surface in ReformCode. It now uses one VS Code-like interface with two product modes.

It replaces the old split between Code Editor, Workbench, and Builder with one shared shell:

  • REFORM Mode starts from existing repositories, packages, or snippets and remixes them into a starter for your needs.
  • CODE Mode starts from the active workspace and lets you generate, edit, preview, connect Git workflows, validate, and ship.
  • Shared infrastructure powers tabs, change review, preview/runtime, diagnostics, GitHub export, and session recovery.

What Workspace Includes

  • CODE Cockpit command center with live files/tabs, agent timeline, terminal output, problems, Git proof, workflow queue, and the Git-preview-deploy proof loop
  • Monaco-based editing with file tree and tabs
  • Agent chat with staged patch review before apply
  • Problems panel for Monaco and runtime diagnostics
  • Preview panel with local frontend preview or remote runtime contract
  • Export and GitHub sync from the same canonical file model
  • Open in CODE handoffs from repo views and REFORM workflows
  • Local IDE bridge sync from VS Code into persisted CODE sessions
  • Session history that reopens builder projects and editor drafts inside Workspace

Opening Workspace

Use CODE to open the AI coding IDE directly, or use REFORM when you want to transform existing code first.

  • repo views expose Open in CODE so repository snapshots can hydrate the IDE directly
  • history entry points reopen existing CODE and REFORM sessions
  • REFORM transformations should hand off cleaned starters into CODE for build-out

File And Session Model

Workspace uses one multi-file state contract for:

  • canonical file paths
  • open tabs and active file
  • staged agent changes
  • diagnostics
  • preview/runtime state
  • revision history

That model is the source of truth for local restore, builder persistence, repo imports, GitHub export, and ZIP export.

CODE Cockpit Command Mode

CODE now keeps the daily work loop visible in one strip instead of hiding it behind separate tools:

  • Files & Tabs shows the active file and open tab count.
  • Agent Timeline shows whether the architect, implementer, reviewer, tester, and security lanes are idle, running, blocked, or waiting for review.
  • Preview and Terminal Output surface runtime readiness, last command, recent logs, and failures.
  • Problems aggregates Monaco, validation, security, preview, and runtime diagnostics.
  • Git Proof shows changed files and opens the GitHub export workflow.
  • Workflow Queue launches API, database, and test generation against the same workspace context.
  • Proof Loop exposes workspace changes, preview smoke, validation, branch, commit, PR, deploy certification, rollback, and report-history evidence in one visible chain.

Use ⌘K / Ctrl+K or the cockpit command button to find files, switch panels, open Git export, inspect runtime output, review proof blockers, or open evidence reports.

Git, Preview, And Deploy Proof Loop

Every CODE change now has a proof-loop model before it is considered shippable:

  • Workspace Changes confirms a meaningful file diff or unsaved workspace state exists.
  • Preview Smoke confirms the preview/runtime surface is ready and not blocked by errors.
  • Validation keeps the current validation score, blockers, and warnings attached to the change.
  • Git Branch, Commit, and Pull Request capture the GitHub export branch plus commit/PR evidence when available.
  • Deploy Certification and Rollback reserve the deploy-proof lane for build, environment, smoke, readiness, security, and rollback evidence.
  • Report History routes the final evidence package into Reports so shipped work leaves an auditable trail.

The cockpit proof card shows the completed stage count and next action. GitHub export success records branch and commit evidence immediately, while any file edit clears stale Git proof so users do not accidentally ship a changed workspace against old evidence.

Local IDE And VS Code Bridge

The VS Code extension can now push a local workspace into CODE without turning local editing into a disconnected lane:

  • ReformCode: Open Current Workspace in ReformCode CODE syncs selected files and opens the persisted CODE builder session.
  • ReformCode: Push Workspace with Proof Metadata syncs files with branch, remote, commit, CODE URL, VS Code URI, reports URL, and proof-loop status.
  • ReformCode: Copy CODE Bridge Link creates a shareable /code?builderSession=...&bridge=local-ide link.
  • ReformCode: Open ReformCode Evidence Reports opens the reports surface attached to the latest bridge session.
  • /.reformcode/local-ide-bridge.json is added to the CODE workspace so the proof trail travels with the imported files.

The bridge accepts browser sessions or API keys with workspace:write, enforces file count/size limits server-side, and stores only the workspace folder name rather than the absolute local path.

Legacy Notes

Older docs may still mention Builder or Workbench as separate surfaces. Treat those as legacy terms. Workspace is the authoritative coding experience in the shipped product.