Product timeline

Raydo Changelog

Key product milestones as Raydo evolves into a local AI Work OS.

Last updated: 2026-05-2523 entries

May 2026

  1. Activation Onboarding, Browser Work Sessions, And Notarized Desktop Delivery

    The first-run experience was upgraded from passive slides into an activation path that helps users set up Quick Entry, the browser extension, workspace mode, runtime health, first-result creation, and the choice between local use and Raydo Cloud. Browser work sessions, visual fallback, local execution boundaries, and macOS notarization also continued to mature.

    User valueThe first launch no longer just explains Raydo. It helps users complete real setup and reach a usable state faster.

  2. App Studio, App Capsule Delivery, And Workflow Editor Progress

    Generated websites, apps, and services started becoming trackable delivery objects instead of temporary Chat outputs. App Capsule, Workflow Editor, connectors, Vercel OAuth groundwork, Knowledge, Chrome extension publishing preparation, and QA all moved forward together, giving generated work a path into preview, refinement, project collection, and final delivery.

    User valueAI-generated app prototypes, web pages, and services can continue to be managed, adjusted, and delivered instead of being scattered inside conversation history.

  3. Native Computer Use And Video Assembly

    Computer Use moved closer to real desktop execution through a native helper, more reliable command handling, and clearer interaction boundaries. Video Assembly and Workflow Canvas run-state refactors also advanced, bringing local tools, media generation, workflow state, and visible progress closer together.

    User valueRaydo can assist with local desktop and media work more reliably, while users can better understand which step a task is currently on.

  4. Computer Use, Knowledge, Quick Entry, And Desktop Packaging

    Computer Use gained permission gates, hot zones, text and click execution, high-DPI coordinate fixes, and safer control paths. Knowledge improved vector search and RAG-oriented capabilities. Quick Entry moved toward inline delivery, while macOS PKG packaging, runtime payloads, and provider runtime sidecars continued to improve.

    User valueRaydo understands local knowledge better, can be invoked quickly from anywhere, and provides a more stable desktop installation and runtime experience.

  5. App Capsule, Code Project, And Provider-Neutral Delivery

    Raydo introduced the App Capsule object layer, detail pages, Code Project routes, Delivery Target Selector, Vercel dry-run, delivery adapter skeletons, and return flows from App Connections back into Project Delivery. The delivery layer began supporting local static preview, provider API, provider CLI, browser handoff, and human-guided steps under one delivery model.

    User valueUsers can move AI-generated apps into code projects and deployment paths without being locked into one framework or cloud platform.

  6. HTML Artifact Salvage, Preview Export, And Quick Entry

    HTML outputs can now be salvaged, previewed, exported, refined, and used as the starting point for App Capsules. PreviewPane continued moving from "view the result" toward "continue improving the result", while Quick Entry became a system-level entry point for capturing and acting without opening the full workspace.

    User valueAI-generated web pages are not just viewable. They can be refined, exported, saved as app prototypes, and followed up from Quick Entry at any time.

  7. Video Creation Flow And Media Capability Projection

    Media Capability Projection V2, video generation offers, prompt-to-image, image-to-video, reference media, starter previews, and early video workflow grammar began converging toward a dedicated Video Creation Flow. The goal is not to replace general Workflow, but to provide a more natural working view for AI video creation.

    User valueUsers can move more naturally from text, images, and references into video clips without needing to understand complex model configuration.

  8. Browser Context, Office Live Artifacts, And Chat Delivery

    The Chrome extension Browser Context Gateway, Office Live Artifact, Video Workbench contract, Raydo Link desktop pairing, Cloud Login disclosure, Chat Office Preview, and connector boundaries advanced together. Chat, browser context, Office artifacts, local preview, and Workflow execution became more tightly connected.

    User valueRaydo can better understand browser context and place documents, decks, spreadsheets, and other results into workflows that can be previewed and continued.

  9. Work Pack, Browser Automation Bridge, And Video Editor Refactor

    Raydo added Work Pack import, Starter Preview, workflow draft creation from imported packs, Browser Automation connection planning, MCP connector improvements, and tool icon assets. Video Editor continued to split Inspector, Timeline, Effects, Transitions, and Canvas Overlays into a more structured media workspace.

    User valueExternal workflows and templates can enter Raydo more easily, where users can turn them into reviewable, editable, and runnable work drafts.

  10. Chat Delivery, Inbox, Projects, And Workspace Shell Tightening

    Chat Delivery, Inbox, Projects, Workflow Run, Role Team, Template Center, local capability settings, Cloud settings, project icons, log summaries, debug telemetry, and the Workspace Shell were tightened together. Results gained clearer destinations, and the gap between pages continued to shrink.

    User valueResults from Chat, pending items, and project delivery are easier to find, so users do not have to guess where the next step lives.

  11. Quick Entry, Live Artifacts, Audio Models, And Workspace Home

    Quick Entry Window, background wake, intent routing, transparent draggable composer, Live Artifacts closure, audio model capability matrices, SenseVoice ASR, project asset collection, and Workspace Home landed together. Raydo started feeling more like an operating cockpit than a collection of pages.

    User valueUsers can invoke Raydo at any time, quickly capture and process tasks, and collect generated results back into projects instead of relying only on the main window.

  12. Web Search, Audio Workspace, Artifact Delivery, And Video Editing MVP

    Web Search, provider registry, runtime artifact routing into workflows, and the Audio connector runtime workspace expanded Raydo's capability boundary. Chat Artifact Delivery became more complete, Artifact Shelf Preview became more stable, and the first Video Editing Workbench MVP landed.

    User valueRaydo can search the web, process audio, preview generated results, and begin supporting more complete video editing work.

  13. Provider Auth, Capability Provenance, And Runtime Boundaries

    Raydo strengthened the control plane with prompt polish runtime commands, Wetoken provider picker, App Connections catalog, Workflow Capability Provenance, Google OAuth PKCE, Notion OAuth, Claude Code local CLI detection, ACP source registry, preflight smoke gates, and `openclaw.json` sidecar boundary enforcement.

    User valueWhen users connect services, choose models, and run capabilities, Raydo can better understand source, permission, and execution boundaries, reducing configuration confusion.

