Troubleshooting

Start with two checks: open the bot and read its real state and the full error, and make sure your computer is awake with Fluf running. Most problems end there.

A connection won't verify

Check you picked the right provider and account, then the provider's status page, the key's permissions, its balance and its limits. Re-enter or rotate the key only in Settings › AI connections. On Linux, unlock your desktop keyring.

Using Claude Code or Codex? Fluf runs your installed Claude Code / Codex, signed in with your own account. Run the CLI on its own and sign in through its normal flow first. Being signed in on the website doesn't sign in the CLI.

A model or toggle is missing

Refresh the connection and check the exact account and model. Effort and speed toggles appear only where your model and plan support them. A plan name, a logo or an old screenshot doesn't guarantee access.

A bot stopped

Open the bot. It's either waiting on you, paused, at a provider limit, or failed, and Fluf says which. Fix the cause and continue from the saved conversation. Before retrying anything that sends, publishes, buys or deletes, check the last step it actually finished.

A connection hit its limit

Fluf names the connection and the bot using the most. Switch that bot to another model or connection, add a key, or resume later. Its work is saved.

A routine didn't run

In Library › Routines, check it's on, then its next run, timezone, bot and connection. Read its run history. Routines run while your computer is awake with Fluf running; runs missed during downtime don't all replay.

Computer use won't start

On Mac or Windows, open Settings › Computer and check the setup shows ready, the app's rule isn't Never, and the OS permissions are still granted. A locked screen or login prompt needs you. On Linux (in release testing), computer use needs an X11 desktop session, or Wayland after you approve the screen-sharing prompt.

A Telegram contact won't reply

Check the contact belongs to the right bot, pairing finished and the token hasn't been revoked. In Fluf, check the bot's state and connection. Keep the computer awake with Fluf running. If a token leaked, rotate it in BotFather and paste the new one into the secure field.

A notification didn't show

Check Inbox first: the item is there even if the alert wasn't. Then Settings › Notifications, your OS notification permission, quiet hours and focus mode.

Install or update fails

Check you picked the right OS, CPU architecture and package, from the official download page. Finish or stop active work and keep your local data before retrying. Never switch off system security to force an install.

Still stuck? Tell us

Send your OS, Fluf version, what you did, what you expected and the exact error text. A screenshot helps; blur anything private. Never send API keys, Telegram tokens, passwords, MFA codes or full private conversations.

Next: FAQ · Connect your AI