跳到正文

Rakazo 版本记录

开源 Grok Bot 替代品:面向会真正执行任务的常驻 AI 队友,使用你自己的密钥、模型和电脑。

下载地址来自 github.com/elie222/rakazo · OpenNavo 不托管安装包
  1. 0.13.0

    最新

    OpenNavo 编辑

    Rakazo 0.13.0 让运行常驻 AI 队友的人把会议机器人送进通话,并在发送前编辑 Gmail 和 Slack 草稿。

    新增
    会议机器人加入通话并返回逐字稿。发送前编辑 Gmail 和 Slack 草稿。用邮件邀请外部嘉宾进入 Space。
    安全
    审批覆盖受外部内容影响的工作。
    修复
    Mac 在迁移前恢复已关闭的渲染进程。

    Rakazo 0.13.0 于 2026 年 11 月 19 日发布,让运行常驻 AI 队友的人把会议机器人送进支持的通话,并在发送前编辑纯文本的 Gmail 和 Slack 草稿。

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

    • 会议机器人可以加入支持的通话,返回带讲话人标记的逐字稿,并从 Google 日历排期出席。
    • 可以在审批卡片里编辑纯文本的 Gmail 和 Slack 草稿,再发送。
    • 可以用邮件邀请外部嘉宾进入指定的 Space。
    • 审批设置现在覆盖例行、已连接的聊天应用,以及受外部内容影响的工作。无人值守的审批在 30 分钟后失效。
    • 在 Mac 上,已关闭的渲染进程可以恢复,应用会先等本地数据库就绪,再迁移。
  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 编辑

    Rakazo 0.11.0 让运行 AI 队友的人在 Apple 芯片上不用 Docker 使用“这台电脑”,并从 Microsoft Teams 给机器人发消息。

    新增
    Apple 芯片上不用 Docker 运行这台电脑。从 Microsoft Teams 给机器人发消息。例行可监视一个 HTTPS 地址。
    变更
    Webhook 和邮件运行遵循审批模式。
    安全
    更新存在已知漏洞的依赖。

    Rakazo 0.11.0 于 2026 年 11 月 12 日发布,让运行常驻 AI 队友的人在 Apple 芯片 Mac 上不用 Docker 就能使用“这台电脑”,也能从 Microsoft Teams 给机器人发消息,并让例行监视一个公开 HTTPS 地址。

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

    • 在 macOS 26 或更新的 Apple 芯片 Mac 上,“这台电脑”让每个机器人在自己的小型虚拟机里运行。防火墙允许访问互联网,但不允许访问这台 Mac 或本地网络。
    • 关联 Teams 账户后,可以从 Microsoft Teams 私信给机器人发消息。
    • 例行可以监视一个公开 HTTPS 地址,只在响应变化时运行,不必启动一台电脑。
    • Webhook 和邮件例行按所有者的审批模式和“始终允许”列表运行。
    • 更新了存在已知漏洞的第三方依赖,包括 HTTP 客户端、邮件发送器,以及 XML 和 Markdown 解析器。
  4. 0.10.0

    展开

    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

    展开

    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

    展开

    OpenNavo 编辑

    Rakazo 0.8.0 新增 iOS 分享面板支持、更多键盘快捷键、桌面端聊天搜索以及完整的土耳其语翻译。

    Rakazo 0.8.0 于 2026-11-04 发布。本次更新新增 iOS 分享面板支持、更多键盘快捷键、桌面端聊天搜索以及完整的土耳其语翻译。

    新增

    • 在 iPhone 和 iPad 上,粘贴到聊天消息输入框的图片会作为附件添加;随图片一同复制的文字仍会进入输入框。
    • Rakazo 会出现在 iOS 分享面板中:从任意应用分享链接、文字、照片或文件,选择一个机器人,内容会作为草稿进入该机器人的消息输入框。
    • 网页端和桌面端新增更多键盘快捷键:发起群聊、连接应用、打开聊天的详情面板、跳到消息输入框以及听写。Cmd/Ctrl+/ 可列出全部快捷键。
    • 桌面应用中的 Cmd/Ctrl+F 可在当前打开的聊天中查找文字,并高亮所有匹配项;搜索机器人改为 Cmd/Ctrl+Shift+F。
    • 网页应用已完整翻译为土耳其语。
    • 当桌面应用运行自带的本地服务器时,Settings 会显示“Let bots use this computer”开关。
    • 自托管用户可以通过 PI_DEFAULT_PROVIDER=deepseek 和 DEEPSEEK_API_KEY 将 DeepSeek 设为默认模型。
    • 长时间等待时的“still needs an answer”提醒和聊天已停止的通知,现在会以浏览器和桌面通知的形式显示。

    变更

    • 群聊中未指定机器人的消息现在会发送给群内的每个机器人,而不再只发给第一个;每个机器人自行决定是否回复,一条未标记的消息最多可触发十个机器人的运行。

    修复

    • 按下 Stop 后,静默的模型调用或长时间运行的工具现在会在大约一秒内结束。
    • 连接器和类别的审批规则现在也适用于带连字符命名的工具,例如 <app>-<action>。
    • 在网页端切换聊天不再删除未发送的附件,归档聊天时也会保留这些附件。
    • 重命名模型连接不再重置同一表单中未保存的修改。
    • Linux 桌面端的更新检查会将短暂断网视为离线,而不再显示更新错误。
  7. 0.7.0

    展开

    OpenNavo 编辑

    Rakazo 0.7.0 于 2026-11-04 发布,支持在同一个登录账号下拥有多个组织,带来三档自带模型套餐、面向机器人的 Computer-use model、Polish 以及一系列安全修复。

    • 已将 Better Auth 更新至 1.7.16,以包含其 11 月的安全修复。最严重的问题出在移动端登录:授权代理可能签署并非由它签发的值。
    • 在移动端退出登录、登录其他账号或切换服务器时,现在会停止朗读,并清除仍在等待朗读的回复。
    • 断开 MCP 服务器的 OAuth 后,即使登录仍在完成中(包括首次登录某台服务器),断开状态也会保持有效。迟到的令牌不会再将该服务器重新标记为已连接。
    • 名为 delete_bot 的已连接工具现在运行在自己的服务上,而不再被发送到 Rakazo 内置的机器人归档功能。
    • 在移动端登录其他账号后,通话卡片不再显示上一个账号的首字母。
    • Android 应用会限制通知检查在后台可下载的数据量,因此即使服务器或代理出现故障,也不会让它占用无上限的内存。
    • 当某台电脑的已保存文件在保留期后被删除时,托管该电脑的主机上所缓存的一份副本也会被删除。
    • 同时到达的两个电脑配对不再能双双突破每个账号十台电脑的上限。
    • 在 Incus 上,停止或删除电脑时会检查实例是否确实属于该电脑,因此错误的存储引用不会破坏其他机器人的电脑。
    • 同一个登录账号可以拥有多个组织,例如 Personal 和 Work,每个组织都有自己的 Billing。可在 Settings → Organization 中创建组织,并从账号菜单中切换。
    • Rakazo 现已在网页端、桌面端和移动端提供 Polish,包括账户邮件。
    • 自带模型套餐分为三档。Standard 是现有套餐;Pro 和 Max 提供规格更大的云电脑,并且每月提供更多电脑使用时长。订阅时可选择档位,并可在网页端和移动端的 Billing 中切换档位。
    • 机器人可以把屏幕和浏览器方面的工作交给第二个模型。在 Settings → Models 中设置 Computer-use model 后,使用纯文本模型或自托管模型的机器人会在回复过程中把视觉任务交给后者。
    • 网页端和桌面端应用现在会在以下情况通知你:另一个聊天中的智能体完成回复、向你提问、请你接管它的屏幕,或执行失败。点击通知会打开该聊天;已静音的聊天仍保持安静。
    • 网页端和桌面端通知现在会显示智能体的头像。
    • 自托管用户可以通过 SANDBOX_PROVIDER=incus 将机器人所用的电脑作为 Incus 应用容器运行,无需在主机上安装 Docker 或 Kubernetes。
    • 更改账号时区后,你的例行任务会随之迁移,因此周一 09:00 的例行任务仍会在当地时间 09:00 运行。固定到特定时区的例行任务则保持原位。
    • 机器人在手机上的通知图片现在与应用内的头像一致。
    • 较长的机器人指令不再把设置面板撑开。输入框会增高到设定高度,然后滚动。
    • Android 发布版本更小、更快,因为构建应用时会移除未使用的代码。
    • 仍在运行旧镜像的电脑,在服务器升级后不会再每次点击都询问 "Complete a payment on this page?"。
    • 在语音通话中,如果一轮发言没有声音,麦克风不会再在通话剩余时间里保持关闭。
    • 在局域网中通过明文 HTTP 打开的自托管服务器上,导入智能体、磁盘的 Clean up 按钮和桌面端单点登录都恢复正常。
    • 在 Android 上,点击 Integrations 中的 Add custom 现在会重新生效。
    • 聊天中的宽表格和代码块在 Android 上可以横向滚动。
    • 机器人读取自己的设置时,只要内容装得下,就会一次性拿到完整设置,即使指令很长。
    • 自托管用户用 expo prebuild 构建的 iOS 版本重新可以在 Xcode 中打开,并安装到手机上。
    • 删除两个同名、同大小、同日期的附件中的一个时,不再会把两个都删掉。
    • 使用模型订阅进行登录时,现在能检测到登录标签页已经打开,而不再总是显示弹窗被拦截时的操作步骤。
  8. 0.6.0

    展开

    OpenNavo 编辑

    Rakazo 0.6.0 于 2026-11-04 发布。本次更新要求桌面端更新必须签名,重新设计了保管库,并新增审批规则、分组动态和磁盘警告。

    安全

    • 现在每个桌面端更新都必须签名,Windows 版本不能再以未签名方式构建,Linux AppImage 更新会附带签名,应用在安装前会先进行校验。
    • 在此版本之前安装的 Linux 版本还无法校验签名,因此它们会像以前一样接受这次更新;此后的每次更新都会进行校验。

    新增

    • 保管库现在除了登录信息、API 密钥和变量,还存放支付卡和联系人(地址、电话和电子邮件),每个条目都有你自定义的标题,以及一条可选备注,说明机器人应在何时使用它。
    • 设置 → 保管库是一个列表,可在原位置展开每个条目,而聊天中的请求则以简短的一行显示,并带有“添加”按钮。
    • 在审批设置中,你可以按名称在机器人发问之前就为某个工具添加规则,并可在“允许”“询问”和“阻止”之间切换任何已保存的工具、连接器或站点规则。
    • 手机通知会显示是哪位智能体发送的,包括其名称和头像。
    • 动态将聊天归类为“需要关注”“进行中”“未读”和“最近”,各分区均可折叠,空分区会自动隐藏。
    • 一次例行运行可以为后续工作创建新的计划,但仍不能更改现有的计划。
    • 当机器人所在电脑的磁盘占用达到 85% 时,机器人会收到通知;达到 90% 及以上时,你会在该电脑上看到一条警告,其中的按钮可让机器人进行清理。

    变更

    • 深色模式的对比度更清晰,聊天文字稍微变大,每个机器人都拥有一种明亮颜色,统一用于其头像、名称和你的消息气泡。
    • 机器人的外观现在改为一项账户设置——设置中的“机器人风格”(Original 或 Rakazo),而不再是每个新机器人的独立选择。
    • 文本输入框不再有灰色填充,以免看起来像是已禁用。
    • 机器人改写自身指令后,不会再在聊天中发布“指令已更新”卡片。
    • 每日签到失败不再通知机器人的所有者,并且一周内不会再次尝试该机器人。
    • 用量已从账户菜单中移出;它仍在设置中。
    • 电脑保存会跳过构建工具标记为可重建缓存的文件夹,因此构建产物不会再让主目录超出保存上限。
    • 在使用托管计费的部署中,已付费方案结束后 30 天,或从未付费的账户在 90 天未使用后,电脑文件的已保存副本会被删除;组织所有者会提前约一周收到警告邮件。

    修复

    • 打开与忙碌中的机器人的聊天时,随着显示机器人正在做什么的那一行出现,对话不再跳动。
    • 删除群组时,即使停止其已取消的运行失败,也始终会移除其存储的文件和页面链接。
    • 指令很长的机器人现在可以再次编辑这些指令,因为它会在改写前完整读取它们。
    • Android 应用重新可以从源代码构建。
  9. 0.5.0

    展开

    OpenNavo 编辑

    Rakazo 0.5.0 于 2026-11-03 发布。本次更新收紧了电脑访问和审批,并新增了机器人搭建的页面、后续跟进、来电手机通话和 Telegram 群聊。

    安全

    • 当你在桌面应用中开启“Let bots use this computer”(允许机器人使用此电脑)时,电脑只在连接它的那次登录持续期间保持连接,并且“This computer”服务器只接受它的第一个账户。
    • 桌面应用的原生语音识别和 Local Computer Access(本地电脑访问)现在需要 HTTPS 服务器,除非它运行在同一台机器上。
    • 关闭电脑访问后,即使应用无法将这一选择保存到磁盘,它也会保持关闭。
    • 电子邮件地址未经核验的账户不能再关联 SSO,而对未核验账户进行密码重置会移除其 SSO 关联、通行密钥和已配对设备。
    • 机器人点击网站上会付款的按钮(例如 Pay、Buy now 或 Place order)之前,会显示一张审批卡片,并且只有在“Allow once”(仅允许一次)之后才会操作,无论处于哪种审批模式。
    • 连接到 Slack 的机器人只有在该所有者向它写入时才会使用所有者的记忆和笔记;同事和访客按群聊处理。
    • 远程 MCP 服务器每次响应最多可返回 16 MB,已停止电脑上的文件预览必须留在该电脑的主文件夹内。

    新增

    • 机器人可以用一组固定的组件搭建页面,例如仪表板;页面会以卡片形式出现在聊天中,打开时全屏显示,聊天停靠在下方,并且“Library”会列出页面,可供重命名、置顶、删除或通过链接分享。
    • 当某段对话把某件事留待处理直到某个已知时间时,机器人无需被要求即可为自己在该时间设置一次后续跟进;如果该事项已经完成,它会保持沉默。
    • 当机器人给你打电话时,iOS 和 Android 应用会响铃:应用打开时显示全屏通话,未打开时显示系统通话界面或锁屏通知。
    • 当网站通过短信或电子邮件发送登录验证码时,机器人会在聊天中用“Code for”卡片向你索要,并在看不到验证码的情况下将其填入页面。
    • Telegram 机器人可以参与群聊,群组会显示在 Requests 下,每位成员可以从各自的 Messaging 设置中批准它。
    • 在私信中发送给机器人的语音留言现在会连同音频文件一起附带文字记录。
    • 机器人每天会就未完成的工作签到一次,每个机器人都可以用“Daily check-ins on unfinished work”(未完成工作的每日签到)关闭此功能。
    • 机器人可以编辑或删除自己记忆中的笔记,而不再只能添加新笔记,机器人自身记忆的上限为 4 KB。
    • 机器人可以使用同一应用的每个已连接账户,并通过它的工具选择账户。
    • 机器人浏览器中的页面可以打开新标签页和弹窗,下载的文件会保存在机器人的 Downloads 文件夹中,结果会给出其名称、路径、大小和类型。
    • 在“设置 → 电脑”(Settings → Computer)中,管理员无需编辑环境变量即可选择新电脑运行的位置,任何账户都可以将自己的 Team Computers 发送到 Wuying 云桌面。
    • 自带密钥方案可以按年付费,“Monthly / Yearly”(每月 / 每年)切换开关会显示按年付费能节省多少。
    • 当例行的下一次计划运行时间逾期超过五分钟时,它会显示“Schedule delayed”(计划已延迟),而只向你的机器人发送“stop”或“stop now”即可停止其工作。
    • 桌面应用的菜单、对话框和账户电子邮件现在支持所有应用语言,并且可以在网页端和移动端搜索较长的模型和提供商列表。

    变更

    • 当机器人的记忆大于其可读取的 32 KiB 时,机器人的记忆视图会说明它大致看不到最早部分的多少内容。
    • Boat 电脑上的机器人现在可以获得 Docker 电脑早已具备的页面工具。

    修复

    • 超过 8,000 个字符的 Slack 消息会以原始 Slack 标记的形式到达机器人,而超出新上限的图表规格会报错失败。
    • 当机器人的所有者发送一条只有停止内容的消息时,机器人的工作会停止。
    • 私有例程和技能不会出现在共享频道中。
  10. 0.4.0

    展开

    OpenNavo 编辑

    Rakazo 0.4.0 于 2026-11-01 发布。本次更新新增了 iMessage 和 macOS 语音、无密钥的密钥封装、更多电脑提供商、全聊天范围搜索,以及一系列安全与可靠性修复。

    安全

    • 行级安全的系统绕过现在需要一把只有应用持有的密钥,因此为某个 Space 运行的 SQL 再也无法给自己开放所有 Space 的访问权限。
    • 使用 harden-host.sh 加固的主机现在会丢弃携带 IP 选项的入站 IPv4 TCP 数据包,并关闭多路径 TCP,从而在修复后的内核运行之前阻断通往 CVE-2026-98432 的已知路径。
    • 在 WebSocket 升级过程中途断开连接,不再会让 API 或 Web 服务器为所有用户崩溃。
    • 日志会遮盖更多敏感数据,包括任何 HTTP 认证方案之后凭据、x-api-key 等请求头中的 API 密钥,以及 access_token 等带引号的 JSON 字段。
    • 当有人在电脑上教机器人时,open_path 和 launch_app 会像其他屏幕工具一样被拒绝。
    • Composio 和 Pipedream 连接会记录你批准的确切外部账户,并且只使用该账户。

    新增

    • 通过 Photon 支持 iMessage:设置 PHOTON_PROJECT_ID 和 PHOTON_PROJECT_SECRET 即可将机器人关联到 iMessage 号码,无需公网 URL,自托管部署也可以运行多个 Photon 项目。
    • 在 macOS 上运行的服务器可提供一个无密钥的 macOS 语音提供商,它会用该 Mac 上安装的语音朗读回复。
    • 配置了密钥管理器后,.env 中的密钥(如 ENCRYPTION_KEY 和 BETTER_AUTH_SECRET)可以以被其封装的形式存储,因此 .env 的副本不再包含可用的密钥。
    • 机器人可以搜索当前 space 中属于你自己的所有聊天,而不仅仅是当前所在的聊天,并能打开搜索到的消息,但仅在你直接发起的运行中可用。
    • 登录卡片新增"Save to Vault"开关,默认开启;将其关闭后,登录信息仅针对该次运行和该网站加密保存。
    • 在移动端添加自定义 MCP 服务器、OpenAPI 或 GraphQL 数据源时,你可以选择 bearer token、放在你指定请求头中的 API 密钥,或在浏览器中进行 OAuth。
    • SANDBOX_COMPUTER_MOUNTS(仅限 Docker 电脑)会将宿主机文件夹挂载到每个机器人电脑中,除非条目添加了 rw,否则为只读。
    • MAX_ATTACHMENTS_PER_MESSAGE(1 到 100,默认 4)设置一条消息可容纳的文件数量。
    • 插件作者可以向 Rakazo 市场提交公开的 GitHub 仓库,管理员可在 /admin/plugins 上批准或拒绝提交。
    • boxd 和 Wuying 作为远程电脑提供商加入,移动端和桌面端应用可以使用位于 Cloudflare Access 等访问代理之后的自托管服务器。
    • 在 macOS 桌面应用中,听写和语音通话的收听部分使用 Mac 内置的语音识别。
    • 可以在网页端和移动端的聊天消息中附加 Excel 电子表格(XLS 和 XLSX)。
    • 听写和通话会识别说话者自己使用的西班牙语及其他语言的地区变体,例行时间则使用该语言的时钟。
    • 简体中文和西班牙语的网页应用已完全翻译。
    • 移动端输入框会为每个对话分别保留一份草稿。
    • 在你发起的聊天中提出要求时,机器人可以更改自己的指令、模型、思考级别、朗读和语音,并会显示"Settings updated"卡片,设置更改还可撤销。

    变更

    • 只有在 RAKAZO_ADMIN_EMAILS 中列出的管理员才能添加或编辑 stdio MCP 服务器,机器人只能添加远程服务器。
    • 机器人之间的消息在机器人的聊天中以一行居中的文字显示,例如"Messaged X",点按后会以只读方式打开机器人之间的对话。
    • 你在消息框中标记的机器人会以卡片形式出现在你输入的位置,按 Backspace 会删除整个提及。
    • 导入智能体只能从“设置 → 通用”中的"Import an agent"开始,并且始终会创建一个新的机器人。
    • 无人处理的接管请求会在 30 分钟后结束,而不是一天。
    • 当提供商拒绝主模型的密钥或登录时,机器人会切换到该 Space 的备用模型,而不是失败。
    • Windows 上的桌面应用使用标准的 Windows 标题栏和窗口按钮。

    修复

    • RAKAZO_LOCAL_MAX_TOKENS 现在是向本地模型请求的输出上限,因此更长的回复不再会被截断并重试。
    • 拥有超过二十个 MCP 工具的机器人可通过惰性工具目录访问这些工具,且参数保持完整。
    • stdio MCP 服务器的参数会加密存储,不再返回给客户端。
    • MAX_UPLOAD_SIZE_MB 现在适用于所有 API 路由。
    • "Use my computer" 现在可在 Web 服务器位于 API 前方的部署中成功连接。
    • 当 Docker 宿主机上缺少电脑镜像时,supervisor 会拉取该镜像或构建标准的 rakazo/computer 镜像,而不是让每次启动都失败。
    • 已经在运行的 Boat、E2B、Novita、Daytona 和 CreateOS 电脑会被每次运行复用,而不是重新连接。
  11. 0.3.6

    展开

    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

    展开

    GitHub Release

    What's Changed

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

  13. 0.3.4

    展开

    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

    展开

    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

    展开

    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

    展开

    GitHub Release

    What's Changed

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

  17. 0.1.5

    展开

    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

    展开

    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

    展开

    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

    展开

    GitHub Release

    What's Changed

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

  21. 0.1.0

    展开

    GitHub Release

    What's Changed

    New Contributors

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