Built in · Personal

Assistant. Summoned.

The Operator surface inside every Space. Tap Shift twice — it comes forward, already scoped to whatever you are doing. No tab to switch to, no context to paste, no parked chat panel waiting for you.

Assistant Space — Operator panel summoned over a Space
Screenshot needed

A Construct Space (e.g. Editor or Boards) in full view. Operator panel summoned in the upper-right via Shift Shift, scoped to the Space — header reads the Space name, tool calls listed, suggested action button, result line. Same look as summon-operator.png but framed as the Assistant Space.

/shots/space-assistant.png

What it does

Always there. Out of your way.

Summoned, not parked

Tap Shift twice. Operator comes forward, already scoped to the Space you are in. Esc to dismiss. No persistent chat panel taking up the rail.

Scope follows you

Open in the Editor, scoped to the file. Open in Boards, scoped to the active board. The Assistant inherits state from wherever you summoned it.

Acts where the work is

Tools fire inside the Space — list, find, update, draft, run. The result is the work being done, not a paragraph describing what you should do.

Multi-model, by task

Pick a model per task, per Space, or by data sensitivity. Cloud or local. The Assistant routes based on the rules you set.

In practice

Three ways teams actually use it.

Quick question, no context-switch

You are in the Editor. Shift Shift, ask, get the answer in-place. Back to work.

One-shot action

"Move the sidebar focus loop bug to high." The Assistant opens Boards, finds the ticket, updates it, confirms.

Cross-Space hand-off

Finish a deal in Revenue → Shift Shift → "create a Support thread for this customer." The thread carries.