AQBot
Connect the local-first desktop AI workbench AQBot to RuToken via one-click import or manual provider setup.
AQBot is a local-first, open-source (AGPL-3.0) desktop AI workbench. It combines multi-provider chat, ACP agents, knowledge bases, MCP tools and a local API gateway, keeping app data in ~/.aqbot/ and your files in ~/Documents/aqbot/. Source: GitHub, downloads: Releases, docs: Getting Started.
Prerequisites
- An API key: open the console, go to API Keys and create a dedicated key (for example, named
AQBot). - AQBot installed and opened at least once, so the system registers its
aqbot://link handler.
Configuration
Option A: one-click import
- On the API Keys page, open the actions menu of the key and choose Chat → AQBot (available when your administrator has enabled it).
- The browser launches AQBot. Check the provider name, API host, type
openaiand key prefix, then confirm. - AQBot opens Settings → Provider Management. It reuses a provider with the same API host and type, or creates a new one.
- Open the provider and click Sync Models.
The import does not validate the key or sync models by itself — step 4 is required.
Option B: manual setup
-
In AQBot, go to Settings → Provider Management → Add Provider.
-
Fill in:
Field Value Provider Name RuTokenProvider Type OpenAI(recommended)API Host https://rutoken.aiAPI Key sk-xxxx -
Click Sync Models to load the models available to your key.
Enter the site root as the API host — AQBot appends /v1 for the OpenAI type. If the host already ends with /v1, AQBot does not add another one. Add a trailing ! only if you need to disable this completion.
Optional: native protocols
RuToken also serves the Claude and Gemini native APIs. You can add extra providers with the same key:
| Use | Provider Type | API Host |
|---|---|---|
| Chat Completions (default) | OpenAI |
https://rutoken.ai |
Claude native /v1/messages |
Anthropic |
https://rutoken.ai |
| Gemini native | Gemini |
https://rutoken.ai |
Verify
Return to chat, select one of the synced models and send Hello, please reply with "Connection successful".. The request appears in the console under Usage Logs.
Troubleshooting
| Symptom | Fix |
|---|---|
| Clicking AQBot does not open the app | Install and launch the desktop app first; a web page or dev server does not register aqbot://. |
401 / invalid API key |
Edit the provider and paste the full key; check that it is enabled, not expired and has quota left. |
404 / not found |
Use https://rutoken.ai as the API host and let AQBot add /v1; remove any extra path. |
| Import works but chat fails | Click Sync Models and make sure the model ID matches the Model Square exactly. |
| macOS says the app is damaged | Follow the AQBot README to allow the app; you do not need to disable Gatekeeper. |
One-click links contain your API key. Generate them only on your own signed-in API Keys page and never share such URLs.