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.

15.7 KB
Raw Blame

Configure bots

Open a bot, then use the panel beside the conversation to edit it.

Initial setup

Setup connects a subscription, then asks one question: what you want help with. Answer it in your own words, in a sentence or two. Select one of the examples to fill in an answer you can rewrite.

From that answer your bot proposes where it will start, as a short numbered plan, along with the one detail it will come back to you for later. Select Edit to reword your answer and get a new plan, or Looks right to move on to naming your bot.

The last step drafts your first message from that plan. Edit it if you like, then send it. Once your bot has started on it, the chat opens with your message already in it, and setup fades away. If the bot is archived before the chat opens, Akeru clears the pending opening and tells you to create or select another bot.

Setup does not ask where the work should go, how often it should run, or which actions it may take on its own. Your bot raises those when it reaches the point of needing them.

Skip initial setup

Select Skip setup on any setup step, then confirm Skip setup in the dialog. Select Cancel to stay in setup. Skipping keeps any connected subscriptions and bots you already created. Setup will not open again after a restart.

You can connect a subscription in Settings and use Create to add a bot later. When the roster is empty, the main view shows Create bot.

Profile

You can change the bot's avatar, name, label, description, model, voice access, and enabled tools. Select Save to apply the changes. The model lives in the bot's settings under Model & usage, not in the chat. From a chat, use Change model in the command palette or its shortcut to jump straight there. The model list also shows providers that cannot run right now, such as one that is signed out or turned off. Their models are dimmed and say why.

Reasoning controls how much thinking the bot spends before answering. Change it under Reasoning in the bot's settings on web or desktop. On mobile, open Model and reasoning settings in the chat. The choices depend on the selected model: some offer levels, some offer a thinking switch, and models with fixed reasoning have no control.

The choice is saved with the bot and appears on other clients connected to the same environment. Select Provider default to clear a chosen level and use the provider runtime's default. Changing models on the same provider keeps choices the new model supports; changing provider starts with its defaults. Group chat controls do not change a member bot's saved reasoning.

A bot keeps its model when that model stops working. Akeru never switches it for you. Instead, the chat and the bot's settings mark the model unavailable, and Send stays off until you fix the cause or pick another model. A line below the composer names the provider, says what went wrong, and gives one next step. Set up a provider opens Settings > Providers.

Cause Next step
No provider is ready for the bot or group Set one up in Settings > Providers
Provider is not set up, turned off, or not installed Open Settings > Providers
Account is not connected, or its sign-in expired Connect or reconnect it in Settings > Providers
Provider no longer offers the model Pick another model for the bot
Your provider plan hit its usage or rate limit Wait for the limit to reset
Your provider account hit its quota or spending cap Raise it with the provider, or switch providers

When a provider reports that it rerouted a message to a different model while the chat is running, the work log notes it as Model rerouted from <requested> to <effective>. Providers that run through Akeru's session controller do not report the effective model yet, so a reroute that stays silent never appears.

When you connect or turn on a provider, its models become available right away. You do not need to restart Akeru. A brief provider error does not turn Send off, so you can try again. The same check covers new-bot setup and the voice call button. On mobile, the composer shows the same note and keeps Send off.

In a group chat, you can still message a member with a configured provider even when the boss cannot reply. Mention that member in your message to direct the turn to them. You can send a follow-up while an earlier group message is still being accepted. Both messages stay in the same chat. Archived members cannot receive new group messages.

Shaped avatars are a flat colored body with a face. The eyes are cut out of the body, so they take the color of whatever sits behind the avatar. Very light and very dark custom colors draw their eyes on instead. Bots saved with an older preset color show the matching color from the current palette.

Avatars rest on a still frame. A working bot sways, glances down at its work, and now and then turns its face around its body. Point at a bot and its eyes widen and follow the pointer. Now and then one resting bot on screen blinks or glances around. With reduced motion turned on, avatars stay still.

A settled reply shows its engine, step tokens, and estimated USD cost when the provider reports enough usage data.

Akeru stores bot profiles on the connected environment. Every client connected to that environment sees the same profile.