April 2026

  1. App Connections, Media Studio, And Provider Control Plane

    App Connections catalog became the core control surface for provider auth, OAuth, capability routing, cloud device auth, and external integrations. Image Studio, Video Studio, media job runtime, and the broader workspace information architecture were refreshed together.

    User valueUsers can manage external service connections in one place and use image, video, and media generation capabilities more smoothly.

  2. ACP Runtime, Gateway Provisioning, And Scheduled Work

    Raydo added ACP runtime, OpenClaw gateway provisioning, Hermes ACP runtime, Gemini integration, directory context attachments, image model support, scheduled tasks, media generation, and Wetoken device gateway revocation. External runtimes entered the adapter executor system, while Raydo continued to manage events, tools, artifacts, approvals, and delivery outcomes consistently.

    User valueRaydo can connect to more AI runtimes and models while preserving a unified execution experience, result history, and task status.

  3. PreviewPane Becomes A Delivery Surface

    PreviewPane added assistant message preview, HTML, Diff, Office, bundled gateway preview, cloud device auth sync, and a more mature assistant UI. Raydo began treating generated results as objects that can be viewed, edited, saved, shared, and delivered rather than temporary fragments inside a conversation.

    User valueWhether the result is a web page, document, code diff, or Office file, users can preview and handle it directly inside Raydo instead of chasing files elsewhere.

  4. Workflow UI, Desktop Stability, Voice, And Execution Timeline

    Workflow UI, desktop stability, capability upgrades, Companion desktop, slash command menu, reminders, execution timeline, voice reminders, model routing, and built-in skills advanced together, allowing workflows, skills, reminders, and execution state to be understood in one workspace.

    User valueUsers can organize flows, invoke capabilities, inspect progress, and bring reminders and voice assistance into actual work.

  5. Local Adapter, Startup Flow, Built-In Skills, And Packaging

    Raydo added local Codex / Claude chat adapters, Japanese i18n tooling, startup preparation flow, built-in skill templates, service / gateway startup status, macOS DMG, portable packaging, and splash fixes. Startup, health explanation, runtime packaging, and local machine boundaries became more reliable.

    User valueRaydo can start and run more reliably on the user's machine, while connecting to different AI assistants with less environment setup friction.

March 2026

  1. Dashboard, Deliverables, Attachments, And Windows Runtime

    A lighter desktop dashboard, deliverables, approval suggestions, chat folder attachments, dashboard polling fixes, and Windows payload runtime moved Raydo from one-off Chat interaction toward a workspace where work can be tracked, approved, attached, and resumed.

    User valueUsers can manage deliverables, approval suggestions, and attachments in the workspace instead of leaving important results inside one-time conversations.

  2. Runtime Payload And Organization Onboarding

    Runtime payload support, bundled runtime, startup performance monitoring, organization onboarding, template package paths, and project working directory improvements laid the foundation for later execution, packaging, and delivery capabilities.

    User valueRaydo's local runtime became more complete, giving users a more stable base when creating organizations, projects, and templates.

  3. Raydo Identity, CLI, And Desktop Release Path

    The product was officially renamed Raydo. Raydo CLI, desktop app architecture updates, app naming cleanup, and the macOS one-click installer entered the real product surface. This marked the shift from prototype standards to product standards.

    User valueRaydo began behaving like a real product users can install, launch, and rely on, rather than an internal development tool.

  4. Organization, Role, Browser Mode, And Health

    Raydo advanced the Organization, Role, Capability, and Flow model, including company setup drafts, role / company improvements, chat context selection, cloud account support, organization creation, browser-mode read-only gateway, and the health dashboard. The product language shifted from "chat tool" toward "prepare roles, connect capabilities, run flows, and deliver work."

    User valueUsers can manage roles, capabilities, and flows in a way that feels closer to real organizational work instead of operating only around individual conversations.

  5. Release Foundation And Workflow Definition

    Early release work, installer improvements, workflow definition editing, and runtime registry updates started the current product arc: packaging, Workflow structure, runtime awareness, and delivery discipline became first-class concerns. This changelog is a product timeline for users and the public website, not a raw commit log. Entries do not need to map to blog posts yet. The page can first be rendered in a Resend-style changelog format: date, title, and summary, with details pages or linked posts added later if needed.

    User valueRaydo gained the foundation for installation, flow definition, and runtime awareness, setting the stage for the full workspace that followed.

This is a product-facing timeline, not a raw commit log.

Download RaydoRead the docs