Skip to content

Open-source Grok Bot alternative for named AI teammates. Local-first desktop, web, and mobile clients with per-bot tools, instructions, and memory. Independent fork of T3 Code.

6.0 KB
Raw Blame

Provider connections

Akeru Bot connects to provider subscriptions and API keys from Settings → Providers. Credentials stay in the environment that owns the connection.

ChatGPT, Claude, Grok, Kimi For Coding, and OpenCode Go run through Akeru's built-in runtime. You do not need their command-line tools installed or signed in to create a bot, chat, or generate chat titles and branch names with ChatGPT, Claude, or Grok. After connecting an account in Akeru, choose its models in onboarding or the bot's settings. If the account is disconnected, reconnect it in Settings → Providers.

Model lists update on their own. The environment server checks models.dev for new provider models about once an hour, and open clients pick them up within a few minutes, with no reload or app update. Older models move to the picker's legacy section when a newer one in the same line ships.

A provider can have more than one account. Backup accounts take over when one hits a usage limit; see Backup accounts. To keep a second subscription apart instead, such as a work and a personal one that different bots use, choose Add separate account on the provider's page. Give it a name, then sign in from its card. A separate account configured with its own credentials uses those credentials rather than the shared connection. A custom configuration directory alone does not connect an account to Akeru's runtime.

Custom API endpoints

Settings > Providers > Custom API connects Akeru Bot to any OpenAI-compatible HTTP endpoint: a hosted service, a gateway, or a server you run yourself. There is no account to connect and no sign-in flow.

Use Add account on the Custom API page and pick what you are connecting to. OpenRouter, Groq, Together AI, DeepSeek, Mistral, Fireworks, LM Studio, Ollama, and vLLM fill in their base URL and a name for you. Choose Other to type the URL of anything else. Local servers such as LM Studio and Ollama resolve on the machine running the environment, not on the device you are using.

Paste the service's key into API key. Hosted services need one; local servers usually do not, and a base URL alone is enough for them. The key is stored outside the settings file, never sent back to a client, and sent to the configured endpoint as a bearer token. Once saved, the field shows that a key is stored. Type a new key to replace it, or use Remove key. A key belongs to its service: changing the base URL to a different host, or from HTTPS to HTTP, removes the stored key, so paste the new service's key afterwards. If the endpoint refuses to list models with that key, the instance shows Needs attention with the reason until a later check succeeds. You can still chat with it, since some keys may use models without listing them.

The model list comes from the endpoint's /models response. Models you add by hand are kept alongside it, and a model disappears from the picker once the endpoint stops listing it. If Akeru cannot read the endpoint, the last successful list stays and the provider row explains what went wrong.

Add one account per endpoint to keep several side by side, such as a local server and a hosted gateway.

The environment sends requests to the URL you configure. Point it only at an endpoint you trust, and prefer HTTPS for anything outside your machine.

Backup accounts

Once you are signed in to a provider, its page lists your accounts under Accounts. Choose Add account there, then sign in or use an API key. Each new account goes to the bottom of the list.

Each account is named by its plan, such as ChatGPT Pro or Claude Max 20x, so the list never shows your email address. API keys show as API key. Grok and Kimi For Coding don't report a plan, so their accounts show as Grok account and Kimi For Coding account.

The list is in the order bots use it. The first account is the Main account and the rest are Backup 1, Backup 2, and so on. Bots use the main account, marked In use. When it reaches a usage limit, the account shows Usage limit reached, back at the time it resets, and bots move to the next account. The request that hit the limit still fails, and the bot's next request uses the backup. Once the limit resets, bots go back to the main account. A backup waiting its turn shows Ready.

If an account stops working, it says why and offers the fix next to it. Signed out and Login expired come with Sign in again, and Key rejected comes with Replace key. Can't reach the provider comes with Try again.

Use the arrows to change the order. The actions menu on each account has Sign in again (or Replace key) and Remove. On mobile, use Move up, Move down, and Disconnect.

Backup accounts serve bots on the provider's main connection. A separate account added with Add separate account keeps its own sign-in and does not take part in the backup order.

Subscription login health

After a login or API key save completes, the environment server sends one request that costs nothing, to confirm the account can reach its models or usage endpoint. The check runs on the server, so closing the app or losing the connection right after login does not stop it. While it runs, the provider row shows Checking health…. It then changes to Connected when the request succeeds or Failed when it does not. A failed check does not undo a successful login. Repair the provider account, then use Reconnect or Check OAuth.

The check covers ChatGPT/Codex, Claude, Grok, and Kimi For Coding logins, and OpenCode Go API keys. OpenCode Go has no device login.

Device codes

For providers that use a device code, Akeru Bot shows the code beside the sign-in link, in Settings, in desktop onboarding, and on mobile. Choose Copy sign-in code (or Copy code on mobile) to copy it. Code copied confirms a successful copy. If the browser, desktop shell, or phone denies clipboard access, Akeru Bot says so. Select the code, copy it manually, and continue on the provider's sign-in page.