Each person can hold up to five personal keys. Create one, copy it once, and treat it like a password.

The page gives you the two commands.

npm install -g @getfrontline/cli

frontline auth login YOUR_API_KEY

Paste your key in place of YOUR_API_KEY. Send to Claude puts the same setup in Claude’s hands. Copy works for Cursor, Codex, or any other agent.

frontline auth login stores the key in a local profile and points at the production API. The max CLI shares that login, so Max commands work with the same key.

After login, frontline auth whoami confirms the account and user.

Anything the CLI covers. Create and debug workflows. Build agent playbooks. Add knowledge base URLs. Create custom tools from API docs. List connectors. Inspect conversations. Assign a WhatsApp number to an agent.

You can also build and configure the CRM itself. Create or modify custom objects, record types, fields, relationships, views, and tables. Rename or extend entities as the operating model changes, and inspect the current schema before making a change.

At the record level, the CLI and coding agent can search, create, update, or delete People, Companies, Deals, Tickets, custom-object records, and table rows, subject to your permissions. They can move a Person between record types, connect related records, fill fields, and log notes, calls, meetings, emails, or WhatsApp activity on the timeline.

That makes headless Frontline useful for both setup and ongoing operations. A coding agent can build the CRM model from a written brief, import or clean a book, update hundreds of records against a rule, and then create the workflow that keeps the model current.

Harrington’s ops lead opens Claude Code, pastes the install and login, and says: “Create a workflow that scores new People, using the Lead Scoring pattern we use in Studio.” The agent reads the graph, adds nodes, and checks a run.

The same agent can first inspect the CRM, add a Mandate record type and its fields, create or update Harrington records, relate the Deal to the right People and Company, and then automate what happens next.

A personal key is user-scoped. Writes are attributed to you. Account-level keys from Developer will not work on these commands. If a command returns unauthorized, you are on the wrong key type.

Share the key only in that agent’s private session. Then give it the two commands and the job.

“Install the Frontline CLI, log in with this personal key, list workflows, and add a Conversation Idle path that sends a WhatsApp follow-up on the qualifying agent.”

For CRM work, name the model and the intended change. “Inspect People, Companies, and Deals. Add the Mandate fields from this specification without duplicating existing fields. Update these records, preserve unique email and phone, and show me what changed.”

Keep keys rotated. Delete one from Bring your own Agent when a laptop or a contractor engagement ends, then create a replacement.