Skip to main content
Common developer commands for 0.1.0-beta.21. Use command-specific help for the full reference. Start with Connect and test for the complete sequence. Use chert --help for short help, chert dev --help for one command, chert --help --all for advanced commands, and chert --version for your version. Developer commands support --json for machine-readable output.

Additional developer commands

These commands exist in beta.21. Server access and current capacity still decide whether a requested service is available. Use command-specific --help before changing a connection, file, or plan. See Personal-agent integration for the distinction between CLI commands and SDK methods.

Credential loading

Run dev and doctor from your agent folder. They automatically read LIVEKIT_URL, LIVEKIT_API_KEY, and LIVEKIT_API_SECRET from .env.local or .env and report which file they used. The Chert project comes from browser sign-in unless you explicitly select one or have saved setup. LiveKit values are selected in this order:
  1. Existing shell environment values take priority.
  2. --env-file PATH selects an explicit file, if supplied.
  3. Otherwise, an env-file path saved by chert setup is used.
  4. Otherwise, the CLI checks .env.local, then .env, in the current folder.
Folder discovery stops at the first readable file that fills a missing LiveKit value. It does not combine both files, search parent folders, or override shell values. Explicit or saved file errors are reported rather than silently falling back to another file. The CLI also reads AGENT_NAME for agent-name discovery. Chert sign-in, endpoint overrides and model keys are not imported. Files are parsed as data, never executed as shell code. --project UUID overrides a saved project; otherwise the signed-in project is used when no project is saved. This does not grant access to another project. If old saved settings point to another project or folder, stop the connector and run chert setup --clear to use folder loading and your signed-in project.

chert login

Sign this computer in to your Chert project. Opens your browser to approve this computer for one project. It then stays signed in for 30 days. In a terminal you choose with 1, 2, 3 or the arrow keys.
Examples:

chert new

Create a new voice or video agent folder from the bundled starter:
The command creates .env.local with an agent name; add your own LiveKit and model credentials. It refuses to overwrite a folder containing files. --video selects code that publishes a drawn face; it does not enable caller-camera input. See Audio, video, and caller vision.

chert dev

Put your LiveKit agent on your line until you press Ctrl+C. Claims your project’s FaceTime line, keeps a room ready with your agent in it, and answers inbound FaceTime Audio and Video calls with that agent, without a webhook. Start your agent first. Ctrl+C requests cleanup and line release; wait for confirmation. The caller chooses the call type. There is no dev --video flag. Configure your agent’s publications and subscriptions as described in the video guide; --muse is not a general video switch.
Examples:

chert doctor

Check sign-in, LiveKit keys, the line and your agent. Runs each check chert dev depends on and says what to fix. With —agent it also sends your agent a test job and times how long it takes to join.
Examples:

chert whoami

Show who is signed in, and to which project. Asks Chert, so it also tells you when a sign-in was revoked. Offline, it shows what is saved and says it could not confirm it.
This command has no flags of its own. Examples:

chert logout

Sign out and revoke this computer. Removes the saved sign-in and revokes it at Chert, so it cannot be used again from anywhere.
This command has no flags of its own. Examples:

chert setup

Optionally save a project and an env file as defaults for dev and doctor. Useful when running outside your agent folder. These defaults take priority over automatic folder loading. Only the project UUID and absolute file path are saved, never the keys. New users running from the agent folder can skip this command.
Examples:

Exit codes

  • 0 success
  • 1 internal
  • 2 usage
  • 3 not ready or not signed in
  • 4 state
  • 5 unsupported runtime
  • 6 network or server
  • 130 cancelled

Advanced commands

The connector and enrollment commands (init, check, byor, create-room, run, status, projects, lines, bindings, enroll, activate, drain, revoke) are for operating a connector by hand. chert dev does all of that for you. Run chert --help --all to see them, and read Advanced connector commands.