Airgentic Help
The agent configuration screen opens when you click a row or the gear icon on the Configure Agents screen. Most fields are disabled for the Frontline agent.

The display name for this agent in the admin console. This is for your reference only and does not affect the agent's behaviour.
Controls who can interact with this agent.
| Status | Description |
|---|---|
| Off | The agent is disabled and will not be used. |
| Testing (Admin Chat) | The agent is active in Admin Chat only. Use this to test behaviour before going live. |
| Live | The agent is active for all users. |
The recommended workflow is to set status to Testing first, verify behaviour in Admin Chat, then switch to Live. The Frontline agent is always live and its status cannot be changed.
A plain-language description of the types of questions this agent handles. The Frontline agent reads this description when deciding whether to delegate an incoming question to this specialist.
Write a clear, concise description of the agent's domain — for example: "Handles questions about pricing, billing, and payment options."
The system prompt file used as the starting point for this agent's conversations. Select from the dropdown, which lists all available agent prompt files.
Create and edit prompt files on the Edit Prompts screen.
The Agent Prompts section lets you attach one or more prompt files to this agent and configure which functions each prompt can call.
AirScript variables are configuration values that your agent's functions can read and write at runtime. They're used to store settings like API keys, email addresses, and other values that functions need to operate.
When a function needs external configuration — such as an API endpoint, authentication token, or email address — it reads these values using air.get_config('variable_name'). This keeps sensitive data out of your function code and lets you configure different values for different agents.
| Type | Description |
|---|---|
| Regular | Stored in plain text in the agent's configuration file. Visible in the admin console. Use for non-sensitive values like email subjects, lead source labels, or template text. |
| Secret | Masked in the admin console (shown as ••••••••) and stored in an encrypted vault. Use for API keys, tokens, passwords, and other sensitive credentials. |
When you add a function to an agent (by ticking the checkbox in the Agent Prompts section), any variables that function requires are automatically created for you. The system reads the function's code, extracts all air.get_config() calls, and creates corresponding variables.
token, key, password, or secret are automatically marked as secret.You can also create, edit, and delete variables manually:
Changes to variables are saved when you click Save Agent Configuration.
In your AirScript code, read variables with:
api_key = air.get_config("api_key")
email_to = air.get_config("notification_email", "default@example.com")
You can also set variables at runtime (values persist for the conversation):
air.set_config("call_count", current_count + 1)
See AirScript Functions for full details on get_config and set_config.
A score multiplier applied to search results where the query matches the page title. A value of 3 means title matches are ranked 3× higher than body matches. Leave at 1 for no boost.
Restrict this agent's search results to pages under specific URL prefixes. Only content from URLs starting with one of these prefixes will be returned to this agent.
https://www.example.com/products/.