Workspaces and browsers

Separate is the default. Each bot gets its own workspace identity and browser profile. Shared lets bots share files and browser cookies.

When a bot shares its browser, the panel shows a small capture of its screen. Select Open to expand it, and select the collapse button or press Esc to shrink it again.

Bots can use Local, E2B, Daytona, Vercel Sandbox, or Upstash Box. Connect remote services under Settings > Sandbox. A bot-specific sandbox overrides the environment default. If a managed browser stops unexpectedly, Akeru records the failure in the bot inbox so you can retry the browser task after it is available again. Each affected workspace keeps its own notice until its browser works again.

Local bots use Auto review by default. Safe actions continue without a prompt. Actions that send, pay, delete, change production, use secrets, or have unclear intent still ask. Select Settings > General > Local execution to ask before each local change or grant full access. Bots that run in a cloud sandbox do not show the local computer prompt.

Run a routine

Open Routines in the bot panel. Add a routine, procedure, schedule, timezone, required skills, and connectors. Select Test to test the routine, then approve the procedure before you enable its schedule.

A routine reports to the bot's chat, so a new bot needs one message before you can add a routine from the panel. You can also ask the bot in chat to set one up.

Each routine card shows its schedule, status, and latest result. Select a card to see when it runs, its latest run, its instructions, and its workspace. You can run, pause, resume, edit, or delete the routine there, then select the back button to return to the list. A procedure change needs approval again. A draft routine shows Draft until you approve its procedure.

The bot's chat notes when a routine is created, starts a run, and finishes, fails, or is canceled. Deleting a routine removes it from the Routines panel while keeping those earlier notes in the chat. The older notes remain readable without opening the Routines panel. The chat loads recent routine notes first. Select Load older routine notes above the conversation to bring earlier runs into view.

A routine can hand its work to another bot. In the routine form, pick that bot under Done by. Bots whose provider cannot take handed-off work appear in the list but can't be picked. Each run then sends the instructions to the other bot, and a work card in the routine's chat shows the work as it runs. The run finishes, fails, or is canceled along with that work, and canceling the run cancels the work. Pausing the routine stops future runs but lets work that already started finish. The routine detail on web and desktop and the routine card on mobile show Done by with the other bot's name. If that bot is archived or cannot take work from other bots, the run is blocked and says why.

On mobile, open a bot's chat, open chat settings, and select Routines. Each routine shows its schedule, status, next and last run, and recent runs. You can approve its procedure, test it, run it, pause, resume, or turn it back on, and delete it. Creating and editing routines needs the desktop or web app, or you can ask the bot in chat. When a bot asks to create a routine, the approval card shows the routine's name, schedule, and instructions before you allow it. For a routine proposed through the built-in create-routine tool, an unanswered review closes after an hour. No routine is created, and the bot learns that the review expired.

If you ask a bot to create a routine in chat, review its proposed name, schedule, timezone, and instructions before selecting Create routine. If those details are missing, the review card says so instead of guessing a name or schedule.

If a required connector, provider, bot, or workspace is unavailable, Akeru pauses the routine and adds one item to the bot inbox, which you can open from Settings > Advanced > Bot inbox. The routine card says it was paused and points you to the bot inbox. Fix the dependency, then resume the routine. Restoring an archived bot does not resume its routines.

Every bot inbox item offers a way to clear it on desktop, web, and mobile. A disconnected provider or connector links to provider settings. A plugin access problem links to Plugins; on mobile the item tells you to fix it on the desktop or web app. Other items have Resolve. On mobile, provider and plugin items have Resolve too, so you can clear them once the problem is fixed.

Tools

Open Tools in the bot editor to enable or disable installed plugins and MCP servers. New tools start enabled for every bot. A workspace-disabled tool stays unavailable to every bot.

Changing the provider starts a fresh provider session with the same enabled tool set.

Bots on Akeru's runtime can read a public web page when you give them its address. They refuse local and private network addresses and read at most 2 MB of a page, noting when a page was cut short. Web search isn't available yet, so the bot says so and asks for a link instead.

