Monaco under the hood
The same editor that powers VS Code. Syntax, autocomplete, multi-cursor, keybinds you already know.
Built in · Personal
Editor. Code, paired.
Monaco-powered editor, real terminal, Operator paired alongside. Edit, run, commit — all inside one Space, all scoped to the project you actually have open.
Screenshot needed
The Editor Space inside Construct. Left rail: file tree. Center: Monaco editor with a file open, AI ghost-text completion visible mid-line. Right: Operator panel with a multi-file diff suggestion. Bottom: integrated terminal showing test output.
/shots/space-editor.pngWhat it does
Everything you expect, paired with help.
Terminal in the same Space
A real shell at the bottom. Run tests, run servers, run anything — output stays in the Space, scoped to the project.
AI completions, in line
Operator suggests as you type, completes blocks, refactors selections. Accept with Tab, reject with Esc — keyboard-first.
Project-aware by default
Open the Space, the project context is already loaded. File tree, recent edits, open record, the lot.
Multi-file edits
Operator can edit across files in one turn — refactor a function and update its callers, change a type and propagate. Reviewed as a diff before commit.
Git, where it belongs
Branch, stage, commit, push from the Space. The terminal and Operator both know the working tree.
In practice
Three loops you'll actually run.
Quick edit, clean diff
Open a file, ask for a fix, review the diff, accept or revise. Same loop as a senior engineer pairing with you.
Refactor with confidence
"Rename this function and update every caller." Operator does the boring part; you read the diff.
New feature, scoped
"Add a settings panel here, wire it to the existing store." The change happens in the Space, with the project state in view.