Skip to content

Rakazo Release Notes

Open-source Grok Bot alternative for persistent AI teammates that do real work, with your own keys, model and machine.

Downloads come from github.com/elie222/rakazo · OpenNavo hosts no installers
  1. 0.13.0

    Latest

    OpenNavo editorial

    Rakazo 0.13.0 lets people running persistent AI teammates send meeting bots into calls and edit Gmail and Slack drafts before they are sent.

    Added
    Meeting bots join calls and return transcripts.Edit Gmail and Slack drafts before sending.Invite outside guests to a Space by email.
    Security
    Approvals cover outside-influenced work.
    Fixed
    Mac recovers a closed renderer before migrating.

    Rakazo 0.13.0, released 19 November 2026, lets people running persistent AI teammates send meeting bots into supported calls and edit plain-text Gmail and Slack drafts before sending.

    Source: https://github.com/elie222/rakazo/blob/main/CHANGELOG.md

    • Meeting bots can join supported calls, return speaker-labeled transcripts, and be scheduled from Google Calendar.
    • Plain-text Gmail and Slack drafts can be edited in the approval card before they are sent.
    • Outside guests can be invited to a specific Space by email.
    • Approval settings now cover routines, connected chat apps, and work influenced by outside content. Unattended approvals expire after 30 minutes.
    • On Mac, a closed renderer can recover, and the app waits for the local database before migrating.
  2. 0.12.0

    GitHub Release

    Security

    • Cloud-agent tools enforce the bot's current integration assignments and allowed tools before using a connected account.
    • Inbound email needs signed recipients before it can be treated as the owner's instructions; an SPF pass reported by a relay is no longer enough. Email routines can still accept signed mail as outside data (inbound email).
    • Saving memory after reading outside content follows the run's approval mode and Always allow list, including after a run resumes (approvals).
    • Spoken answers containing both yes and no cannot approve an action. A texted YES or NO applies only to a group invite or agent connection request delivered before the reply.
    • Ambiguous checkout totals require manual payment, including when an approved action is checked again. Amounts such as $.99 are read as cents, and payment-method controls are excluded from purchase approval.
    • Model connection errors and logs hide more credential formats, including quoted and encoded values, custom headers, URL passwords, cookies and nested JSON. Card redaction also covers grouped American Express and Diners Club numbers.
    • Team-chat sender and channel names cannot escape their prompt labels. Malformed stored approval, plugin and billing configuration is rejected, and unexpected internal errors are no longer shown as client error details.
    • Removing connections and replaced secrets retries external cleanup after temporary failures. Desktop tool servers keep sign-in cookies separate from each other and the app, and disconnecting clears that server's browser.
    • Native clipboard writes require HTTPS or a loopback origin. App sign-in links reject malformed addresses and non-web schemes before reaching native handlers.
    • Private memory endpoints, including loopback addresses, require operator consent at the adapter boundary as well as the API.
    • Billing database triggers resist temporary-object shadowing, and organization deletion keeps Spaces inaccessible when a replacement deletion attempt fails.
    • Sign-up domain restrictions reject malformed addresses containing more than one @. The computer supervisor requires authentication on unknown routes as well as registered ones.
    • Crafted text no longer causes excessive parsing work in chat Markdown, voice reading, page validation, imported agent settings, provider errors and model replies. Cloud-agent schemas and expanded OpenAPI server addresses also have bounded processing.
    • Error reporting refuses plaintext HTTP collectors instead of sending diagnostic context without encryption.
    • Updated vulnerable build and release dependencies and container tooling. Some container advisories still lack upstream fixes; these updates do not resolve every reported vulnerability.
    • Source-checkout integration and browser tests always use the local encrypted secret store, preventing test credentials from being written to a configured external store.

    Added

    • Organization owners and admins can invite people, change member roles and remove members from Settings > Organization > Members. Each new member gets a private Space; joining does not reveal anyone else's Spaces. Paid organization seats follow membership, and removing a member keeps their work in the organization.
    • Optional conversation memory can learn from direct and group chats, recall facts and answer questions from a bot's own memory. Memory is isolated by default; choosing Shared pools learned conversations, including direct chats, within the Space. Connected memory providers can be edited without disconnecting (memory).
    • Vault items can limit which bots use them, ask before each use, hold additional login sites and authenticator keys, and show usage history. Import saved logins from CSV (reusable credentials).
    • Each connected model has its own context and output limits, image support and thinking settings, with a searchable model list and individual settings pages. Connections can also supply project and region routing where required (models).
    • Connect your own T3 Code environment and hand it coding work through the cloud-agent card, including follow-ups and cancellation (integrations).
    • Import Agent Skills catalogs or individual skill folders from GitHub, including supported referenced text resources; imported scripts are not executed (skills). Agent imports also accept a Grok Bot's self-export (import an agent).
    • Custom MCP servers offer browser OAuth sign-in when being added, and each server gets its own sign-in browser session.
    • Optional Google and Apple account sign-in, with passkeys available alongside the other methods and the last-used method marked (account sign-in).
    • Large composer pastes can be attached as a file or kept inline. Cmd/Ctrl+L on desktop, or Cmd/Ctrl+Shift+L in a browser, quotes selected transcript text. Slash commands work anywhere in a message with Enter choosing the highlighted command.
    • Settings > Labs enables the ticket board and its bot tools for an account.
    • Usage can be broken down by bot and model over a local-calendar date range.
    • Self-hosted speech and transcription can use separate servers and keys (voice and calls).
    • Object storage supports Azure Blob Storage through the existing storage connection settings (storage).
    • Docker computers can optionally expose host GPUs to bot programs. Railway computer browsers can optionally use an upstream proxy; shell programs still connect directly (Docker computers, computer providers).
    • Mobile has a Computers settings screen for paired computers and revocation, a full-screen computer trackpad with zoom and scroll controls, and section renaming by long-pressing a heading.
    • Forks can publish signed macOS-only desktop releases with updates from their own repository (fork distribution).

    Changed

    • Bot settings share one panel with advanced controls folded away. Computer maintenance lives in bot settings, and the computer screen uses one control model for viewing, taking control and returning control.
    • Switch and create organizations from one menu. Integration pages list the app's own actions, and account Vault settings point to the Space's vault when it keeps separate items.
    • One-to-one messaging apps show a bot's pending question or computer takeover request as text, with a link back to the app. Group conversations keep these requests private.
    • Unanswered bot questions stay open until someone answers, except when the run holds a single-use login or code that must expire.
    • Bot email sending uses a separate SMTP connection and a per-account recipient allowance; by default bots can send only to their verified owner. Mailbox-rule forwards and signed Microsoft 365 mail can start email routines as outside data (bot email).
    • Activity, routines, chat rosters and computer updates refresh through live change signals instead of polling.
    • Runs recover from brief database outages, and deploys let in-flight turns finish or hand work back between steps instead of cutting them off.
    • Bots retain earlier tool calls, results and the latest kept screenshot for later turns, and stop unproductive loops when one tool keeps returning the same result.
    • Delegated bots keep their own instructions and capabilities and run independently while the parent remains available, returning results and attachments to the originating chat.
    • Connector audit entries identify the linked account used for an action (audit log).
    • Mobile bot deletion warns about groups that will also be removed. Android voice calls finish recognizing speech sooner and avoid transcribing the bot's playback; speaking over a reply no longer interrupts it.

    Fixed

    • Desktop Copy buttons work reliably and text fields have a native right-click menu. Chat search reveals matches inside horizontally scrolling code.
    • Desktop cancellation avoids putting a stopped local stack to sleep, local stack stop remains available after server switches, and offline update checks report cached results accurately.
    • Renewed sessions send the refreshed cookie, keeping people signed in. Email sign-in works with browser Back, and model subscription sign-in works across multiple API instances.
    • Model calls retry empty, thinking-only, interrupted and unfinished replies, including failures during tool calls. Tool results retain unique call identities, and incompatible encrypted reasoning can be retried without it.
    • Tool-server connections recover when credentials rotate, keep refreshed sign-ins after an uncertain save, allow longer tool calls and retain healthy sessions after tool errors.
    • Tool-server connections also retry when credentials are replaced before connecting; editing a server mid-run makes it unavailable for that turn instead of failing the run with an internal error. Servers needing sign-in report Reconnect even when their suggested sign-in address is unusable; settings still validates the address before opening it.
    • Speech playback retries with a supported voice when a server rejects the chosen one. Delayed chat-app connection codes cannot link the wrong bot after switching bots.
    • OpenAPI tools preserve integer types, numeric bounds, minimum string lengths, nested parameter definitions, server-variable defaults and form query encoding. GraphQL headers are merged without case-related duplicates.
    • Long messaging-app replies preserve formatting and link destinations when split. Group mentions accept @all and @所有人, rich-text mentions retain names, and inserted bot mentions preserve code source.
    • Linked chats open in the correct Space and organization without an older read cancelling navigation. Repeated live events cannot make a finished chat appear active again, and Open work drafts survive the last saved item being removed.
    • Old uploads stop being listed and copied to the computer after several text-only turns; files from older history remain available on demand.
    • Failed computer starts clean up machines they leave behind, retry failed deletion and preserve recovery instructions. Remote computer deletion cleans saved bot files, and taking or releasing control avoids a duplicate screen read.
    • Runs waiting for their bot's computer start when it becomes free, and finished runs stop leaving computers shown as busy. Backup jobs run at the intended instant regardless of the database timezone, and setup failures retry promptly.
    • Routine next-run times stay correct across daylight-saving changes. Archived bots keep finished runs, and duplicate exact bot names are rejected.
    • Pages handle nested table text, numeric sorting, date-only calendar values, wide Japanese and Chinese diagram labels, right-to-left galleries and table hints, and links with paired punctuation. Animated PNG attachments retain animation, fetched text honors its charset, and failed audio previews can be retried.
    • Mobile keeps successful settings saves when the following refresh fails, asks before deleting unsent messages after sign-out, and keeps live notifications on the selected Space. Android chat scrolling retains the keyboard, landscape keyboards no longer cover the computer screen, and call audio resources are released.
    • Payment history uses the currency's decimal precision, and declined credit upgrades make clear that the card was not charged.
    • Credits from a disputed purchase are withheld during the dispute, removed if it is lost and restored if it is won.
    • Backups work with multiple API containers, use the container's database settings and fail when the data directory is missing.
    • Computers explain when an update cannot save oversized files and keep running. Interrupted workspace downloads use the normal provider-recovery path instead of failing as unexpected server errors.
    • Database sessions use UTC, fixing incorrect session expiry, stale-work detection and chat counts on servers whose default timezone differs.

    Self-host upgrade notes

    • Finish upgrading API and worker processes before relying on per-model settings; an older process refreshing a connection can discard them. Update the server before this desktop client when using single-use computer-screen sign-in links.
    • Set BOT_EMAIL_SMTP_URL on API and worker to keep bot sending enabled; it no longer falls back to account email settings. Drain previous-release workers before enabling sending under the new recipient policy. Check DKIM signing if owner email stops starting chats (sending, inbound verification).
    • Vault items can move under rotatable content-encryption keys. Stop previous-release API and workers before running content-encryption migrate; earlier releases cannot read migrated vault items. Follow the documented decrypt procedure before rolling back. Vault access restrictions require the restricted runtime database role (content encryption, database roles).
    • Reimport existing OpenAPI connectors to pick up corrected server-variable defaults and query encoding. Update computer images for corrected browser-side checkout amount parsing.
    • Plain HTTP SENTRY_DSN collectors are disabled; use trusted HTTPS to keep error reporting enabled.
    • The migration sets the database's default timezone to UTC. Reconnect existing sessions; if the migration login cannot change that setting, follow its warning and run the command as the database owner. Remove conflicting runtime-role timezone settings.
    • Optional RUN_DRAIN_ENABLED=true lets stopping workers finish turns before handing work over. Custom deploys should start replacements before stopping old workers (run execution).
    • Optional RAKAZO_API_REPLICAS and RAKAZO_WORKER_REPLICAS scale the production Compose stack. Multiple API replicas require webhook delivery for Telegram and iMessage and sufficient database connections during deploy overlap (configuration).
    • Optional RAKAZO_LOCAL_TOKENS_PER_MINUTE paces local model calls, RAKAZO_LOCAL_PROMPT_CACHE=off tunes context trimming for servers without prompt caching, and STUCK_WORK_NOTIFY_AFTER_MS / STUCK_WORK_EXPIRE_AFTER_MS control stalled-run reminders and expiry (local models, configuration).
    • COMPUTER_DEFAULT_MODE=dedicated gives new bots a Private computer. GPU access through SANDBOX_COMPUTER_COMPUTE_GPUS and browser proxying through RAKAZO_COMPUTER_PROXY are opt-in: GPUs expose the host driver to bots, and proxy credentials are readable inside the computer. Enable them only for trusted users (computer providers).

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.11.0...v0.12.0

  3. 0.11.0

    OpenNavo editorial

    Rakazo 0.11.0 lets people running AI teammates use This computer on Apple silicon without Docker and message bots from Microsoft Teams.

    Added
    This computer runs without Docker on Apple silicon.Message bots from Microsoft Teams.Watch an HTTPS address from a routine.
    Changed
    Webhook and email runs follow approval mode.
    Security
    Updated dependencies with known vulnerabilities.

    Rakazo 0.11.0, released 12 November 2026, lets people running persistent AI teammates use This computer on Apple silicon Macs without Docker, message bots from Microsoft Teams, and watch a public HTTPS address from a routine.

    Source: https://github.com/elie222/rakazo/releases/tag/v0.11.0

    • On Apple silicon Macs with macOS 26 or newer, This computer runs each bot in its own small VM. The firewall allows the internet but not the Mac or the local network.
    • Bots can be messaged from Microsoft Teams direct messages after the Teams account is linked.
    • Routines can watch a public HTTPS address and run only when its response changes, without starting a computer.
    • Webhook and email routine runs follow the owner's approval mode and Always allow list.
    • Third-party dependencies with known vulnerabilities were updated, including the HTTP client, mail sender, and XML and Markdown parsers.
  4. 0.10.0

    Expand

    GitHub Release

    Security

    • Updated the IP-address parser to fix a regular-expression denial of service affecting address parsing in rate limiting and proxy connections.
    • Failed MCP responses now have a total size limit even when they use an event stream, preventing oversized error responses from being buffered without a bound.

    Added

    • In the desktop app's This computer mode, bots can see and use Mac and Windows apps when Let bots use this computer is enabled. Screen access is limited to owner-started chats and asks for approval on the first use of each app in a Space (computer).
    • See subscription allowances, reset times and remaining credits in the account menu and Settings > Usage, with the same breakdown on the mobile account screen.
    • Voice connections can reuse a supported model sign-in for speech and transcription instead of requiring another key (voice and calls).
    • Added another optional remote computer adapter with suspend and resume support (computer providers).
    • Mobile now offers French, Hebrew, Hindi, Korean, Brazilian Portuguese and Turkish; Hebrew uses a right-to-left layout.
    • Owners can delete an unpaid organization from the plan choice, with the existing type-the-name confirmation.
    • Operators can cap an account's total hosted model-credit usage without deactivating it (billing).

    Changed

    • Deleting a bot on web or desktop names the group chats that will also be deleted, including their messages, files and pages.
    • Bots retain earlier conversation by token budget rather than stopping at eight exchanges, helping them follow decisions made earlier in a chat. Longer retained history can use more input tokens.
    • Bots receive a description of their Docker computer's tools and limits before starting work, and can offer the computer card when you need to see or scan its screen.
    • Admin-granted credit now includes computer hours for organizations without a monthly plan; purchased top-ups remain unchanged.
    • Mobile Activity replaces the regular chat list while the bell is on. Chat messages fade under the header and composer, page cards fill the message column, and Android answer options align to the left.
    • Self-host monitoring now alerts on sustained CPU overload and low available memory.

    Fixed

    • Local and compatible model streams honor the configured timeouts without a hidden five-minute limit. Leading inline thought blocks are treated as reasoning instead of appearing in replies, and rejected thinking levels recover from more endpoint error formats.
    • Unresponsive Docker computers recover instead of leaving commands hanging or blaming the model connection. Quiet long-running commands keep their connection alive; recovery retains home files but ends running programs.
    • Team computer file choosers open on the screen that requested them, screen startup waits for a chooser still launching, and stale process records no longer interfere with other screens after a restart.
    • Computer workspace saves avoid repeated large-buffer copies, and mounted-home checkpoints keep screens available. Kubernetes computers whose pods disappear are recognized as gone and replaced automatically.
    • Concurrent page-browser calls no longer read partially written settings. Group computer screens refresh when control changes in another tab, and typed input appears sooner during takeover.
    • Voice calls keep a steady audio session so replies play and the microphone keeps working. Web and desktop no longer transcribe the bot's own spoken reply, and failed playback reports an error.
    • Switching bots returns the transcript to the latest messages reliably. Snoozed open chats suppress ordinary browser notifications, and computer takeover requests produce one notification.
    • The Mac computer-view header clears the window buttons, page views show one scrollbar, and dated bot-to-bot messages are easier to scan.
    • The bot style setting stays available when no preference has been saved, so either style can be chosen.
    • Incoming voice notes and other supported attachments are accepted when their reported media type includes parameters.
    • Group messages, handoffs and membership changes no longer deadlock against a finishing bot turn.
    • Group messages keep author labels after a bot leaves or is deleted. Android incoming-call labels use the selected app language; Android 12 and later still use the phone language for system-provided Answer and Decline buttons.
    • Mobile dictation keeps a pending transcription across backgrounding or screen blur, and Send stays disabled until recording and transcription finish.
    • Android custom server settings show Save, sheets fit tablets and foldables, composer controls align with the text, and voice calls show a hang-up icon.

    Self-host upgrade notes

    • If you use hosted model-credit caps, finish updating both API and worker processes before relying on enforcement. Existing admitted calls can finish, and costs above their reservation can exceed a cap; personal model connections remain available (billing).
    • Local and compatible model streams now fully respect MODEL_STREAM_TIMEOUT_MS and MODEL_STREAM_IDLE_TIMEOUT_MS. Setting the idle timeout to 0 allows a stalled stream to wait until cancellation (model connections).
    • Mobile language resources require the new native mobile build; the desktop release does not distribute that build.

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.9.0...v0.10.0

  5. 0.9.0

    Expand

    GitHub Release

    Security

    • Mobile discards sign-ins that finish after a server change, preventing the previous server's session credentials from reaching the new server. Offline sign-out now retries session revocation when connectivity returns; Android also suppresses bot notifications while signed out. On iOS, old notification previews can still appear until revocation reaches the server.
    • Credentials passed in local MCP server launch arguments are hidden from tool output, errors and run history, including authorization flags, numeric secret values and passwords in URLs.
    • Incus computers explicitly start as an unprivileged user, including custom images without a declared user. Remote command working directories stay within the bot workspace, and team-chat attachment names are sanitized before entering bot context.
    • Computer helpers no longer load Python code from the bot-writable home directory or inherit the control token when starting commands, protecting saved logins and payment details.
    • The desktop computer viewer can no longer read the host clipboard. Copying from the bot's computer to the host clipboard is disabled; pasting into it remains available.
    • Calls ask for voice consent before recording audio for hosted transcription, including calls without a greeting.
    • Bot edits to pages shared by link now follow approval rules and show the proposed changes before publishing them. Never ask still saves without a prompt.
    • Hardened bot email authentication and send limits, encrypted existing inbox content when content encryption is enabled, and prevented untrusted attachments from replacing existing files. Deactivated owners no longer receive bot email.
    • Purchase approval recognizes payment-card forms that also request a security code or expiry. Account imports refuse temporary-file symlinks, and background helpers cannot bypass their read-only tools through connector name collisions.
    • Auto Review only accepts a single complete, valid verdict; malformed or ambiguous replies ask the owner instead of allowing the action. Oversized chat messages are refused, and future-dated group roster updates cannot prevent later membership removals.
    • Bounded third-party response reads to prevent unbounded memory use, and updated image and JavaScript dependencies for security fixes, including apt CVE-2026-109518.

    Added

    • Invite people into a Space to share bots, chats, memory, routines and its computer. Each member has their own unread state, notifications, connected accounts and billing. Browser logins on the shared computer are visible to everyone in the Space (Spaces).
    • Bots can hand read-only research to background helpers and keep chatting while it runs. Results return to the chat, and each helper's card has its own Stop control (bots and chats).
    • Snooze a chat until later, then bring it back to the inbox.
    • On iOS, a Live Activity shows working bots and those waiting for an answer on the Lock Screen and Dynamic Island. This needs the new app build.
    • Dictate into the mobile message box, review the text, and send it (voice and calls).
    • Create and edit routines, including email triggers, and edit or delete bot memory and shared notes on iOS and Android (routines).
    • Give bots their own email addresses, receive and search their inboxes, send email from chat, and start routines from incoming mail (bot email).
    • Set a spending limit for purchases bots make, review recent payments, and see order items on purchase approval cards (computer).
    • Speech connections can select a speech model, saved logins show their site icons, and open-egress Docker computers can reach IPv6-only sites with IPv4 fallback (voice, computer).
    • Connected MCP servers can show interactive apps in chat. Bots can also use optional deployment-funded paid data services for read-only lookups, with approval and credit accounting (integrations).
    • Create bots from ready-made templates, and choose Messages under Replies to keep working notes with tool steps while showing deliberate messages and the final answer in chat (bots and chats).
    • Bots can find files shared earlier in chat, send files to each other by path, read large files in line ranges, and look up the tool work behind earlier replies. Finished generated videos arrive automatically.
    • Self-hosters can provision and deactivate accounts through SCIM, and theme web and desktop colors, fonts and corners with RAKAZO_THEME (accounts, themes).
    • Mobile gains optional haptic feedback and an App Store update link in Settings. Haptics need the new app build.

    Changed

    • Desktop opens Cloud sign-in on first launch. Change server on sign-in and the app menu still open server setup.
    • The iOS inbox uses a native list with swipe and long-press actions. Mobile bot creation asks for a name and appearance, and inbox rows identify bots waiting for you.
    • Artifacts focuses on files bots made; settings, routines and connection states are simpler to scan. Web translations now cover previously untranslated strings.
    • New credit purchases and monthly plans top out at $200, while existing larger plans retain their credits and renewals. Credit checkout requests bank authentication. The Max own-key plan is now $99 monthly or $79 per month billed yearly; existing subscriptions retain their price.
    • Bot-to-bot turns no longer each trigger a notification. Running routines show their name, and stopping one leaves a note the bot can read.
    • Desktop-managed local stacks allow private model and connector endpoints. Docker deployments can reach host-local model and speech servers through loopback addresses when private endpoints are enabled (local models).

    Fixed

    • Reading web pages with very large numbers of HTML elements no longer freezes unrelated sign-ins, page loads and chat runs. Oversized pages use simpler text extraction, which may include navigation.
    • Rejected personal access tokens open model connection recovery, and unavailable hosted models offer another model instead of showing a generic server error.
    • Mobile drafts and unsent attachments survive chat changes, rejected sessions and cache cleanup. Failed dictated sends retain their words without duplication, and near-silent recordings are discarded before transcription.
    • Sending, stopping, streaming and answering cards are more reliable while other chat operations are running. Background command output reaches the next model request, and loop detection stops equivalent repeated tool calls.
    • Android avoids a native memory-sampling launch crash, and long mobile messages and streamed replies cause fewer layout stalls.
    • Calls can be answered while bot lists load, stay with their original Space, stop on sign-out, and no longer compete with chat read-aloud. Android long-press menus and notification content work reliably.
    • Computer screens reconnect through restarts, large workspaces finish saving, and oversized backups no longer prevent sleep. Unresponsive computer, storage and encryption services no longer leave requests hanging indefinitely.
    • Interrupted model streams retry, backup models use their own thinking settings, and compatible model and MCP connections honor configured proxies. Settings retain edits across saves and reconnects.
    • Connecting an MCP server whose OAuth requests many permissions no longer fails with "MCP URL exceeds 2048 characters". Native OIDC sign-in accepts authorization URLs that previously failed validation.
    • Billing actions stay with the Space shown in the window; paid own-key plans receive their computer hours regardless of model funding, and interrupted credit holds settle automatically.
    • Account exports containing nested ZIP files or files beginning with zero bytes import correctly. Account and Space deletion recover from interruptions without accepting new work during deletion.
    • Pinned installs download their Compose files from the chosen release. Updates remove replaced unused images, migrations run before deployment, and volume startup avoids needlessly changing ownership of every file.
    • OpenAPI tools retain parameter descriptions, GraphQL tools preserve explicit null inputs, and paused routines ignore webhook deliveries.

    Self-host upgrade notes

    • Source installs now require Node.js 24.15 or newer on the 24.x line, or Node.js 26+, and pnpm 12.18. Published images include compatible runtimes. Run migrations before restarting the API and worker (upgrading).
    • Update computer images to receive helper isolation, purchase safeguards and image security fixes. Mobile native changes, including the SDK upgrade and Live Activities, require new store builds; an over-the-air update cannot deliver them.
    • Incus-backed computers require Incus 6.11 or newer. Docker computers adopt their owner's time zone and language; existing computers are replaced on their next start, preserving home files and browser profiles but closing running apps.
    • Production Compose database memory defaults target an 8 GB host. Smaller hosts should set POSTGRES_MEMORY_LIMIT, POSTGRES_SHARED_BUFFERS and POSTGRES_EFFECTIVE_CACHE_SIZE for their capacity; the published-images Compose setup is unchanged.
    • Computer provider settings are hidden by default. Set COMPUTER_SETTINGS_ENABLED=true to edit them; saved connections continue working (computer providers).
    • Docker loopback model and speech URLs now refer to the Docker host. Private endpoints still require MCP_ALLOW_PRIVATE_ENDPOINT; on Linux, the service must listen on an address reachable from the Docker bridge (models).
    • Bot outbound mail needs the sending-domain DNS configuration and EMAIL_* settings on the worker as well as the API. INBOUND_EMAIL_RELAY_ARC_DOMAIN optionally trusts a configured relay's sealed authentication results (bot email).
    • Deactivating an account removes its memberships in other people's Spaces, transfers its work to the Space owner and pauses its routines. Reactivating the account does not restore those memberships (accounts).
    • Reimport existing GraphQL sources to regenerate schemas with nullable inputs. Optional paid services use PAID_SERVICES_PROVIDER, PAID_SERVICES_API_KEY and PAID_SERVICES_BASE_URL; without managed credits, usage charges the operator's service account (integrations).

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.8.0...v0.9.0

  6. 0.8.0

    Expand

    OpenNavo editorial

    Rakazo 0.8.0 adds iOS share-sheet support, more keyboard shortcuts, desktop chat search and a full Turkish translation.

    Rakazo 0.8.0 was released on 2026-11-04. This update adds iOS share-sheet support, more keyboard shortcuts, desktop chat search and a full Turkish translation.

    New

    • On iPhone and iPad, an image pasted into a chat's message field is added as an attachment; text copied with it still goes into the field.
    • Rakazo appears in the iOS share sheet: share a link, text, photos or files from any app, pick a bot, and it lands in that bot's message field as a draft.
    • More keyboard shortcuts on web and desktop: start a group chat, connect apps, open the chat's details panel, jump to the message box and dictate. Cmd/Ctrl+/ lists every shortcut.
    • Cmd/Ctrl+F in the desktop app finds text in the open chat, highlighting every match; searching bots moves to Cmd/Ctrl+Shift+F.
    • The web app is fully translated into Turkish.
    • When the desktop app runs its own local server, Settings shows the "Let bots use this computer" switch.
    • Self-hosters can make DeepSeek the default model with PI_DEFAULT_PROVIDER=deepseek and DEEPSEEK_API_KEY.
    • Long-wait "still needs an answer" reminders and stopped-chat notices now show as browser and desktop alerts.

    Changed

    • A group message that names no bot now reaches every bot in the group instead of only the first; each bot decides whether to reply, and an untagged message can start a run for up to ten bots.

    Fixed

    • Pressing Stop now ends a quiet model call or a long-running tool within about a second.
    • Connector and category approval rules now apply to tools named with a hyphen, like <app>-<action>.
    • Switching chats on web no longer deletes unsent attachments, and archiving a chat keeps them.
    • Renaming a model connection no longer resets unsaved edits in the same form.
    • Linux desktop update checks treat a brief network drop as offline instead of showing an update error.
  7. 0.7.0

    Expand

    OpenNavo editorial

    Adds multiple organizations under one login, three own-model plan tiers, a computer-use model, Polish, and security fixes.

    Rakazo 0.7.0 was released on 2026-11-04 with multiple organizations under one login, three own-model plan tiers, a computer-use model for bots, Polish, and a set of security fixes.

    • Better Auth is updated to 1.7.16 for its November security fixes. The most serious one was in mobile sign-in, where the authorization proxy could sign values it did not issue.
    • Signing out, signing in to another account, or switching server on mobile now stops read-aloud and clears the replies still waiting to be read.
    • Disconnecting an MCP server's OAuth stays in effect even when a sign-in was still finishing, including the first sign-in to a server. A late token no longer marks the server as connected again.
    • A connected tool named delete_bot now runs on its own service instead of being sent to Rakazo's built-in bot archiving.
    • After signing in as another account on mobile, the call card no longer shows the previous account's initial.
    • The Android app limits how much a notification check can download in the background, so a faulty server or proxy cannot make it use unbounded memory.
    • When a computer's saved files are deleted after the retention period, a copy cached on a computer host is deleted too.
    • Two computer pairings that arrive at the same moment can no longer both get past the limit of ten computers per account.
    • On Incus, stopping or deleting a computer checks that the instance belongs to it, so a wrong stored reference cannot tear down another bot's computer.
    • One login can own several organizations, such as Personal and Work, each with its own billing. Create one in Settings → Organization and switch between them from the account menu.
    • Rakazo is available in Polish on web, desktop and mobile, including account emails.
    • The own-model plan comes in three tiers. Standard is the existing plan; Pro and Max give bigger cloud computers and more computer hours each month. Choose a tier when you subscribe, and move between tiers from Billing on web and mobile.
    • Bots can hand screen and browser work to a second model. Set a Computer-use model in Settings → Models and a bot on a text-only or self-hosted model passes visual tasks to it in the middle of a reply.
    • The web and desktop app now notifies you when an agent in another chat finishes a reply, asks you something, asks you to take over its screen, or fails. Clicking the notification opens that chat, and muted chats stay quiet.
    • Web and desktop notifications now show the agent's avatar.
    • Self-hosters can run bot computers as Incus application containers with SANDBOX_PROVIDER=incus, without Docker or Kubernetes on the host.
    • Changing your account timezone now moves your routines with it, so a Monday 09:00 routine still runs at 09:00 local time. Routines pinned to a specific timezone stay where they are.
    • A bot's notification picture on the phone now matches its avatar in the app.
    • Long bot instructions no longer stretch the settings panel. The box grows up to a set height, then scrolls.
    • Android release builds are smaller and faster, because unused code is removed when the app is built.
    • A computer still running an older image no longer asks "Complete a payment on this page?" on every click after a server upgrade.
    • During a voice call, a silent turn no longer leaves the microphone off for the rest of the call.
    • On a self-hosted server opened over plain HTTP on a local network, importing an agent, the disk Clean up button and desktop single sign-on work again.
    • Tapping Add custom on Integrations does something again on Android.
    • Wide tables and code blocks in chat scroll sideways on Android.
    • A bot reading its own settings gets them in one piece whenever they fit, even with long instructions.
    • iOS builds that self-hosters make with expo prebuild open in Xcode and install on a phone again.
    • Removing one of two attached files that share a name, size and date no longer removes both.
    • Signing in with a model subscription now notices when the sign-in tab opened, instead of always showing the steps for a blocked popup.
  8. 0.6.0

    Expand

    OpenNavo editorial

    Requires signed desktop updates, redesigns the vault and adds approval rules, grouped activity and disk warnings.

    Rakazo 0.6.0 was released on 2026-11-04. This update requires signed desktop updates, redesigns the vault and adds approval rules, grouped activity and disk warnings.

    Security

    • Every desktop update now has to be signed, Windows releases can no longer be built unsigned, and Linux AppImage updates come with a signature that the app checks before it installs them.
    • Linux installs from before this release can't check signatures yet, so they accept this update the same way as before; every update after it is checked.

    Added

    • The vault holds payment cards and contacts (addresses, phones and emails) next to logins, API keys and variables, and each item has a title you choose and an optional note on when the bot should use it.
    • Settings → Vault is one list that opens each item in place, and a chat request is a short row with an Add button.
    • In Approvals settings you can add a rule for a tool by name before the bot ever asks about it, and switch any saved tool, connector or site rule between Allow, Ask and Block.
    • Phone notifications show which agent sent them, with its name and picture.
    • Activity groups chats into Needs attention, Working, Unread and Recent, and each section folds while empty ones are hidden.
    • A routine run can create new schedules for follow-up work, but it still can't change existing ones.
    • A bot is told when its computer's disk is 85% full, and from 90% you see a warning on that computer with a button that asks the bot to clean up.

    Changed

    • Dark mode has clearer contrast, chat text is a little larger, and each bot has one bright color shared by its avatar, name and your message bubbles.
    • How your bots look is now one account setting, Bot style in Settings (Original or Rakazo), instead of a choice on every new bot.
    • Text fields no longer have a grey fill that made them look disabled.
    • A bot rewriting its own instructions no longer posts an "Instructions updated" card in the chat.
    • A failed daily check-in no longer notifies the bot's owner, and the bot isn't tried again for a week.
    • Usage moved out of the account menu; it is still in Settings.
    • Computer saves skip folders that build tools mark as rebuildable caches, so build output no longer pushes a home past the save limit.
    • On deployments with hosted billing, the saved copy of a computer's files is deleted 30 days after a paid plan ends, or after 90 days without use on accounts that never paid; the organization's owner gets a warning email about a week before.

    Fixed

    • Opening a chat with a busy bot no longer makes the conversation jump when the row saying what the bot is doing appears.
    • Deleting a group always removes its stored files and its page links, even when stopping its cancelled runs fails.
    • A bot with long instructions can edit them again, because it now reads them in full before rewriting.
    • The Android app builds from source again.
  9. 0.5.0

    Expand

    OpenNavo editorial

    Tightens computer access and approvals, and adds bot-built pages, follow-ups, incoming mobile calls and Telegram group chats.

    Rakazo 0.5.0 was released on 2026-11-03. This update tightens computer access and approvals, and adds bot-built pages, follow-ups, incoming mobile calls and Telegram group chats.

    Security

    • When you turn on "Let bots use this computer" in the desktop app, the computer stays connected only as long as the sign-in that connected it, and the "This computer" server accepts only its first account.
    • The desktop app's native speech recognition and Local Computer Access now need an HTTPS server unless it runs on the same machine.
    • Turning off computer access now stays off even when the app can't save the choice to disk.
    • An account whose email address is not verified can no longer link SSO, and a password reset on an unverified account removes its SSO links, passkeys and paired devices.
    • Before a bot clicks a button that pays on a website, such as Pay, Buy now or Place order, it shows an approval card and acts only after "Allow once", in every approval mode.
    • A bot connected to Slack uses the owner's memory and notes only when the owner writes to it; coworkers and guests get group-chat treatment.
    • A remote MCP server can send back at most 16 MB per response, and previews of files on a stopped computer must stay inside the computer's home folder.

    Added

    • Bots can build pages, such as dashboards, from a fixed set of components; a page appears as a card in the chat and opens full screen with the chat docked below, and the Library lists pages to rename, pin, delete or share by link.
    • When a conversation leaves something open until a known time, the bot can set itself one follow-up for then without being asked, and it stays silent if the item is already done.
    • When a bot calls you, the iOS and Android apps ring, with a full-screen call while the app is open and a system call screen or lock-screen notification when it is not.
    • When a site texts or emails a sign-in code, the bot asks for it with a "Code for" card in the chat and fills it into the page without seeing it.
    • Telegram bots can take part in group chats, where a group shows up under Requests and each member approves it from their own Messaging settings.
    • Voice notes sent to a bot in a direct message now arrive with a transcript beside the audio file.
    • Bots check in once a day on unfinished work, and each bot can turn this off with "Daily check-ins on unfinished work".
    • Bots can edit or delete a note in their own memory instead of only adding new ones, with a 4 KB cap on a bot's own memory.
    • Bots can use each connected account of the same app, choosing the account through its tools.
    • Pages in the bot's browser can open new tabs and pop-ups, a downloaded file is saved in the bot's Downloads folder, and the result gives its name, path, size and type.
    • In Settings → Computer, admins can choose where new computers run without editing environment variables, and any account can send its own Team Computers to a Wuying cloud desktop.
    • The own-key plan can be paid yearly, with a Monthly / Yearly switch that shows how much yearly saves.
    • A routine shows "Schedule delayed" when its next scheduled run is more than five minutes overdue, and messaging your bot just "stop" or "stop now" stops its work.
    • The desktop app's menus, dialogs and account emails now come in every app language, and long model and provider lists can be searched on web and mobile.

    Changed

    • A bot's memory view says roughly how much of the oldest part it doesn't see when its memory is larger than the 32 KiB it can read.
    • Bots on Boat computers get the page tools that Docker computers already had.

    Fixed

    • Slack messages over 8,000 characters reach the bot as raw Slack markup, and chart specs beyond the new limits fail with an error.
    • A bot's work stops when its owner sends a bare stop message.
    • Private routines and skills stay out of shared channels.
  10. 0.4.0

    Expand

    OpenNavo editorial

    Adds iMessage and macOS voices, keyless secret wrapping, more computer providers, chat-wide search and a set of security and reliability fixes.

    Rakazo 0.4.0 was released on 2026-11-01. This update adds iMessage and macOS voices, keyless secret wrapping, more computer providers, chat-wide search and a set of security and reliability fixes.

    Security

    • Row-level security's system bypass now needs a key that only the app holds, so SQL running for one Space can no longer give itself access to every Space.
    • Hosts hardened with harden-host.sh now drop inbound IPv4 TCP packets that carry IP options and turn off multipath TCP, which blocks the known path to CVE-2026-98432 until a fixed kernel is running.
    • Dropping a connection partway through a WebSocket upgrade no longer crashes the API or the web server for every user.
    • Logs redact more sensitive data, including credentials after any HTTP auth scheme, API keys in headers such as x-api-key, and quoted JSON fields such as access_token.
    • While someone is teaching a bot on its computer, open_path and launch_app are refused like the other screen tools.
    • Composio and Pipedream connections record the exact external account you approved and use only that account.

    Added

    • iMessage through Photon: set PHOTON_PROJECT_ID and PHOTON_PROJECT_SECRET to link a bot to an iMessage number, with no public URL needed, and self-hosted deployments can run several Photon projects.
    • A server running on macOS offers a keyless macOS voice provider that reads replies with the voices installed on that Mac.
    • With a key manager configured, secrets in .env such as ENCRYPTION_KEY and BETTER_AUTH_SECRET can be stored wrapped by it, so a copy of .env no longer holds usable secrets.
    • Bots can search all of your own chats in the current space, not just the chat you are in, and open the messages they find, only in runs you start directly.
    • Login cards have a "Save to Vault" switch, on by default; turn it off and the login is kept encrypted only for that run and that site.
    • When you add a custom MCP server, OpenAPI or GraphQL source on mobile, you can choose bearer token, an API key in a header you name, or OAuth in your browser.
    • SANDBOX_COMPUTER_MOUNTS (Docker computers only) mounts host folders into every bot computer, read-only unless an entry adds rw.
    • MAX_ATTACHMENTS_PER_MESSAGE (1 to 100, default 4) sets how many files fit in one message.
    • Plugin authors can submit a public GitHub repository to the Rakazo marketplace, and admins approve or reject submissions on /admin/plugins.
    • boxd and Wuying join as remote computer providers, and the mobile and desktop apps can use a self-hosted server behind an access proxy such as Cloudflare Access.
    • On the macOS desktop app, dictation and the listening side of voice calls use the Mac's built-in speech recognition.
    • Excel spreadsheets (XLS and XLSX) can be attached to chat messages on web and mobile.
    • Dictation and calls listen for the speaker's own regional variant of Spanish and other languages, and routine times use the language's clock.
    • The Simplified Chinese and Spanish web apps are fully translated.
    • The mobile composer keeps a separate draft for each conversation.
    • Bots can change their own instructions, model, thinking level, read-aloud and voice when you ask in a chat you started, with a "Settings updated" card and Undo for settings changes.

    Changed

    • Only admins listed in RAKAZO_ADMIN_EMAILS can add or edit stdio MCP servers, and bots can add remote servers only.
    • Messages between bots show up in a bot's chat as one centered line, such as "Messaged X", and tapping it opens the bot-to-bot conversation read-only.
    • A bot you tag in the message box appears as a card where you typed it, and Backspace removes the whole mention.
    • Importing an agent starts only from "Import an agent" in Settings → General and always creates a new bot.
    • A takeover request that nobody acts on ends after 30 minutes instead of a day.
    • Bots switch to the Space's backup model when the provider rejects the main model's key or sign-in, instead of failing.
    • The desktop app on Windows uses the standard Windows title bar and window buttons.

    Fixed

    • RAKAZO_LOCAL_MAX_TOKENS is now the output limit a local model is asked for, so a longer reply is no longer cut off and retried.
    • A bot with more than twenty MCP tools reaches them through the lazy tool catalog with intact arguments.
    • Arguments of a stdio MCP server are stored encrypted and no longer returned to clients.
    • MAX_UPLOAD_SIZE_MB now applies to every API route.
    • "Use my computer" now connects on deployments where the web server fronts the API.
    • When the computer image is missing on the Docker host, the supervisor pulls it or builds the stock rakazo/computer image instead of failing every start.
    • Boat, E2B, Novita, Daytona and CreateOS computers that are already running are reused by each run instead of reconnected.
  11. 0.3.6

    Expand

    GitHub Release

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.3.5...v0.3.6

  12. 0.3.5

    Expand

    GitHub Release

    What's Changed

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.3.4...v0.3.5

  13. 0.3.4

    Expand

    GitHub Release

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.3.3...v0.3.4

  14. 0.3.3

    Expand

    GitHub Release

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.3.2...v0.3.3

  15. 0.2.0

    Expand

    GitHub Release

    Highlights

    • Optional OIDC single sign-on, an optional Infisical secret store, and Stripe seat billing (each off unless configured).
    • Ordered backup models when a provider fails, and routines that can run on their own model.
    • Optional shared ticket board (TICKET_BOARD_ENABLED, off by default).
    • Restricted network access for computers (opt-in), SANDBOX_IDLE_MS=0 to keep computers awake, a production Compose overlay, and SANDBOX_MAX_COMPUTERS_PER_USER.
    • New providers: the CreateOS sandbox, a Daytona snapshot option, and Serenity memory.

    Chat

    • Replies to a specific message, quoting part of a message, and reply quotes for images and attachments.
    • Time separators, site icons before links, Markdown tables shown as cards, and remote images loaded on tap.
    • Zip files allowed as attachments.

    Models

    • Model settings reorganized around connection state, with connections tested before saving.
    • OpenAI-compatible settings, Codex model discovery, and the new GPT-6 and Claude Opus 5.5 models.

    Mobile (the server must be on this release)

    • Voice calls with transcripts and a voice per bot, inline images, an artifacts browser, and native iOS styling.
    • Seven performance fixes: faster typing in long threads and far fewer wasted re-renders and requests.

    Computers

    • gh CLI included, Python tools can be installed without root, an action to focus or launch an app, and recovery steps when a computer is unavailable.

    Other

    • French locale, and roughly 170 bug fixes.

    Thanks to the contributors to this release: ald3b, Fatih Karahan, Smelter Labs, Paul Preibisch, Brice Le Blevennec, Li Rui and many others.

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.1.6...v0.2.0

  16. 0.1.6

    Expand

    GitHub Release

    What's Changed

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.1.5...v0.1.6

  17. 0.1.5

    Expand

    GitHub Release

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.1.4...v0.1.5

  18. 0.1.3

    Expand

    GitHub Release

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.1.2...v0.1.3

  19. 0.1.2

    Expand

    GitHub Release

    Rakazo v0.1.2 includes improvements across desktop, server, and the shared web interface.

    • Persistent team bot desktops, more reliable computer recovery, and cloud coding agents.
    • Multi-account integrations, optional integration catalogs, GraphQL tools, and signed GitHub routine triggers.
    • Configurable model reasoning, editable agent memory and skills, and protected credential handoff.
    • Simpler onboarding and chat controls, faster integration catalogs, and mobile layout and theme fixes.
    • Security and reliability fixes for permissions, secret handling, backups, network responses, and server updates.

    Downloads include signed and notarized macOS installers and a Linux AppImage. Server images are published separately by the server-image workflow.

    Mobile 1.0.1 uses a new native runtime and requires new iOS and Android builds; it is not delivered to 1.0.0 installations as an OTA update.

  20. 0.1.1

    Expand

    GitHub Release

    What's Changed

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.1.0...v0.1.1

  21. 0.1.0

    Expand

    GitHub Release

    What's Changed

    New Contributors

    Full Changelog: https://github.com/elie222/rakazo/compare/v0.1.0-beta...v0.1.0