A bot can hand part of a request to a temporary helper and use its answer. Up to three helpers can work at once for one request. Helpers can't start their own helpers, message you, or ask you for approval or help. A helper skips any step that needs your approval and reports it to the bot instead. A helper that has not finished in 10 minutes fails as a timeout. Helpers stop when the bot finishes or you stop the request. Their work doesn't appear as separate chats, even when the bot works in a group chat. Standard OpenCode bots don't use helpers.

Organize the roster

The sidebar shows pinned bots and groups as launcher cards at the top, followed by the rest as detailed rows under Bots. Drag a bot or group to reorder it, pin it, or unpin it. Dragging into Pinned pins it at that spot, and dragging a pinned item back into Bots unpins it.

To archive a bot, open its menu and select Archive bot. Archived bots leave the roster and stop taking messages, but their chats are kept. A message sent from another device that still shows the bot is refused with a note that the bot is archived. Archived bots are listed in Settings > Archived, where Restore brings one back and the delete button removes it right away. Akeru deletes an archived bot automatically 7 days after it was archived. Its chats stay in your history.

Pins only change the roster layout. They do not change group membership or settle chats.

While you drag, the lifted row stays in the roster and moves vertically between available positions. The destination label stays readable and takes the accent color. These transitions follow your reduced-motion preference, and a drop does not replay a second animation.

Pinning, unpinning, and moving an item keeps the sidebar at your current scroll position instead of following the item to its new place in the roster.

On this device the layout is stored in the browser for the connected environment. Refresh keeps it. Other devices keep their own layout until the environment can store roster order.

Conversation panel

Use the panel button to collapse or reopen the bot editor. The default shortcut is Mod+Alt+B. You can change Toggle right panel in Settings > Keyboard. Narrow screens open the editor as a sheet.

Bot replies support headings, links, tables, task lists, code blocks, math, and Mermaid diagrams. While a bot works, a small pixel meter sits under the latest message with the bot's current step and the elapsed time. The meter sweeps once when the bot starts or moves to a new step, then holds still. With reduced motion turned on, it skips the sweep. The timer counts whole seconds either way. During longer bot work, the bot posts short status notes after meaningful progress.

When a bot hands work to another bot or group, the chat shows a card for each handoff. Cards for work that is still running always stay. For finished, failed, or canceled work, the chat keeps the 20 most recent cards, and a long result shows its first 2,000 characters. Open the delegated chat to read the full result.

When a request fails, the chat shows a short card that says what went wrong and what to do next. A provider that is turned off or signed out gets a Settings > Providers link. A provider account limit gets a Bot settings button so you can switch the bot to another provider. When the cause is unknown, select Send feedback to report it with its details. Expand Technical details to see the underlying error, or select Resume when an interrupted request can continue. If your message was saved but the bot never started, the chat says so under your message instead of leaving the reply empty. Group chats do the same and name the bot that was asked to reply. On mobile, the resume card shows the same summary.

Voice calls

  1. Open Settings > Providers > Voice.
  2. Enable voice and choose the connected ChatGPT subscription and voice.
  3. Turn on Voice calls for the bot.
  4. Select the phone button in the bot's chat header.

Akeru uses the microphone and speaker on the current computer. Only one call can run at a time. The call bar stays visible when you open another bot. Select it to return to the call, or select hang up to end the call.

Image generation

Open the bot's settings and choose a provider under Workspace > Image generation, or keep Use global default. This does not change the bot's chat model. See Image generation.

Delete a bot

Open the bot's settings page and select Delete under Danger, then confirm. On mobile, open the chat's settings and select Delete bot under Danger. Deleting removes the bot from the roster. Its chats stay in your history and move to Settings > Archived.

Deleting stops anything the bot is doing. Running replies stop, work it handed to other bots or received from them is canceled, and a voice call with the bot ends. In a group chat the bot was answering, the boss picks up the next message.

A bot that leads a group as boss cannot be deleted. Set a new boss for the group first. A bot also cannot be deleted when its removal would leave a group with fewer than two active bots.