liveplanner in Your Developer Tools

Work in a plan inside your developer tool, signed in, and talk to your agent about what you select.

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.

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.

Building a tool of your own? Building a Workbench has the full integration contract.

Pair a Workbench Once

A workbench opens your plans 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:

liveplanner workbench pair --origin https://127.0.0.1:5175 --name "Acme Editor"

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 plans with the token liveplanner CLI? Check the address: it is what liveplanner 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 Plan

The workbench does this for you when you open a plan in it. By hand:

liveplanner workbench open "Sprint 14" --origin https://127.0.0.1:5175 --json

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 Workspace

A workbench can also keep your Explorer beside your code: Home, your folders, your teams' plans, the Inbox, Recent and the Trash, with every plan opening in the same view and a Back to where you were. New Plan makes the plan 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:

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.

Talk to Your Agent About a Selection

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:

[liveplanner] "Sprint 14" › tab "Board" (project 4cd7082b-…, tab 8bf8, rev 41)
selected: plan-board 0933
read: liveplanner tab view 4cd7082b-… --tab 8bf8 --view show --ref 0933

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 Unpair

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 API Tokens under Account: each token lists its Paired workbenches, each with what it may open (One plan at a time or Whole workspace), and Unpair turns their open plans read-only straight away. Revoking the token does the same for every tool it paired.

Was this article helpful?