Your Work in Your Developer Tools

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

Applies To

livediagram, liveplanner, livedocuments and livedesign

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

Pair a Workbench Once

A 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 File

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' 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:

Talk to Your Agent About a Selection

Stop or Unpair

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us