Troubleshooting

Replies fail or take too long#

Check Settings → Providers for the selected provider, model and saved credentials. HTTP 429 means the provider has reached a rate or quota limit. Wait, check your account or choose another available model. Repeatedly retrying immediately can make rate limits worse.

For slow browser tasks, separate model waiting from browser actions. Compare the same task and model settings. A fast page action can still be followed by a slow provider round.

The browser is unavailable#

Check Plugins for the enabled backend and its connection/setup state. Install the managed Chromium from the Playwright card if required, or follow the Chrome connection instructions. A site’s 403 refusal or sign-in challenge is not solved by repeating screenshots.

Take control for MFA or CAPTCHA, then hand the browser back. Stop cancels a stuck run; inspect the last observed state before retrying an action that may already have completed.

Dragging a mascot does not capture the page#

Confirm the Chrome/Edge capture helper is loaded and paired in that browser profile. Reopen Browser helper in Ankita for its folder and pairing controls. Test on an ordinary HTTP/HTTPS document.

Browser-internal pages, extension stores and inaccessible viewers or frames cannot be captured. Capture and browser automation use different connections.

Updating a portable copy#

Download the newer portable executable from Releases. Portable builds do not use the installed app’s in-app update flow. Use the release notes to check what changed.

Report a useful issue#

Include the Ankita version, operating system, provider/model names, reproduction steps and the exact error. Attach a screenshot or scrubbed trace if helpful. Never include API keys, passwords or private document contents. The Support page links to the project’s issue tracker.