A bot can have several threads. Each thread tracks an objective, success criteria, checklist, status, dependencies, summary, and the session currently executing it. The rail and project view read the same server records, including work started by the coordinator rather than the current browser window.

​
Standing and task threads

Every bot has one always-on main chat (its standing conversation). It knows the status of the bot’s other threads but not their full context. Open a bot from the Bots rail to reach its main chat and threads on its bot screen, or create a new thread for a separate task. Incognito threads are private: they are left out of the bot’s thread list and the main chat’s view of its work. In a group conversation, a bot mention can start a task thread; the inline card opens that work and exposes its running state. Open threads with no activity for 7 days are marked Stale automatically and fold to the bottom of the list. A thread waiting on you is never marked stale.

​
Switching threads

In a thread, click the thread title (with the small arrow) to open the switcher. It lists, in order:
  1. The bot’s Main chat.
  2. The bot’s other threads, grouped Needs you, Working, Queued and Idle, then a folded Stale group.
  3. Same project · other bots, when the thread belongs to a project.
Type to filter by title. Use the arrow keys and Enter, or click; Esc closes. Picking a thread opens its session in place. The footer has + New thread, + Incognito and a link to all of the bot’s threads on its bot screen. On a phone the switcher opens as a bottom sheet.

​
Status and progress

Checklist progress is reported as completed steps out of total steps. Review means the result needs attention; it is not a claim that the task has been approved. Use Stop on an active turn to interrupt execution, including a turn started by the server. Stopping a turn and resolving a task are separate actions.

​
Bots handing work to other bots

A bot’s own chat (its main chat or one of its threads) can hand a task to another of your bots with the message_agent tool. This is how your main bot routes work to the bot that owns it.
  • Who exists. message_agent with target list returns your other bots with their title, tagline and description, so the bot can pick the owner. Targets resolve by name, @handle or id, case-insensitive; an unknown or ambiguous name returns the choices instead of guessing.
  • Where the work goes. The target gets a task thread (created by bot) linked under the caller’s thread (parentThreadId) and in the same project, so it shows in the target bot’s thread list and on the project page like any other thread. A follow-up from the same chat to the same bot continues that thread while it is open; a second hand-off while it is still working is refused with “still working”.
  • What comes back. The target runs the task at once. If it replies within the wait window (90 seconds by default), the reply is the tool’s result. Longer work returns a “started” handle with the thread id, and the result is posted into the caller’s chat when it lands. The thread moves to Review with the reply as its summary, or to Waiting on you with the reason if the turn fails.
  • Ownership. The calling bot comes from the chat’s session, never from the model’s input, and the target must belong to the same account. Group rooms, regular chats and subagents do not get the tool.
  • Terminal bots (made with gizzi agents bot, kept in ~/.gizzi/bots) keep the inbox model: the message lands in the target’s inbox and its reply arrives later as a background message.
In the chat’s process block the call reads Handed to Scout.

​
Context generations

A durable thread can span several model sessions, called generations. A handoff checkpoints the current work, opens a fresh session, and seeds it with the checkpoint. The transcript marks the boundary with a divider and summary. Earlier generations remain part of the work history. Usage reporting can request a handoff when the current context reaches 70 percent of its model window, including after switching to a smaller window. The thread id remains stable; currentSessionId can change. Integrations should keep the thread id as their work reference.

​
Subagents

Subagents delegate a portion of a thread’s work and appear in its subagent tree/feed. Inspect their activity and results alongside the parent thread. A subagent is distinct from a reusable bot and does not automatically become a project team member.

​
Runtime API

These authenticated routes belong to the private Allternit API data plane, normally on port 8013. Do not assume they are public Cloud API endpoints; see API overview. Continue with project coordination or artifact modes.

​
Thread top and reading the history

The thread top uses one row: the bot pill, the vendor provenance chip when connected, and thread controls. Tap the avatar to open the bot screen. Tap the bot name or progress to open the Thread pane. Tap the thread title to switch threads. Task threads also offer Resolve. The via Vendor ✓ chip identifies the connected vendor. The check indicates verified connection identity; it does not verify the answer. Open the chip to see the agent, connection mode, lane, guarantee level, connection health, and channel when present. A browser lane can be best effort even when the account is verified. A ripped-page divider marks a new context generation. It shows what was carried forward and the checkpoint when available. A plan card shows the task objective and checklist. The wavy rule marks work picked back up after a time gap; project conversations also use a wavy day separator. These markers describe history, not task completion.

​
Thread, Browser, and Computer pane

Open the thread pane from the pill or pane control, or open the computer from its control. The pane’s title menu switches between Thread, Browser, and Computer. Thread contains activity, subagents, artifacts, memory, and details. Browser and Computer show this thread’s browser and computer surfaces. On Desktop, the pane can dock, resize, and expand. While it is open, notifications and Edit bot fold into ⋯ beside Resolve; the pane supplies its own view menu and close control. On the phone, the avatar and provenance chip stay in the top row. Use the pill for Thread, or ⋯ → Computer for the computer. The pane opens full screen. Its slim view bar switches Thread / Browser / Computer; Back returns to chat. The same controls are used by the ai.allternit.com phone layout and the m.allternit.com PWA. The computer status row wraps to fit the screen.