Skip to main content

πŸ› οΈ Agent Settings

Agent Settings control the agent's general behavior in your server β€” its command prefix, its language, who can manage it, and whether it runs under your own branded Discord bot instead of the default Fren One agent.

Overview​

From this page you can:

  • Set the command prefix the agent responds to
  • Choose the agent's language for server-facing messages
  • Grant agent admin roles so trusted staff can manage the agent without holding Discord Administrator
  • Deploy a Custom Bot β€” the agent runs under your own bot's name and avatar

Configuration​

To configure agent settings:

  1. Open your project in the Fren One webapp.
  2. Select the Discord server you want to configure.
  3. In the sidebar under Agent Configuration, select Agent Settings.

The page has two cards: guild settings (saved together via the Save bar) and Custom Bot (immediate actions).

Guild settings​

OptionDescription
Command PrefixThe prefix for text commands. Required; up to 5 characters. Default: !.
LanguageThe agent's language. Required. Options: English, EspaΓ±ol, FranΓ§ais, Deutsch, PortuguΓͺs, Русский, δΈ­ζ–‡, ζ—₯本θͺž, ν•œκ΅­μ–΄. Default: English.

Agent admin roles​

"Agent admin roles" is a role multi-select with real reach β€” treat it as your agent staff list. Members with any of these roles can:

  • Manage the agent's settings from Discord (they appear on the /botadmin list), and
  • Join your Fren One project as verified admins β€” they pass the project's admin verification for this server without holding Discord Administrator.

That second point is the usual way to onboard staff who help run the agent but aren't Discord admins: create a role for them, grant it in Discord, and add it here. They can then verify into the project and use the full Agent Configuration dashboard for this server.

Two safeguards apply:

  • Only real Discord admins and the server owner can edit this list. Someone who gained access through an agent admin role can change the prefix and language, but the "Agent admin roles" field isn't shown to them β€” agent admins can't grant agent admin.
  • Adding a role with more than 15 members asks for confirmation first, spelling out how many members would gain access to the agent's settings.
Grant agent admin deliberately

Every member holding an agent admin role can reconfigure the agent and verify into your Fren One project as an admin of this server. Prefer a small, dedicated role over adding a broad community role.

Custom Bot​

The Custom Bot card runs the agent under your own branded Discord bot β€” your bot's name and avatar instead of ours. Paste a bot token from the Discord Developer Portal (your application β†’ Bot β†’ Reset Token) into the "Bot token" field and select "Deploy bot". The token is validated before it's stored β€” Discord rejects invalid tokens immediately β€” then stored encrypted and never shown again.

Once deployed, the card shows a green "Deployed" badge with the name your bot is running as, plus a "Remove custom bot" button. Removing asks for confirmation: the agent switches back to the default Fren One bot in this server and your custom bot stops running. You can re-deploy later with a token.

How it works in Discord​

Members of agent admin roles can manage the agent's settings directly in Discord, and the /botadmin command (which requires Discord Administrator) lets server admins view and manage that list from Discord too. Agent admins are also treated as staff by the agent's protections β€” for example, the word filter never actions them.

With a custom bot deployed, everything the agent does in the server β€” messages, embeds, moderation actions β€” appears under your bot's name and avatar.

Saving your changes​

The guild settings card uses a batched save β€” Command Prefix, Language, and Agent admin roles stay local until you select Save in the bar at the bottom of the page, and leaving with unsaved changes shows a warning. The Custom Bot card is different: "Deploy bot" and "Remove custom bot" are immediate actions (remove asks for confirmation first).

Best practices​

Managing agent access
  • Create a dedicated role (for example "Agent Admin") rather than reusing a broad staff role β€” the 15-member confirmation prompt is a hint you're granting too widely.
  • After adding a role here, tell those staff members to open the server in the Fren One webapp and verify β€” that's how they unlock the dashboard.
  • For a custom bot, generate the token with Reset Token in the Discord Developer Portal right before deploying, and never share it β€” it grants full control of your bot.
  • Remove a custom bot from this page, not by kicking it from the server β€” kicking the branded bot leaves the community in a degraded state.
Troubleshooting

You can't see the "Agent admin roles" field?

  • It only appears for real Discord admins and the server owner. If your access comes from an agent admin role, you can edit the prefix and language but not the admin-roles list.

A staff member can't verify into the project?

  • Confirm they actually hold one of the configured agent admin roles in Discord (or Discord admin permissions), and that the roles were saved via the Save bar.

"Deploy bot" rejects your token?

  • Tokens are validated with Discord before being stored. Generate a fresh one via your application β†’ Bot β†’ Reset Token in the Discord Developer Portal and paste it immediately β€” a token is only shown once.

On this page