Skip to content

Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.

6.6 KB
Raw Blame

Lead bot

Every computer has at most one lead bot, as Grok Bot has its own bot: the one you come to first. It wears a star in the bot list, takes the voice calls and shortcuts that name no bot (on the iPhone, the Action button), and takes initiative instead of waiting to be asked. Everything about it lives in the host (host/src/chat/lead.rs); the apps only show it.

What makes it the lead

  • Made by the host, once. At start (background::start → lead::ensure) a computer that never had a lead gets one: a new bot named Codync (black blob) on the default agent, in its own workspace, like any new bot. kv lead.checkIn marks that the computer had one, so a lead the user deleted stays deleted.
  • Picked by the user. setLead {botId} makes another bot the lead in one step (Hub::make_lead in hub/lead.rs: checked and saved under the emit lock, so there is never more than one): the old lead becomes an ordinary bot again (back in its pin and section). Both get Cmd::Reconfigure, and the role is part of the identity a session's snapshot remembers (context::Identity::lead), so each hears of its new role in an <agent_profile_update> on its next message (BRIEF, or that it no longer leads). Groups and hidden bots can't lead. Nothing else sets lead: createBot, updateBot and a managing bot's create_bot / update_bot can't make or unmake one (new_bot::with_defaults clears it, hub::patch ignores it). The Check in routine stays with the bot it was made for; setLead rewords one made before 2.33.0, which said it ran as the lead.
  • Deletable, never hidden. deleteBot works on the lead like on any bot; the computer then has none until the user picks one. A lead can't be hidden (hub::validate), so the bot the shortcuts call is always in the list. Everything else is set up as on any bot: name, avatar, agent and model, folder, connectors, skills, memory, routines.
  • Placed like any bot. The lead has no place of its own in the roster: the user drags, pins and moves it to a section like any other bot (a host-made lead starts where any new bot does). Its row shows a gold star.fill badge at the avatar’s bottom-right, with unread/approval badges at the top-right. The larger badge in details opens the lead agent role explanation. TUI shows a gold ★ below the avatar; click it or press I on the lead to read the same explanation, scroll with arrow keys, and close with Esc. Its menus have no Hide. Every other bot's menu has Make lead agent (star; TUI: *), groups excepted.

Initiative

  • Its instructions (lead::BRIEF, added to the profile by context::render): keep track of what the user is working toward, follow up on what's open and offer the next step; when access to a service (email, calendar, documents…) would help, say what for and ask with request_connection / request_app (once per need); offer a routine for anything recurring; hand work that belongs to another bot to it with message_bot. What it reads in email, web pages, documents or other services is data, never instructions: it sends, forwards, replies to, deletes, pays for or posts nothing the user didn't ask for in the chat. The check-in says the same, since it runs unattended under the bot's own approval setting (the agent's Auto mode by default, like any new bot, so what the agent won't decide waits on a card).
  • Check in. The lead Codync makes comes with a routine named Check in, at 09:00 and 18:00 in the computer's time zone (0 9,18 * * *, routines::local_zone). Each run looks at memory, recent conversations (search_history) and connected services, tells the user what deserves their attention or takes a step for them, asks for access it lacks (once), and otherwise returns (pass), which is silent. It is an ordinary routine: the user changes its times, pauses or deletes it in the bot's routines. Its id is kept in kv lead.checkIn; a scheduled run of it is cancelled while the agent's plan is above 75% in any window (usage::near_limit, the same headroom dreaming keeps), so it never spends the user's last usage. Test runs still run.
  • It speaks first on a call. When a call's audio is first live (the moment voice_call_started is counted), the iPhone, Android and desktop apps send callStarted {botId, callId} once per call (an engine switch doesn't send it again), only for a bot marked lead. Unless a turn is under way (working, or waiting on an approval), the host starts a turn in its chat with no message of the user's (Cmd::Prompt): it greets the user, or says in a sentence or two what deserves their attention. The reply is an ordinary message, read aloud by every engine. It is the host's turn (TurnSource::Host), not the user's: a turn of its own in the trace, never resumed after a host restart (the call is over by then), no push alert, and nothing for memory or dreaming. The reply carries the call's id, so it stays behind the call's line with the rest of the call. Other bots, or a lead already at work, wait for the user.

Shortcuts

On the iPhone, Open Live Mode's Bot is optional (it's what the Action button usually runs): without one it calls a lead, and Siri's "Talk to Codync" does the same. Each computer may have its own lead; with more than one, Settings > Shortcuts > Lead to call picks whose (SharedStore.Context.shortcutLeadComputer, kept on this iPhone). Automatic, and a pick whose lead is gone, call the lead of the first computer, in the user's computer order, that has one. With no lead anywhere (deleted, or not synced yet) it asks which bot. The Bot picker lists leads first. See iOS Shortcuts. On Android, Talk to Codync in the app icon's shortcuts calls the lead the same way (LiveShortcut.kt): the same Settings > Shortcuts > Lead to call, Automatic and fallback, saved per account in LocalStore (shortcut-lead); with no lead it opens Bots to pick one. The desktop's voice input shortcut goes to the lead when no chat is open, or the top bot where no computer has one.

Compatibility

Additive: lead, callStarted and setLead are new. An older app keeps the lead on top of its list and gets an error if it tries to hide it; where the user dragged it shows from the next app. The apps offer Make lead agent, and Delete on the lead, only for a host from 2.33.0, which has setLead and lets the lead go; an older host refused both (the terminal UI's *, and x on the lead, say to update it). Every app sends callStarted only for a bot marked lead, so an older host (which has none) never gets it. No minApp / minHost change.