Product changelog

What's new in MaiaChat

Human-reviewed notes covering the capabilities, improvements, fixes, and safety work that matter when you use MaiaChat.

Release notes are curated from the project history. They describe user-visible outcomes and intentionally omit credentials, infrastructure details, and internal-only maintenance noise.
  1. LatestImprovedFixedSafety

    Device Access across paired computers

    Device Access now follows the account and selected paired computer instead of disappearing when you switch models or providers.

    • Device policy now persists across model changes and is shared with explicitly configured agents, including agents using different providers.
    • The selected paired computer, Files scope, filesystem mode, destructive policy, and Full Computer File Access authorisation remain available when you change models.
    • The latest policy migration preserves each account's most recently updated Device Access settings while retaining legacy model rows for audit attribution.
    • Explicitly selected agent models can use shared Device Access; unrequested automatic provider failover remains blocked rather than inheriting computer access.
    • The Device Access UI now uses Paired computer and Full Computer File Access so Windows and Linux users are not presented with Mac-only wording.
    Commit references2ce87cb
  2. NewImprovedFixedSafety

    Safer paired-computer workspaces

    Agent file work now makes the server-versus-computer boundary explicit and keeps project confinement enforced through the entire device path.

    • Choose whether an Agent turn uses the MaiaChat server workspace or a selected paired computer.
    • Selected project folders are confined at both server and bridge layers; missing or outdated bridge support fails closed.
    • Explicit None, Selected Project, and Full Computer File Access modes prevent project selection from silently escalating privileges.
    • Device results render as authoritative operation statuses instead of relying on model-generated success text.
    • Runtime-backed models are routed to the paired computer when their execution contract requires local work, without silently reusing server tools.
    Commit referencesca509ca6a1f6be94cb174
  3. NewImprovedSafety

    Connected provider runtimes

    MaiaChat can now use more provider subscriptions and local runtimes through explicit, bounded, and inspectable connections.

    • Connect supported provider accounts and use subscription-backed chat and coding models without copying provider secrets into ordinary chat settings.
    • Codex subscription chat and workspace-write tasks run through explicit paired-device workflows with bounded permissions.
    • Added supported runtime paths for Grok, Kimi, Qwen, MiniMax, Copilot, and OpenCode with readiness checks and permission ceilings.
    • Hosted LM Studio and LM Studio Link support local model access while keeping local credentials on the paired computer.
    • Provider status, runtime discovery, stale-login handling, executable lookup, and embedded LM Studio reasoning output now fail or render safely.
    Commit referencesc9e58b42af38d2940437f4e2fa4c555513d35cfa46e2a0da74acc6aed85431ac971bd2
  4. NewImprovedSafety

    Reviewable coding workbench

    Long-running coding work is now easier to inspect, control, review, restore, and integrate without losing the surrounding Agent session.

    • Coding sessions record runs, events, changed files, checkpoints, and completion evidence.
    • Review changes with diffs, restore reversible change sets, integrate managed worktrees, or create pull requests without losing session context.
    • Governed specialist delegation and durable run controls make parallel work inspectable, stoppable, and bounded.
    • Verification reports distinguish completed work from unverified, incomplete, or failed outcomes.
    • Coding interoperability supports importing and exporting project work while preserving review and integration evidence.
    Commit referencesec3307eeb7c842a847c7fa941c987fb3006ae00db6aca4f7450d422a
  5. ImprovedFixedSafety

    More predictable autonomous work

    Autonomous runs now respect their execution limits and recover more cleanly when optional verification or hosted shell capabilities are unavailable.

    • Loop presets now respect autonomous API timeouts instead of overrunning their execution budget.
    • Hosted loops complete cleanly when optional shell verification is unavailable, rather than remaining stuck.
    • Simplified chat entry and Agent harness controls make Agent tools and coding work easier to discover.
    • Memory hook and deployment checks stay aligned across chat and autonomous execution paths.
    Commit references282a628d71c16042d7879
  6. NewImprovedSafety

    Safer recovery and interoperability

    MaiaChat gained stronger recovery controls, secure external interoperability, and safer shared-installation administration.

    • Added encrypted portable-backup integrity checks and isolated restore workflows.
    • Durable maintenance and backup-attempt fencing improve recovery after restarts or replica handoffs.
    • Secure MCP interoperability supports scoped keys, idempotent operations, rate limits, and audit controls for external clients.
    • Private GitHub mirroring exports redacted, encrypted state without exposing credentials or sensitive content.
    • Tenant-safe skill curation, review, pinning, rollback, and fail-closed feature rollouts keep shared installations separated.
    Commit referencesa815c54a4012685e0eafcee23ba331edaeff3b7099c09f961
  7. ImprovedFixedSafety

    Device Access follows permission changes

    When you update Device Access during a conversation, MaiaChat now continues the original computer task with the newly available capability.

    • File-creation requests with quoted macOS paths now route to the paired computer instead of becoming an ambiguous server task.
    • Natural follow-ups such as “I gave access to files” retain the original computer context and immediately retry through Device Access.
    • The Agent no longer redirects these requests to Terminal or Google Drive when the paired-device tool is available.
    • Block, Ask, and Allow remain authoritative: the current policy still decides whether a requested change is refused, approved, or performed.
    Commit referencese6b0a90
  8. NewImprovedFixedSafety

    Live Agent activity in chat

    Agent mode now shows what MaiaChat is doing as work progresses, while keeping private prompts, tool inputs, and raw results out of the activity feed.

    • An inline activity timeline shows the current stage, elapsed time, tool count, and completed steps during longer Agent requests.
    • File, browser, search, calculation, and connected-tool activity uses clear fixed labels instead of exposing provider logs or raw tool payloads.
    • Read-only and approval blocks are shown immediately with an explicit confirmation that the protected action was not performed.
    • Useful answer text now streams into chat as it arrives, avoiding a large single update at the end of a long request.
    • Completed activity collapses into a compact summary that can be reopened on desktop or mobile.
    Commit references7300b0a
  9. NewImprovedFixedSafety

    Device Access preview and current AI models

    MaiaChat can now work with a computer you explicitly pair, while fresh chats start with a current multi-provider model catalogue.

    • Pair a macOS, Windows, or Linux computer and choose Browser, Files, Applications, Screen, Terminal, or OS Administrator access.
    • Device policy is shared by one MaiaChat account and its selected paired computer; normal application routes isolate other site users.
    • Hosted users can download the one-file Node.js bridge directly; a full MaiaChat source checkout is no longer required for pairing.
    • Computer requests now route to the paired computer instead of probing the hosted server workspace, including short follow-ups such as “try again.”
    • Completed pairings now appear automatically and are matched to their exact pairing code, with clearer restart and activation instructions inside Device Access.
    • Google and other social-only accounts are no longer asked for a nonexistent MaiaChat password; Google verification can be renewed without manually signing out.
    • Small models now recover safely when they announce a folder-listing tool call without sending its payload, and the verified device result is always shown in chat.
    • Computer-changing actions start blocked, with separate Ask and Allow modes protected by short-lived account reauthentication.
    • Fresh chats use GPT-5.6 Terra, with current OpenAI, Anthropic, Google, xAI, OpenRouter, Ollama, and LM Studio catalogues.
    Device Access is an experimental preview. The companion currently runs manually and does not yet include signed installers, an OS service, or a tray kill switch.
    Commit references693894ad605aa00724473
  10. Improved

    A clearer MaiaChat front door

    The public introduction and signed-in workbench now explain MaiaChat through real outcomes instead of a generic chat screen.

    • Reworked guest and signed-in starting experiences with clearer next actions.
    • Added outcome-led starters for learning, comparing, creating, and automating with AI.
    • Made the Learning Lab and Comparison Lab easier to discover from primary navigation.
    Commit references2a17cb1
  11. NewImproved

    Learning Lab and Comparison Lab

    A guided path now helps people move from basic chat toward documents, agents, coding, loops, and automation using real MaiaChat controls.

    • Added practical lessons, private progress tracking, achievements, and guided capability paths.
    • Added side-by-side model and prompt comparisons with latency, token, and cost context.
    • Introduced organization-managed lessons and clearer onboarding for different experience levels.
    Commit references1d69d2781c70cc
  12. ImprovedSafety

    Stronger Agent mode controls

    Longer-running agent work is more bounded, easier to inspect, and clearer about when it has verified an outcome or stopped.

    • Added clearer loop controls, project context, verification gates, and stop behaviour.
    • Improved parallel subtask coordination for work that benefits from independent specialists.
    • Tightened tool discovery and hosted safety boundaries so disabled capabilities stay unavailable.
    Commit references75ea906
  13. ImprovedFixed

    More reliable local-model agent runs

    Ollama and LM Studio users can run agent loops without cloud keys, with better control over context growth and completion.

    • Made local providers first-class in autonomous model access decisions.
    • Compacted older loop history and bounded large tool results before replaying them to a model.
    • Improved completion checks, recovery, and reporting when verification cannot finish.
    Commit references78f38ba
  14. ImprovedFixedSafety

    Clearer and safer file work

    Agent file tasks now show what changed, stop more predictably, and preserve better recovery points when work fails or is cancelled.

    • Added visible file-change summaries and better progress for local file tasks.
    • Added reliable stop and cancellation handling for active chat and model runs.
    • Improved model failover, message deduplication, scoped file browsing, and mutation checkpoints.
    Commit referencesc070f09add34ed
  15. NewImproved

    Mixture of Agents and in-product help

    Multiple specialist agents can collaborate on one task, with visible roles and practical guidance for choosing the right workflow.

    • Added specialist-agent orchestration for chat, schedules, profiles, and connected channels.
    • Made agent roles visible when configuring and selecting a team.
    • Added practical MaiaChat and Mixture of Agents manuals inside the application.
    Commit references97f66f363eba83
  16. NewSafety

    Plain-language automation with safer hosted defaults

    Common recurring tasks can be created from reusable blueprints and natural-language shortcuts, while hosted installations enforce stricter isolation.

    • Added automation blueprints, suggestions, slash commands, and channel-friendly shortcuts.
    • Improved approval defaults and workspace isolation for hosted deployments.
    • Made the application code read-only in hosted containers while preserving explicit runtime directories.
    Commit references952be7d02af46710c4f2a0ffef2cd5daf63
  17. NewImproved

    Goals, loops, schedules, and memory controls

    MaiaChat gained bounded autonomous work that can pursue a goal, run on a schedule, and remain visible from the normal chat experience.

    • Added standing goals, bounded agent loops, and scheduled autonomous runs.
    • Integrated loop controls into chat instead of hiding them on a separate management page.
    • Improved session recall, self-review controls, and navigation on shorter screens.
    Commit references5355922ce84b208fea594
  18. NewSafety

    Agent workbench foundation

    The Worker Board and safety layers established a more inspectable foundation for longer-running agent work.

    • Added Worker Board triage, artifacts, checkpoints, handoffs, dependencies, and cost caps.
    • Hardened autonomous task concurrency and workspace boundaries around file mutations.
    • Improved reviewed skill discovery, connected-channel actions, and approval-aware workflows.
    Commit references604862b525233ad3868fabc901c70c06204