Bring your own Agent
Generate personal API keys and connect external AI agents to Frontline through the CLI.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Generate personal API keys and connect external AI agents to Frontline through the CLI.
Concepts covered
Step breakdown
- Open Bring your own AgentStart in the Bring your own Agent section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
Bring your own Agent lets operators use Frontline with external AI agents and developer tools. The screen shows supported agent contexts, CLI installation, authentication, personal API keys, and Create Personal API Key.
This is the bridge between the product and external agent environments such as Claude, Cursor, Codex, ChatGPT, Windsurf, and similar tools.
What each control changes
Install Frontline CLI gives the terminal install command. Authenticate gives the login command and expects a personal API key. Create Personal API Key generates a key for agent access. Copy controls help move commands or keys into the operator's environment.
Personal API keys should be treated as credentials. Create them for specific external agent usage, rotate them if exposed, and delete keys that are no longer needed.
Operational outcome
External AI agents can work with Frontline context without asking operators to copy product data manually. That makes implementation faster while keeping access explicit and revocable.
Operational playbook
Use Bring your own Agent as part of the Frontline Admin Bring your own Agent operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Bring your own Agent control?
Generate personal API keys and connect external AI agents to Frontline through the CLI.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.