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.
Akeru Bot
Akeru Bot is a local-first app for named teammate bots. Web, desktop, and mobile clients connect to an environment that owns the bots, projects, chats, providers, and local data.
Identity
Akeru Bot: The product name. Avoid: T3 Code, akeru-bot, t3code-leo
Akeru home:
The directory that stores Akeru Bot settings, secrets, logs, and durable state. The default is ~/.akeru, and worktree development uses .akeru.
Avoid: T3 home, ~/.t3
Product language
Bot: A named teammate that has a profile, provider, tools, memory, workspaces, and routines. Avoid: Agent when the text refers to the named teammate that the user configures
Chat: The user-facing conversation with a bot. Use chat or conversation in interface copy and user documentation. Avoid: Thread in user-facing text
Thread: The internal durable record that stores one chat and its work history. Use this term only in source identifiers, contracts, architecture documentation, logs, and compatibility paths. Avoid: Thread as a user-facing label
Turn: One user request and the bot work that follows it inside a chat. Avoid: Message when the complete request-to-result cycle is intended
Project: An environment-local record rooted at a directory. Avoid: Repository when the project can exist without Git
Workspace: The files and execution context assigned to bot work. A workspace can be local or provided by a sandbox service. Avoid: Project when the execution context is intended
Environment: One running Akeru Bot server and the machine, filesystem, provider credentials, and state that it owns. Avoid: Server when the user is choosing or managing the complete environment
Provider: The bot runtime that Akeru Bot connects to, such as Codex, Claude, Grok, Kimi For Coding, or OpenCode. Avoid: Model when the runtime or account connection is intended
Routine: Saved bot work with a procedure and an optional schedule. Avoid: Job, automation, task when the durable configured routine is intended
Project rules
- Keep the MIT license and credit the T3 Code team and contributors for the original codebase.
- Use the
akeru-botdesktop Chromium profile. - Do not push, publish, or create a GitHub repository unless Leo asks.