​
Release Notes

​
2026-10-10 — Main bot setup and drag to make main

  • Every account now has a main bot. The first bot you create becomes it. Without one, the main bot tile (and Bot Mode, once per session) opens Set up your main bot: a short explanation of what the main bot does and what it never does without approval, then Set up A:// in one click, or pick one of your bots. See Your main bot.
  • On desktop, drag a bot in the Bots rail onto the main bot tile to make it your main bot, or onto the promoted row to promote it.

​
2026-10-10 — Bot Mode: main bot, bot screen, thread switcher

  • The Bots rail is lighter. Your main bot sits at the top as a large photo tile. Up to three promoted bots sit in a row under it, then Projects, then Bots, with Group chats pinned at the bottom above your account row. See Bots.
  • Each bot row shows the last line from its newest thread. The thread dropdown under each bot is gone; a bot’s threads live on its bot screen.
  • Make any bot your main bot, or promote it, from its ⋯ menu.
  • Clicking a bot opens its bot screen: a bigger header with its photo and how to reach it, then its main chat beside its threads. The main chat is always there and knows the status of the bot’s threads without taking in their context. Threads idle for 7 days fold into Stale. See Bots.
  • Bot Settings (formerly Config) starts with Phone and reach: the bot’s number, texting and voice calls, its phone, email and channels, and who it can contact on its own.
  • In a thread, click the thread title to switch threads: the main chat, the bot’s other threads, and the same project’s threads from other bots, with + New thread and + Incognito. See Switching threads.
  • The bots home shows your bots as a horizontal row (main bot first). Terminal CLI runs (Kimi, Codex, Claude Code) no longer appear there; they stay in Code mode.
  • Project pages add Needs you · N in the header and a row of the project’s bots to start one on a new thread.

​
2026-10-08 — Polished interactive cards

  • Cards in replies have a new design: inputs and results in labelled groups, sliders with a filled track, number fields with $ / % and − / + buttons, segmented choices, and up to two actions at the bottom. Numbers animate when you change an input. Light and dark, desktop and phone. See Interactive answers.
  • Cards now draw in Chat, Cowork, Code and bot threads instead of showing as a code block, and no longer show up under Outputs.
  • While a card is being written, one steady placeholder holds its place with the card’s title, then the finished card appears in one step. Numbers no longer flash in digit by digit.
  • Cards have a controls panel for the numbers you change and lead with the answer in large type.
  • Starting a new chat shows your message and Starting chat… right away, instead of an empty screen while the chat is set up.

