CLI and API keys

Account and server required

The CLI connects to the server API. It does not read projects that exist only in another browser’s local workspace.

For the complete agent setup, start with connect your agent. The CLI also works directly from a terminal or another agent.

Create an API key

Open API keys in the account menu. Create a key with a name that describes its purpose, then copy it into the tool that needs access.

Treat the key as an account credential. Keep it out of documents, screenshots, source control, and shared chat messages. Revoke a key from the account menu when it is no longer needed or may have been exposed.

Install and connect the CLI

Install the published CLI with Node.js available:

npm install -g tylor-cli@latest

Set TYLOR_API_KEY in your local environment to the key you created. Set TYLOR_API_URL to your instance’s API endpoint (the default is https://api.tylor.app). Then run:

tylor list

The key acts with your account’s permissions. See the CLI reference for configuration and the full command list.

Use automation with an open editor

External tools work with saved server files. Wait for browser edits to sync before asking a tool to modify the same project. When returning to the editor, follow any update or reload message and check the resulting document.

Keep a history checkpoint or backup before broad automated edits. Verify the final source and PDF, even if an agent reports that compilation succeeded.