Yesterday
A chat tab beside the work, with thin context, weak memory, and no clear way to act.
Construct Operator
The AI that works with your project,
not beside it.
Operator keeps answers, actions, specialists, and follow-through inside the same Space. It switches models for the task, reads the real state of the work, and loads the right capabilities — without turning the product into a chatbot.
Summon
Hit ShiftShift. Ask exactly what you need.
Operator runs in the background. Tap Shift twice and it comes forward, already scoped to the Space you're in — with that Space's tools in hand. No tab to switch to, no context to paste, no "as an AI…" preamble. Type what you want, get it done.
Screenshot needed
A Construct Space (e.g. Boards / Bugs) in full view. Operator panel summoned in the upper-right, scoped to the Space — header reads 'Board', tool calls listed inline (board.listTickets, board.listColumns, board.updateTicket), each ticked. Above them, the suggested action button: 'Update backlog bug to low priority'. Result line below: 'Updated Bug: UI button state in Backlog to low priority'. Composer at the bottom with 'Ask anything…' placeholder.
/shots/summon-operator.png1Shift ShiftOperator comes forward, already inside the Space you're in.
2Ask"Move the UI button bug to low priority." No prefix, no setup.
3ActOperator runs the Space's tools — list, find, update — and returns a precise result.
The Shift
One Operator. Every mode of work.
Construct does not treat AI as a side panel. Operator is part of the product layer, so planning, execution, and follow-through happen in the same system.
Today, in Construct
The Operator is part of the Space — it reads the real state, switches models, and runs actions inside the same surface.
The result
Answers, actions, verification, and follow-through all happen in one place. The work moves.
Vocabulary
Not skills. Grasps.
A skill is something you teach to someone who cannot yet do it. The model already can. What it needs is a moment of contact — the recognition that this is what the situation calls for. We call that a Grasp.
Skillwhat the industry says
Adds a capability the model does not have. Implies a curriculum, a teacher, and a learner. The wrong shape for a system that already understands more than it applies.
Graspwhat is actually happening
Brings a latent capability into contact with the work in front of it. The Operator already knows the move; the Grasp tells it which move, now, on this.
A Grasp can be:
- Reply in our voice — a Support Space loads it and Operator drafts in the team's register, not generic AI.
- Read the contract — a Legal Space loads it and Operator sees clauses, not paragraphs.
- Plan a release — a Code Space loads it and Operator returns a plan with risks and approvals, not a wall of text.
- Triage a route — a Transport Space loads it and Operator knows what counts as drift, what counts as failure, and who to page.
Capabilities
One Operator. Several powerful surfaces.
Operator is broken into explicit capability areas so teams can understand what it can do, how it behaves, and where each layer fits in the product.
Specialists, not one assistant
Architect, Coder, Project, Researcher — the right specialist takes the turn, with the same thread and the same goal in view.
Project memory that carries forward
Decisions, files, preferences, recent state. Every new turn starts where the work actually is, not from zero.
Multi-model, multimodal
Load the right model for the job. Move across text, screenshots, documents, images, and live state without flattening into chat.
Capabilities with boundaries
Browsing, tools, automation, approvals, execution — all loaded deliberately. Power without losing control.