​
2026-10-08 — Interactive answers turned on, with live data

  • Assistants now know they can answer with an interactive card (sliders, metrics, tables, charts, choices) in Chat, Cowork, Code, bot threads, the HUD and Design mode. Plain text stays the default.
  • Cards can show live data from your connected apps and refresh it. A card that changes something asks first with an Allow bar showing the exact tool and arguments; nothing runs until you approve.
  • What you set on a card is remembered when you come back to the chat (on that device).
  • Settings → Response style → Layout and visuals: choose Auto or Text only.
  • Bot threads and the HUD now render cards instead of showing their code. In Slack, Telegram, email and other channels a card is sent as readable text.
  • Design mode’s preview shows the reply’s card re-skinned with your DESIGN.md. UI Forge is now a working playground for cards.
  • Removed: the old [v:…] preview syntax (no model was ever told to write it, and the text after a stray [v: in a reply disappeared), BlueprintCanvas, and the render_walkthrough tool, which reported a render that never happened.

​
2026-10-08 — Attach any file or folder

  • Attach any file type in the composer: video, audio, ZIP, and files with any extension, including dotfiles. On Desktop and desktop browsers, attach whole folders from Add a folder or by dragging them in. See Attachments.
  • Files show the moment you pick them, with Reading… while they are read, so a slow PDF or folder is never silent. Videos show a frame and their length.
  • Video, audio and other files reach the agent as a link to your Allternit Cloud storage. Sent messages show file chips instead of the extracted text.
  • The composer’s grey outline is gone. The soft grey band only appears behind a reply strip or attachment cards.

​
2026-10-07 — Composer polish, replies, images and interactive answers

  • The chat text box, question cards, working pill and card grids have a new, quieter look across Desktop, ai.allternit.com and the m.allternit.com app. See Composer, replies and questions.
  • Reply to a whole reply, or to text you select in one. The quote travels with your message.
  • Agent questions use numbered choices: press 1–9 on Desktop. Skip question skips only that question. The agent now receives the text of your choice; before, it got an internal id like 0-Framer.
  • Images you attach now reach the model as images. Before, they showed in the text box but weren’t sent. Desktop shows attachments as cards with real details (pages, lines, rows and columns); phones show previews. See Attachments.
  • While a file is being written, a placeholder shaped like it holds its place.
  • Replies can include interactive answers: cards with sliders, metrics and tables that update on your device.
  • API: POST /api/agent-chat accepts attachments like the Desktop /api/v1/ai/chat bridge. See Agent Chat API.

​
2026-10-07 — Bots on your cloud computer

  • gizzi agents up <team> --on "Cloud computer" runs a team’s bots on your Allternit cloud computer, the same way as on a paired Mac or VPS. The cloud computer pairs itself; there is nothing to set up. See Factory agents.
  • Only the Factory engine’s peer port goes on your private mesh, never the cloud computer’s screen. The pairing is removed when the cloud computer is deleted. See Cloud computers as paired computers.

​
2026-10-06 — Memory Drive

  • Everything your agents remember is now kept in your Memory Drive: a private folder of one-line notes with the conversation each came from and the date, and a full history of changes. Chat, bots, the phone app and Gizzi share it. See Memory Drive.
  • Settings → Memory → Memory Drive shows the files, history and diffs, lets you edit, and creates read-only or write tokens so other agents (Claude Code, Codex) can clone it.
  • A nightly Dream merges duplicates, fixes contradictions a conversation proves wrong, adds lessons and removes long-unused memories, as one change with a report and an undo. It runs at night in your time zone.
  • Move memories you already had with Import existing memory (your Needs you inbox reminds you), or bring them from ChatGPT or Claude by pasting or uploading their memory list.
  • Delete forever removes chosen memories from the drive and its whole history.
  • Teams, projects, bots and swarms get their own drives, with a questions board for people and agents. Gizzi: gizzi memory.

​
2026-10-06 — Notifications from the event backbone

  • One push sink turns event backbone events into notifications: approvals, threads that need you, messages, ended calls, sign-in needed and usage alerts are on by default; finished runs and other informational events are off. Each type has its own switch. See Notifications and Notification preferences.
  • Relayed channel messages from a runtime that forwards its events now notify once, with the sender and text, through the sink instead of the direct push.
  • Cloud budget alerts now emit usage.threshold once per crossing, so push and MCP Events subscribers get them.
  • The allternit-bot CLI keys list now shows each key’s MCP Events subscriptions, and the owner can stop one. See allternit-bot CLI.

​
2026-10-02 — Thread and project pane parity

  • Bot threads now use one-row tops with avatar navigation and vendor provenance popovers. Ripped-page context dividers, plan cards, and wavy gap/day rules explain thread history. The pane switches Thread, Browser, and Computer; notifications and bot settings fold into ⋯ when docked. See Threads.
  • Projects and Bot Mode share one bot project list with pin/archive, server context files, per-device folders, coordinator instructions, and Threads / Library / Routines / Browser panes. Projects-tab workspaces include grouped threads, graphs, receipts, decision cards, wrap-up reports, and Library. See Projects.
  • Carried vendors and all seven channel providers have thread looks. Allternit remains the default composer; vendor composer skinning is opt-in through an in-memory flag. Packed threads omit the dot-grid backdrop. See Vendor packs.
  • Gemini and Copilot connection entries use best-effort ui_bridge. They are new and not yet verified against the live services. Sign in under Settings → Subscriptions and read the terms warning. See Subscriptions.
  • Web phone and PWA layouts keep avatar, provenance, project controls, and pane menus reachable. Panes open full screen with Back; view menus and actions stay above pane content.

​
September 30 documentation update

  • Bots and threads: Documented durable standing/task threads, server status, context generations, subagents, and removal of the standalone Bot Hub. See Bots and Threads.
  • Project launches: Added Al’s planning, dependency execution, follow-up routing, project work directories, and bot/team template setup. See Project coordination.
  • Subscriptions: Added the Sessions-computer sign-in flow, several logins per provider, preferred login selection, disclosure, and human-initiated sends. See Subscriptions.
  • Artifact modes and computers: Explained editor-pane sessions, bot-thread mode limits, deliverable requirements, and ACI observation/control. See Artifact modes and Computers.
  • MCP Apps: Recorded the merged host integrations and pending developer-docs package separately from existing MCP tools. Deployment and installation checks still apply.

​
2026.09

  • APIs: Documented the production split. Cloud API at https://api.allternit.com is the only public API. Allternit API (:8013, SQLite) is the private data plane. Agent sessions, Office, and beta research are Cloud API routes that relay to a paired or provisioned node (HTTP 428 if none is healthy).
  • BYOC: Three data-plane modes — local desktop, user-paired VPS, Allternit-provisioned instance. Control plane is Cloud API.
  • Provisioning: /api/v1/provisioned-instances lifecycle on the Cloud API; node traffic still uses the runtime relay.

​
2026.08

  • Docs: Migrated documentation site to Mintlify v4 with expanded API, Admin, SDK, and Guides coverage.
  • Gizzi Code: Added permission profiles, remote runner commands, memory search, and CI mode.
  • Platform: Added marketplace capabilities, Qwen-MM plugin adapter, and page-agent service promotion.
  • API: New endpoints for batches, deployments, work queue, memory stores, evals, outcome rubrics, and federation.
  • Enterprise: Added SCIM, audit transparency, compliance, spend limits, and external key management scaffolds.

​
2026.07

  • BYOC: General availability of bring-your-own-compute runtime and agent daemon.
  • Voice: Duplex voice session client and platform voice controls.
  • SDKs: TypeScript and Python SDK middleware hook system.

​
Earlier releases

See the GitHub releases page for full historical changelogs.