Its own interface
A real UI for the job — boards, queues, dashboards, editors. Whatever the work needs.
Spaces
Open one. Get to work.
Sales has its own. Support has its own. Routes, revenue, code, notes, the messy thing nobody built software for — each gets its own. Browse what's installed, add what isn't, and switch between them like rooms in a house.
Anatomy
What a Space is made of.
Four layers — the host chrome you sign in to, the subspaces rail, the toolbar, and the content surface. Every Space is a stack of these, tuned to its workflow.
Host chromeThe window the OS gives every Space — sign-in, sidebar, theme, account.
SubspacesRail of focused views inside the Space — boards, queues, settings, automations.
ToolbarThe actions that belong to the open subspace. Create, run, approve.
ContentThe actual work surface. Boards, queues, dashboards, editors — whatever the workflow needs.
Built in
Open Construct, these are already there.
The Spaces that ship with the OS — the equivalent of what comes in the box. Anything beyond these comes from the Space Store.
For everyone
- AssistantThe Operator surface. Summon with Shift Shift — already scoped to whatever you are doing.
- AskExplore ideas, get real answers. Multi-model, multi-turn, with the right context already loaded.
- MeetPeer-to-peer video meetings — no server in the media path. Instant rooms, scheduling, invite links.
- EditorCode editor with Monaco, terminal, and AI completions.
- TUIRun Claude Code, Codex, OpenCode, or any TUI tool — direct inside Construct, sharing identity, files, and the active project.
- ProjectProject-aware agent that knows your codebase, tools, and context.
- BuilderBuild anything outside Construct — landing pages, websites, mobile apps, games. Plans, codes, ships.
- SpaceKitBuild Spaces inside Construct. Plans, codes, previews, and ships — same autonomous loop as Builder, specialized for Spaces.
When you are in an org
- OrgManage your organization — members, departments, teams, roles, and invitations.
- Org ProjectOrg-wide project management — track, clone, and coordinate shared projects.
Everything else comes from the Space Store.
Underneath
Every Space inherits from the system.
Identity, memory, models, tools, permissions — handled once at the OS level. Spaces compose against them instead of reinventing them.
Its own Operator
An AI that knows this Space, its data, its actions. Not a generic chatbot dropped on top.
Its own memory
Decisions, files, recent state, preferences — kept inside the Space, carried turn to turn.
Shared identity & files
Sign in once, access lives at the system level. Spaces inherit from the OS, not the other way around.
Permissions you control
Read-only, run-tools, auto-execute — Spaces declare what they need, you decide what to grant.
Distribution, three ways
Public on the Space Store, private to your org, or scoped to a single project. Same SDK either way.
Featured
A few of the rooms already built.
Real, opinionated surfaces — not blank canvases pretending to be flexibility. Take any of these as-is, fork it, or use it as a template.
T
Routes, dispatch, fleet
Transport
Plan routes, assign drivers, and let the Operator catch failures the moment they happen.
S
Queues, replies, resolution
Support
Triage incoming tickets, draft replies in your voice, and close the loop without leaving the queue.
R
Pipeline, deals, motion
Revenue
A pipeline that updates itself, with the Operator suggesting next steps on every card.
O
Runbooks, schedules, follow-up
Operations
The day-to-day of running a team — checked, scheduled, and chased without a separate app.
More Spaces
The built-ins are the start. The Space Store is the rest.
Browse everything published — productivity, finance, ops, games, and more — install in a click, or build the one nobody made yet.