Limits & safety

BotFather is deliberately bounded. It performs real actions on your workspace, so the safety model matters: it acts only from an approved set of operations, always as you, and it declines cleanly when a request falls outside that set instead of improvising. This page is the honest inventory of what it will not do.

It only acts from an approved set

The actions BotFather can take are a closed list, not a starting point it improvises from. When a request maps to a real, listed operation, it does it. When it doesn't, BotFather says so plainly rather than reaching for something close:

• No listed action means unsupported. Ask it to rename or delete something the platform only lets it read, and it tells you that isn't available. It does not fake it with a workaround.
• It never guesses its way to a capability. It won't try one endpoint, then another, hunting for one that happens to work. If the first thing it reaches for isn't a supported action, it stops and tells you.
• It never invents an operation. There is no "the AI found a way", the set is finite and known.

It acts as you, on the platform only

Every action goes through the same platform API the dashboard uses, authenticated with your session, so it inherits your permissions exactly and can't exceed them. Two hard boundaries follow:

• BotFather talks only to the AnyBot platform. It is not a general web agent. It cannot reach arbitrary systems or run code on your machine.
• If your session is about to expire mid-task, it stops and asks you to refresh and resend rather than firing a call that would fail halfway.

Destructive actions

Deleting a BotFather conversation asks you to confirm first ("This action can't be undone"). That removes the chat, not your data.

For your actual platform data, the protection is structural rather than a pop-up on every step:

• It won't fake an edit by deleting and recreating. A contact, agent, lead, or conversation carries real linked history; recreating it would orphan that. If an edit isn't a supported action, BotFather states the boundary and stops.
• It won't hijack a shared resource. It will not re-point an integration that already belongs to another agent. That would silently remove it there. It installs a new one for your agent instead.

Tools it does not have

Some capabilities simply are not wired in the current build. BotFather returns an explicit "not available" for these. It will not pretend a tool ran:

• No voice mode. BotFather is text, plus files and workspace entities you attach. There is no talk-to-it audio mode.
• No PDF export. It cannot generate a PDF or other downloadable file. Ask for a document and it offers the content inline (for example, as a copyable block) instead.
• No web search. It cannot search the open web. It can read a specific public URL you paste in and use that page's text, but it won't go find pages on its own.

It won't loop or fabricate

• It won't retry the same failed call. If a call fails the same way, BotFather doesn't burn your turn re-sending it. It reports what failed and moves on.
• It never dresses up a failure as success. If a call errors, returns nothing, or comes back empty, it tells you what happened. It will not paraphrase a 404 or an error as "all connected and healthy."

Next

• What is BotFather?
• Using BotFather
• Team & security
• Audit log