Self-serve setup
For a new personal project, use the Chert app orchert onboard to sign in, verify your phone, and request an eligible line.
Onboarding can offer a demo and agent setup; allocation depends on capacity and
plan. chert login connects this computer to an existing project instead.
For a workshop or an existing customer line, follow the organizer path below.
Do not create another project when an existing allocation is waiting or needs
attention. See Dashboard for verification and billing.
Chert setup: organizer or project administrator
Before a student starts, the organizer must arrange:- A Chert account with owner or admin access to the intended workshop project.
The current CLI cannot claim a line with the
memberrole. - Exactly one assigned FaceTime line in that Chert project. If none is
assigned, get one with
chert onboardor in the Chert app; installing the CLI does not create one. - In the FaceTime dashboard, verify the selected
project’s Workers & Lines configuration: inbound policy customer decides
(
customer_decides) and no default hosted assistant. Coordinate this change with the line owner before using a line that serves other traffic. - Confirm the line is online, supports the intended audio and video directions, and is reserved for the team. An available line is not necessarily ready to answer.
- Give the student the Chert project name and UUID, actual FaceTime address, and testing time slot. See the organizer checklist.
LiveKit setup: each team
Usechert livekit when Chert offers keys for your eligible paid Shared project.
Otherwise create your own LiveKit Cloud account, create a project,
and obtain that project’s URL, API key, and API secret. Put them privately in
.env.local as shown in Build your agent.
Use the same credentials for the agent and Chert CLI. A LiveKit project does not
create a Chert line or grant Chert access.
Connect your computer: each student/operator
Once Chert access is assigned and CLI beta.21 is installed, run these from your agent folder, which holds.env.local:
dev and doctor read the three LiveKit
values from this folder’s .env.local (or .env); no separate setup is needed.
A Chert UUID is not a LiveKit project name or API key.
To run from another folder, optionally save defaults:
PROJECT_UUID with the approved Chert project’s UUID. Saved defaults
retain priority over folder loading. See credential loading.
No manual
enroll or activate command is needed for chert dev, for either
FaceTime Audio or FaceTime Video. Neither call type requires a webhook. Video
still requires an appropriately configured line and agent; see the
video guide.
Switch projects or hand off a line
End the call and stopchert dev; wait for line release before another operator
starts. To switch Chert projects, run chert login and approve the new project,
then run from the new agent folder with its matching LiveKit credentials.
If you have saved setup, clear it with chert setup --clear or replace it with
the matching UUID and env-file path. Also remove stale shell LiveKit overrides.
Changing --project alone cannot expand the scope of an existing browser login.
Only one connected CLI and one active call can use a line at a time. Coordinate
handoffs; --takeover replaces another session and is not a routine setup step.
chert setup --clear removes saved defaults but does not sign you out or release
an active line. Stop the connector before chert logout.
For custom callback/hook connectors, use manual enrollment.
