In livediagram, livedocuments and livedesign
A workbench is a developer tool that shows a every app file live beside a coding agent. You draw in the editor right there, everything reaches every app at once, and when you type a message to your agent, the tool attaches what you had selected so the agent reads exactly those elements.
In liveplanner
A workbench is a developer tool that shows a liveplanner plan live beside a coding agent. You work in the editor right there (move cards, fill in a sheet, check a dashboard), everything reaches liveplanner at once, and when you type a message to your agent, the tool attaches what you had selected so the agent reads exactly that.
In livediagram
The editor in a workbench is signed in as you, for one canvas at a time. It has the canvas, the tab bar, the palette and the panels; account settings, sharing and your canvas library stay in livediagram itself, one click away through Open in livediagram .
In liveplanner
The editor in a workbench is signed in as you, for one plan at a time. It has the plan's tabs, its boards, sheets, dashboards and forms, and the controls around them; account settings, sharing and your plan library stay in liveplanner itself, one click away through Open in liveplanner .
In livedocuments and livedesign
The editor in a workbench is signed in as you, for one file at a time. It has the canvas, the tab bar, the palette and the panels; account settings, sharing and your file library stay in every app itself, one click away through Open in every app .
Building a tool of your own? Building a Workbench has the full integration contract.
Pair a Workbench OnceA workbench opens your files through your CLI sign-in, and only after you have allowed it. The first time, the tool asks you to approve it, or you can pair it yourself:
The command prints a link and, in a terminal, opens it in your browser: a page headed Allow this workbench? , asking Allow Acme Editor at https://127.0.0.1:5175 to open your files with the token every app CLI? Check the address: it is what every app enforces, while the name is only a label. Choose Allow , and the command finishes by itself. Don't allow pairs nothing.
Pairing belongs to one CLI sign-in and one address. If someone obtained your token, it would still open nothing in a tool you never allowed.
Open a FileIn liveplanner, livedocuments and livedesign
The workbench does this for you when you open a file in it. By hand:
It prints a link that works once, within a minute, and only inside the workbench at that address. Opened anywhere else, the page shows This view opens only inside the workbench's address and does nothing.
Open Your Whole WorkspaceA workbench can also keep your Explorer beside your code: Home, your folders, your teams' files, the Inbox, Recent and the Trash, with every file opening in the same view and a Back to where you were. New File makes the file right there. Your account stays out of it: no Settings, no API tokens, no team administration.
The whole workspace is a second approval, even for a tool you already paired:
In livediagram
livediagram workbench pair --origin https://127.0.0.1:5175 --name "Acme Editor" --workspace
livediagram folder ls
livediagram workbench open --workspace --folder Minigames --origin https://127.0.0.1:5175 --json
The page asks Allow Acme Editor at https://127.0.0.1:5175 to open your whole workspace in livediagram, and to create, move, share and trash canvases and folders in it, with the token livediagram CLI? A token made read-only gives a workspace that browses and reads. livediagram folder create <name> [--in <folder>] makes a folder for a project and prints its id.
In liveplanner
liveplanner workbench pair --origin https://127.0.0.1:5175 --name "Acme Editor" --workspace
liveplanner folder ls
liveplanner workbench open --workspace --folder Minigames --origin https://127.0.0.1:5175 --json
The page asks Allow Acme Editor at https://127.0.0.1:5175 to open your whole workspace, and to create, move, share and trash plans and folders in it, with the token liveplanner CLI? A token made read-only gives a workspace that browses and reads. liveplanner folder create <name> [--in <folder>] makes a folder for a plan and prints its id.
In livedocuments
livedocuments workbench pair --origin https://127.0.0.1:5175 --name "Acme Editor" --workspace
livedocuments folder ls
livedocuments workbench open --workspace --folder Minigames --origin https://127.0.0.1:5175 --json
The page asks Allow Acme Editor at https://127.0.0.1:5175 to open your whole workspace, and to create, move, share and trash documents and folders in it, with the token livedocuments CLI? A token made read-only gives a workspace that browses and reads. livedocuments folder create <name> [--in <folder>] makes a folder for a project and prints its id.
In livedesign
livedesign workbench pair --origin https://127.0.0.1:5175 --name "Acme Editor" --workspace
livedesign folder ls
livedesign workbench open --workspace --folder Minigames --origin https://127.0.0.1:5175 --json
The page asks Allow Acme Editor at https://127.0.0.1:5175 to open your whole workspace, and to create, move, share and trash designs and folders in it, with the token livedesign CLI? A token made read-only gives a workspace that browses and reads. livedesign folder create <name> [--in <folder>] makes a folder for a project and prints its id.
Talk to Your Agent About a SelectionIn livediagram, livedocuments and livedesign
Select elements, then type your message. The workbench adds a short block to it, naming the file, the tab and each selected element, for example:
In liveplanner
Select something on the tab, such as a board or a sheet, then type your message. The workbench adds a short block to it, naming the plan, the tab and what you selected, for example:
In livediagram
[livediagram] "Home screen" › tab "Wireframe" (doc 3h9x2a, tab 0b34, rev 41)
selected: button 146b "Play", frame e4a8 "Game grid"
read: livediagram tab view 3h9x2a --tab 0b34 --view show --ref 146b
In livedocuments
[livedocuments] "Launch plan" › tab "Overview" (doc 3h9x2a, tab 0b34, rev 41)
selected: square 146b "Kick-off", stack e4a8 "Milestones"
read: livedocuments tab view 3h9x2a --tab 0b34 --view show --ref 146b
In livedesign
[livedesign] "Home screen" › tab "Wireframe" (doc 3h9x2a, tab 0b34, rev 41)
selected: button 146b "Play", frame e4a8 "Game grid"
read: livedesign tab view 3h9x2a --tab 0b34 --view show --ref 146b
In livediagram, livedocuments and livedesign
With nothing selected, it names the whole tab. The block is plain text in your message, nothing hidden. Your agent reads the elements with the CLI and its changes appear in the editor as you watch, with an Undo on each.
In liveplanner
With nothing selected, it names the whole tab. The block is plain text in your message, nothing hidden. Your agent reads the tab with the CLI, and its changes appear in the editor as you watch; a change to the tab itself comes with an Undo .
Stop or UnpairIn livediagram
A workbench session lasts a working day and renews itself while the tool is open. To stop a tool for good, go to Settings , then Developers , API Tokens : it lists your Paired workbenches , each with what it may open (One canvas at a time or Whole workspace ), and Unpair (which asks first) turns their open diagrams read-only straight away, until you allow the tool again. Revoking the token does the same for every tool it paired.
In liveplanner
A workbench session lasts a working day and renews itself while the tool is open. To stop a tool for good, go to Settings , then Developers , API Tokens : Paired workbenches lists each tool by name and address, with what it may open (One plan at a time or Whole workspace ), and Unpair turns its open plans read-only straight away. Revoking the token, in the same place, does the same, within a few minutes, for every tool it paired.
In livedocuments and livedesign
A workbench session lasts a working day and renews itself while the tool is open. To stop a tool for good, go to Settings , then Developers , API Tokens : it lists your Paired workbenches , each with what it may open (One file at a time or Whole workspace ), and Unpair turns their open files read-only straight away. Revoking the token does the same for every tool it paired.