Thanks for testing
Thank you for testing Unifyr and sharing your ideas and feedback. The Unifyr test phase has ended: sign-in, chats and app features are no longer available. The website remains accessible. This project continues at Ufora.ai.
The latest improvements to UnifyrOS, in plain language.
Thank you for testing Unifyr and sharing your ideas and feedback. The Unifyr test phase has ended: sign-in, chats and app features are no longer available. The website remains accessible. This project continues at Ufora.ai.
Idle update views request the same information less frequently. Active updates continue to refresh promptly, while a hidden legacy update notice no longer sends duplicate requests. Access checks and update holds are preserved.
Supported request flows expose the current question draft for independent review and can classify a request using source evidence. Employee choices are preserved. Execution context helps the agent close a processing step correctly; missing information leads to a draft question without automatic delivery.
Supported inbox and request actions show recognizable steps, such as reading a request, identifying missing information and saving a question draft. Progress does not expose message content or internal identifiers and uses the existing refresh cadence.
Supported connected apps no longer need to fetch their capabilities twice for a read request. Current access and the requested operation remain checked. Knowledge migration shows steps, scheduling, permissions and errors in the selected language: Dutch or English.
Sections such as Context, files and knowledge load when opened, so chat does not need to load them beforehand. A loading error leaves the other tabs usable, while existing drafts are preserved when switching tabs. Invalid read requests to connected apps return actionable feedback without interrupting the conversation.
An open conversation no longer repeatedly fetches unchanged messages in full. New answers, updated files and scheduled results remain visible. Access is checked again on every refresh.
Conversation history, scheduled results and input requests share one fresh access check within a refresh. Every new refresh checks access again. The secure connection to your One retains its own checks.
Confirmed connected-app steps remain individually recognizable when live progress arrives at the same time. The chat uses existing progress data without refreshing more often.
Delivery of an executed and settled result uses its original model agreement, even when the catalog has changed meanwhile. New execution continues to check current access. Specific connected-app steps remain visible alongside live progress.
Completed execution on a One is verified against the final answer and separate AI review. Incomplete tasks show a neutral message without assuming a person stopped them. Content verification and your approval remain separate steps.
Very small precision differences in reported model usage no longer block a new task. Reservations can be safely released when a stopped task is confirmed not to have created a model key. Budget limits remain in force; tasks are not automatically repeated.
New tasks can use pricing from an available model route when the cheapest route is unavailable. The account budget is checked again before starting. Existing tasks keep their agreed price limits.
Availability checks for new tasks no longer wait for unfinished management checks. Brief shared checks reduce repeated work. When a task is confirmed not to have started, its message is preserved with a clear explanation. Budget limits and access checks remain in force.
Model prices retain more decimal places so small amounts are not unintentionally rounded when stored. New tasks continue to check exact prices and existing budget limits.
An administrator can resolve a stopped task’s reservation when the platform explicitly covers the remaining cost risk. Unconfirmed costs are not charged to the customer. Budget limits remain in force and previous tasks are not automatically repeated.
New tasks check whether the selected model is available within current price limits. Changed catalog data is checked again before starting the task. Existing tasks and their limits are preserved.
A progress check that coincides with a task ending no longer causes an error status on its own. AI reviews distinguish content findings from the limitations of text checks. Visual inspection and human approval remain separate steps.
Tool descriptions for assigned app tasks now specify only the assigned record. Existing access checks still validate every call; other records remain unavailable.
A temporarily unavailable check no longer ends an existing app task as though access had been revoked. It grants no additional access or time. Actions still require current permission, and revoked or expired tasks remain blocked.
Separate AI reviews use the connected app’s data contract when saved. The review remains bound to the exact version that was checked. Human approval remains a separate step.
Chat tasks are checked against their original request at completion. Identity, current authority and settled usage remain required after a separate AI review. This does not restart earlier tasks or replace human approval.
The connection service allows an initial load to finish within the existing startup limit. Identity and access checks remain required. Stopped tasks are not restarted.
A hidden chat tab pauses its live connection and periodic checks. Returning to the tab retrieves current progress again. Running tasks continue.
At startup, the connection service verifies that requests reach its own execution version. A leftover process cannot be mistaken for a successful new start. Existing access checks remain in force.
An active One confirms its connection through a shorter route. Progress for connected apps is stored and processed separately with current access checks. Stopped tasks are not restarted and human approval remains required.
Supported connected apps retrieve the required access information in a single check, so sequential requests no longer consume the available check time together. Existing permissions remain enforced; an incomplete check does not grant access.
Discovering available capabilities checks only the connections included in the selected catalog. An access restriction can show its explanation without repeating the same failed check. App actions remain subject to access checks.
Administrators can resolve remaining reservations for verified stopped tasks. New execution continues to wait for confirmed reconciliation. Tasks that never started can be closed safely without running them again.
Supported connected apps show concrete execution steps and their outcomes, including after a task finishes. Connection access checks use fewer sequential database requests while preserving all checks and required human approval.
A preconfigured AI review now uses its own recorded model selection within the same task. Access, budget and required human approval remain enforced. Stopped tasks are not automatically repeated.
Administrators can investigate rejections before a model request using the associated check times. Conversation content and keys are excluded from these diagnostics. Model requests are not automatically repeated.
If an access check expires while its response is being retrieved, an AI step can confirm it once more before execution starts. Revoked access and changed policies still block execution. Model requests are not repeated.
Chat and Apps recognize existing account-bound connections for the selected One. Confirmed intermediate AI responses appear in progress, while access rules and required approvals stay in place.
New chat requests on configured Ones use the managed AI connection. The user, conversation, selected model and shared AI credit remain linked to the same request. A missing acknowledgement does not automatically create a second request.
Actions for one selected app check only the required connection. A slow or unavailable unrelated connection no longer holds up this preparation. Access checks and protection against duplicate changes remain in place.
Supported accounting connections expose bank transactions and receipts to your One. Your One can inspect linked documents and attachments within the selected period. Bank data may require renewed consent in the connected app.
The chat shows when your One is preparing connected apps and context. Independent preparation steps run together. Checks for actual actions and changes remain in place. Long quote PDF titles now wrap without overlapping document details.
New Ones now receive all required desktop connection components during initial setup, preventing installation from getting stuck on a missing file.
In Knowledge, analyze supported exports and choose which conversations, knowledge and instructions to share with One. A saved migration report shows imported items, checks and issues requiring attention. Agents and scheduled tasks remain drafts until you review and publish them; missing source data and apps requiring reconnection are listed separately.
Apps and integrations share the same connection steps. After sign-in, you return to the connection to check its status or select an administration. Workspace administrators can connect available apps directly; platform administrators can disable access per workspace. Account consent, write access and any paid activation remain separate steps.
Notifications show the relevant One’s name and a short preview of the actual answer. The notification list and supported browser push also show its avatar. Sensitive technical content remains protected. The avatar in the iOS push banner requires an additional app update.
Administrators can set up supported accounting and Microsoft connections for the selected workspace with their own app registration. Required accounts, provider permissions and sign-in are still needed. Connection settings and write consent belong to the selected workspace. The Yuki help link opens the instructions for obtaining the webservice key.
Platform administrators can give One instructions directly in the selected workspace again. The management chat uses the administrator’s own identity. Customer inspection remains a separate, audited read-only function.
Platform administrators opening a selected One see its existing customer chat, including connected-app requests, progress and results. The sender and original request remain recognisable. Conversation history stays accessible inside the chat workspace. Supported accounting connections use your own app registration; connection details and tokens remain scoped to the workspace.
Assigned requests from connected apps appear with their sender, progress and result in your conversation with One. You can return to the original request. New accounting connections use existing workspace access and separate write consent; provider configuration and your own account remain required. Draft updates show the current request revision separately from the document version.
An administrator can close an expired first start attempt when One never received permission to execute. Started tasks, documents, confirmed costs and your separate approval retain their own checks.
A computer progress update no longer needs to wait for its connected app. Both retain their own confirmed task duration and access checks. App logos remain recognisable when an external image is unavailable.
Confirmed One progress also keeps the existing task in its connected app current. One can continue from saving to reading documents and separate review. Expired or revoked tasks are not restarted. The heading in app details remains readable against its dark background.
One can prepare the first update of an existing assigned draft using its current revision. Concurrent change checks and your separate approval remain in place.
Larger model streams are processed more compactly while preserving content, tool calls and confirmed usage. Execution hands over more clearly to the separate review. On computers that support viewing, opening the screen leaves One working; input starts only with Take control of screen. First-party and external connections are clearly identified. New direct connections first require administrator configuration. Where a connected app requires approval, your decision remains a separate step on the reviewed version.
Model calls receive an appropriate reservation window within existing task limits. A provably unsent call can be closed without inventing model costs or successful execution. Whenever transmission may have occurred, cost reconciliation remains required.
Administrators can explicitly recover a stalled read-only usage check. The original unknown outcome is retained; tasks are not replayed and unknown model costs are not recorded as confirmed.
Administrators receive more precise technical information when a model response cannot be confirmed, without recording prompts, answers or keys. Unconfirmed outcomes are not automatically replayed or billed as successful.
When an execution check is rejected, administrators can more precisely identify which control step interrupted the task. Sensitive content is not recorded. Existing access checks and your required approval remain in force.
One can record an intermediate question and its matching draft through the connected app. A first answer closed after a stopped execution does not unnecessarily block the queue. Existing changes are preserved; work is never replayed or approved on your behalf.
Deleted Spaces are accessible from navigation again. Read-only administration offers no restore action. One updates requiring shared desktop control are offered and permitted only on computers that have recently confirmed support. Installation and your required approval remain separate steps.
When arguments for discovering or reading connected tools are invalid, One receives the correct input schema before a service is called. This lets One correct an excessive page limit, for example. Connected-service failures and your approval remain separate checks.
Technical diagnostics distinguish cost checks, task permissions and the connected tool. Task contents and connection credentials are excluded; a failed execution remains unconfirmed.
A terminated execution can request its own stop handling, so a failed task does not keep the worker occupied unnecessarily. Actual stopping, cost handling and your approval remain separate checks.
Reasoning models can carry their text reasoning context after an app action. Existing checks of model selection, tenant credits and maximum costs still apply to every follow-up step.
A periodic catalog check does not interrupt separate tasks when prices and model terms remain unchanged. Changes to prices, capabilities or limits are still checked before the next model call.
Separate tasks can use managed model access within existing tenant credits. An uncertain key change keeps execution blocked until the change is confirmed. Managed keys are not displayed in the browser.
Selected reasoning models can be used for text and app actions while retaining their required reasoning. Existing task and tenant credits are checked before execution to cover the cost. AI review does not replace your approval.
A stopped execution no longer keeps the queue occupied unnecessarily once its matching task has also been closed in the connected app. Existing changes are preserved; the task is not automatically repeated or approved.
The connection for separate tasks checks the installed package and existing machine identity. Responses are relayed consistently. An active connection remains separate from execution, AI review and your approval.
The model panel stays fully visible on tablets. Supporting models and the separate review choice remain accessible within the panel.
You can choose a separate model for full review under supporting models. The file list opens reliably after a website update. Administrators gain settings for partner gifts and billing details; availability depends on configured permissions and required information.
Budget and usage are displayed more clearly. The partner portal makes it easier to see when a payout account needs more information. Conversations and administrator access remain bound to the correct user, One and workspace. New execution capabilities become available only after the required checks have been completed.
Platform administrators can configure an app connection for an assigned One without signing in as its employee. Existing app permissions remain in effect and management actions are recorded. Missing or ambiguous employee assignments prevent connection.
Connecting a payout account in the partner portal now works reliably, including when multiple accounts are present.
Approved partners can connect their payout account through the updated onboarding flow. Temporary blockers receive a clear explanation. Support now follows the visual style of your One chat. Notifications for successful tasks can show a short answer preview. On mobile, the keyboard closes after a confirmed send while your chat stays open.
Follow your report’s progress and read its explanation in Support. Administrators can filter cases by progress and view attachments. Chat stays steadier while sending and receiving updates, includes earlier conversations more consistently, and retains reported progress when interrupted. You can prepare an editable follow-up message.
Earlier conversations with the same One now appear together in one continuous timeline. Attachments and scheduled replies remain available. The separate history picker has been removed; existing messages are not deleted or moved. Conversations remain isolated by user and workspace.
Each One opens its main chat, without controls to create extra conversations. Earlier conversations remain accessible through Chat history. On mobile, tapping the name or avatar opens the chat; selecting a One no longer reopens the overview.
Top-ups show only the purchase amount, without additional percentages. Open usage details directly from your plan. Very small usage remains visible as less than 0.1% instead of rounding to 0%.
Budget limits are compared at the same precision used to store them. Periodic checks read the current limit and only change it when needed. A temporary activation limit now shows a specific message instead of an unclear creation error. The message explains that setup should be retried later and that the attempt has not created a new One.
Open your apps from the store icon in the mobile chat overview. App details and connection setup have a clear header and compact controls. Choose read and write permissions during setup; writing requires a separate confirmation. The new One picker presents your Ones as clear icons and opens conversations with one tap.
Open Connect apps directly from the mobile chat overview. App details and setup now have separate steps, with compact forms, accessible confirmations and immediately refreshed connection status. Small screens and permission flows have been improved.
New Ones retrieve their initial configuration through the correct secured service. This fixes a blockage before installation. The machine is only shown as ready after its installation checks pass.
When a change is requested through a read function, One now receives the correct next steps and input fields. Invalid input is distinguished from connection problems. Existing authorization remains valid for the same action; uncertain sends are not automatically repeated.
Approved partners can open the partner portal from their account menu or workspace management. Overview, agreements, referrals and payouts each have their own tab. Connect your payout account through Stripe and follow verification and payouts.
Send additions while One works: messages are included or processed as follow-ups. Your One’s activity is also visible in the menu. Invitations clearly identify the workspace and role; existing users keep their account and switch between their workspaces. App permission confirmation, sign-in and partner management have also been simplified.
Platform administrators viewing another workspace select a workspace member when creating a One. The One is assigned directly to that member.
The website and home-screen icons now use the same blue-to-cyan U on a dark background as the app.
A new integration lets you direct coding agents from One. When read or write permissions are missing, chat explains which permission is required. Administrators can open app permissions directly; other users are referred to their workspace administrator. Connection dialogs avoid showing an incorrect connect action while loading and use more compact settings.
One checks your current app connections first and directs missing mailbox access to the appropriate connection in Unifyr. Mailbox connections are distinguished from website sign-in to avoid unnecessary password and desktop takeover steps.
Icons, labels and arrows stay aligned in mobile connection settings. Profile and app connections share a quiet footer with separate touch targets, stable hover states and support for the collapsed sidebar.
Connection dialogs use recognisable app logos, consistently aligned settings and concise guidance beside each choice. App details, allowed actions and removal follow a fixed order. Blue-to-cyan accents and subtle transitions identify progress and active settings. The layout works on desktop and mobile, including editing and error states.
Voice processes your words with fewer intermediate steps and retrieves answers sooner. Empty recognition while waiting no longer interrupts your answer. Quieter speech is picked up more easily, and a short spoken cue tells you when help is needed in chat. Recognition and audio quality still depend on your microphone and surroundings.
New tasks check current connected apps, including in existing conversations. Integration calls appear alongside progress; successfully consulted apps appear as sources below the answer. A failed check is not presented as a missing connection.
Connection dialogs show one clear step at a time, with compact settings and confirmation after saving. On mobile, the panel uses the full screen. Allowed actions and app details stay accessible without interrupting sign-in.
Connect apps now appears only at the bottom of the chat sidebar, beside your profile. A compact button with recognisable app logos and a soft fade keeps navigation clear, including on mobile.
Integrations handle sign-in expiry information more flexibly so a valid connection is not incorrectly rejected. When integration subscriptions are disabled, unnecessary payment-status messages no longer appear during connection setup.
Find and connect apps from your conversation. When mailbox access is unavailable, your One gives clearer guidance towards the appropriate app connection. Administrators can approve apps and manage connections and allowed actions in a compact dialog. Voice has an organisation-wide setting and clearer help with microphone problems. Partner links, purchase dialogs and withdrawing a scheduled cancellation are easier to use, including on mobile.
Your support reports and their updates are shown within the active workspace. Refining a report and continuing the conversation is clearer. The improvement inbox uses fixed table columns with one case per row. Licence information presents the original texts and attribution without additional technical commentary.
Supported integrations guide administrators through setting up their own app registration, signing in and choosing administrations. App credentials are stored encrypted per organisation. Replacing or removing them ends the existing connection, after which you can sign in again. Available data remains subject to your licence and access permissions at the connected service.
Partners can invite customers through a dedicated landing page and track their results. Customers purchase directly in their workspace. Administrators can configure commission agreements; approved partners connect their payout account through secure verification. Available commission is processed monthly after the holding period.
Drag Ones to save your preferred order. Creation, confirmation and cancellation use consistent dialogs with clearer information. One capacity is shared within your organisation; member limits do not reserve unused slots. Subscription and partner management is clearer, with direct access to terms and open-source notices.
Opening a One or conversation preserves its selection in the URL so refreshing opens the same chat. Notifications has a readable label in the mobile menu. Support shows a single loading state until saved reports are available and respects your reading position.
After a request is declined for insufficient AI credit, chat stays paused across reloads and switching Ones. Top up or upgrade directly. Chat becomes available again when new credit is available. A remaining balance is not displayed as fully used up.
Chat checks your allowance on opening, while in use and after a request ends. Insufficient credit shows a budget notice with top-up and upgrade options without sending another message first. Requests stopped by insufficient credit show a budget notice instead of a generic failure.
When AI credit is insufficient, buy extra credits or choose a plan directly on the website. Compare all plans, including on mobile, and add a payment method during your first payment. After confirmation and updating your available allowance, chat shows that you can continue. Existing paid plans change at the next renewal; extra credits become available after processing. The progress orb subtly changes colour and aligns better with short and long text.
Choose a custom photo while creating a One. For your profile and your One, reposition and zoom the photo with a crop preview before saving. Mobile input dialogs fit the screen more reliably. In Support, refine a proposed report more easily before submitting it.
Conversations, Support, notifications and management each have a top edge matching the active screen. This lets the mobile browser select the appropriate colour again after leaving the dark chat list. Opening and closing a panel also keeps its header tied to the correct screen.
Support helps you clarify a report and shows similar reports within your own organisation, using only explicitly published summaries. Your own reports remain available with status and feedback. On the website, choose and review a plan from Usage. After completing or cancelling payment, you return to the same conversation; usage updates once payment is confirmed.
Computer takeover stays within the visible screen, including in landscape and above the keyboard. Mobile chat options open the selected screen without first showing desktop navigation. Notifications open on their own screen without an overlapping menu. The page colour and top area update together when moving between the chat list, conversation and panels.
Continue chatting immediately after submitting a report. My reports provides an overview with status and feedback for each report. The computer takeover window adapts better to small screens, landscape orientation and the visible space above the keyboard, including when your One asks you to sign in yourself.
Submitted reports remain available in Support, with updates when a ticket is picked up, declined or completed. Administrators can explicitly approve improvements for processing and find declined items in the archive. The thinking orb moves more fluidly, answers appear gently and the mobile top area matches the active screen.
The chat list shows the latest message with its time or date and an unread reply count. Read status is saved per user and conversation, including across your devices. Pending questions and approvals are marked separately as ‘Your reply is needed’. Mobile menu options open the selected screen directly, without a duplicate navigation bar. The composer and top area fit the mobile chat more closely. An existing session opens your workspace without first showing the sign-in form. Support keeps your conversation when closed and accepts pasted images. Management pages check your current access and clearly explain when access is unavailable.
The app and mobile browser now share the same chat list, conversation header, messages and menus. Find conversations, files, skills and model selection in the options menu. Progress and input requests stay readable on small screens. Support retains your ticket proposal during corrections, including longer conversations. If delivery is uncertain, retry the same message without losing your next draft.
On mobile, choose a One from a full chat list. The back button returns to the overview; switch conversations from the chat header. Your profile menu shows management options when your role allows them. Use the permanent Support Orb to report a bug or share an idea, review your text and receive confirmation. Reports reach the team’s improvement inbox.
Weekly and monthly usage and extra budget are shown as percentages. Top-ups show how much monthly budget you add, with purchase prices still visible. Administrators centrally configure plans, storage bundles and reseller pricing. The included AI purchase budget is fully available for OpenRouter usage; funding fees are a separate platform cost. Resellers pay Unifyr and invoice their own customers; cash commissions end. New subscription prices take effect at the next renewal. The current paid period remains unchanged.
Verified AI usage continues to be processed when an individual provider receipt is temporarily unavailable. Missing receipts remain pending and are retried; costs are never estimated. This platform repair does not change the software installed on your One.
A new accounting connection offers guided sign-in, administration selection and separate write permissions. Chat can discover documented operations, with approval for changes. Connection availability is shown clearly; provider app registration must be completed before sign-in can be enabled.
Sign-in immediately shows progress through to opening your workspace. On touch devices, sending a message closes the keyboard. Space menus use neutral surfaces, and chat refers to your agent in plain language. New One installations also handle starting the screen connection more reliably.
Approval cards offer Allow always when supported by the installed runtime. It remembers permission for the offered action type on that One. Radio and checkbox choices now use less space while keeping the entire row clickable.
Chat immediately shows when your request is being prepared, with a subtle orb animation. Completed input requests disappear from the active conversation. Model menus scroll more reliably, and One setup has clearer spacing on mobile and desktop.
Custom photos now appear in a circular crop while your One is being prepared, including setup error messages, on desktop and mobile.
Existing Ones can now use a custom photo as the last option in the orb picker. Preview and replace your image, or switch back to an orb. Your photo appears in the sidebar and conversation.
The mobile sign-in page now extends its dark header colour to the page canvas and supported browser bars from the first load. The header stays accessible while scrolling. Browser appearance may vary by device and settings.
The website now uses the refreshed sign-in design on phones too, with a compact brand header, clearer sign-in methods and consistent styling for code entry and registration.
The model switcher stays within the screen on phones, including landscape orientation. Main and supporting model settings remain scrollable, with the Apply action accessible.
Credit purchases and paid plan upgrades now immediately refresh the AI spending limit. A separate periodic check also refreshes weekly allowances for idle workspaces. If your available credits are exhausted, chat explains when your weekly allowance renews and preserves your draft.
Models made available by the platform administrator are now enabled automatically in existing and new workspaces. Workspace administrators can turn models off; those choices are preserved when models become available again. Creating your first One now also sets up its AI access and explains capacity problems more clearly.
Stripe checkout supports credit purchases and subscriptions, with traceable payment descriptions and protection against duplicate credit grants. Credit balances also show their euro value. Administrators can securely configure production payment credentials. Live checkout requires completed tax settings. The mobile chat header is more compact, with knowledge available in the computer panel.
One usage is now reconciled with provider receipts, including supporting model calls. Missing usage from the current billing period is recovered without duplicate charges. Plan and tokens refreshes automatically and indicates when recent usage is still being processed. Existing Ones receive this improvement without a VM update.
Profile photos now save to private storage while existing photos remain available. Model settings remain scrollable on short screens and in landscape, with Apply always within reach. New workspaces get readable slugs, and One management shows the installed UnifyrOS version in its version column.
Fixed a problem that could prevent a new One from being created. If setup fails, the workspace now explains what happened and that another attempt will follow, instead of continuing to show loading progress.
Live guidance now checks its connection independently of skills synchronization. Delayed synchronization no longer disables guidance during an active task, and connection messages explain what is happening.
Creating a One and switching models in chat now use the same model picker. Navigation, workspace search and sign-in are clearer on desktop and mobile. Task updates disappear when their task ends, and tenant navigation opens the selected section directly.
The chat bar keeps its rounded appearance while sending is paused. During an update, the input explains why you cannot send a message yet, on desktop and mobile.
One briefly reuses capability descriptions on its own machine. This reduces repeated requests within the same task. Every actual action remains checked.
View changesOne can review saved drafts and their PDF in a separate step through connected apps. The report belongs to the reviewed version and does not replace human approval.
View changesOne maintains active processing in connected apps during longer AI steps. Chat makes it clearer which connections and capabilities are being checked.
View changesOne refreshes its skills and Context status correctly. Saved source files can be downloaded, while an unchanged inbox checks for updates less often.
View changesA secure input prompt waits briefly while task checks are renewed. Your password stays outside the agent and ordinary chat.
View changesOne recognizes equivalent task deadlines and waits during startup until the separate browser is ready. Existing access checks and stop conditions remain in place.
View changesOne keeps a task active while you complete isolated input. The prompt is available before the agent continues, while preserving the task deadline and stop button.
View changesOrdinary tasks can create and verify text files in their own task directory on One. Hidden and unchanged chats request history less often.
View changesOne aligns reserved model costs with the allowed response length. Budget checks and unresolved usage safeguards remain in place.
View changesOne can execute model requests directly within a reserved budget and confirm usage in batches. Live steps and files can travel from One to your chat over a protected connection.
View changesOne aligns the waiting periods for receiving and confirming model responses. The original task deadline and stop requests remain in effect.
View changesOne checks required local directories before accepting a request. Exported files are read through the isolated execution service.
View changesOne reduces unnecessary refreshes while waiting. Supported Ones show public intermediate steps and provide exported files through chat.
View changesGives connected-app requests a fixed time limit so expired requests cannot start a new change. Conversations, configuration and files are preserved.
View changesImproves safe closure of an expired request after execution has ended. The request is not run again. Conversations, configuration and files are preserved.
View changesOne can close a confirmed unused start attempt without running the request again. Conversations, configuration and files are preserved.
View changesCorrects a startup issue in the updated agent runtime. Includes managed chat support while preserving conversations, configuration and files.
View changesRestores ordinary chat requests through the managed AI connection and updates the bundled agent runtime.
View changesTechnical failures in interrupted background tasks can be distinguished more clearly.
View changesImproves follow-up steps in tasks using the managed model connection.
View changesOne preserves tool-call identity when continuing a conversation through the managed model connection.
View changesSupported connected-app tasks can use a separate AI review before your approval.
View changesAssigned background tasks can create and update drafts, and ask for missing information before continuing.
View changesScheduled checks can stay quiet without new results and report matches in the original conversation.
View changesFixes a browser startup issue introduced in 2.20 when One prepares a sign-in window.
View changesClearer guidance helps you sign in in the browser One uses for your task.
View changesOne briefly retries temporary connection problems and explains when AI credit is insufficient.
View changesOne describes its work in clear language. You choose when to install this update.
View changesChoose Allow always when an action supports remembered approval on your One.
View changesSwitch your main or supporting model without a lengthy setup step, including the first change after an update.
View changesSwitch your main or supporting model without a lengthy setup step, including the first change after an update.
View changesOne applies only changed model settings, so your next task can start sooner after switching models.
View changesRestores connected-app access on older One installations without reinstalling your environment.
View changesYour One can discover and use permitted write actions in connected apps and MCP integrations, alongside read tools.
View changesClearer descriptions show what your One is doing in the browser. Progress and answer text reach your conversation sooner.
View changesYour One can retrieve data through connected apps and MCP integrations. It checks available connections, tools and relevant skills before choosing another approach.
View changesAdd a clarification while your One is working. Follow whether your update was received, without starting a separate task.
View changesSee the lessons your One has saved, with the time they were last shared. Keep useful knowledge close to the work.
View changesInstall updates directly from the UnifyrOS app after confirming. The update button stays disabled when no update is available. Follow progress while your conversations, skills and files are preserved.
View changesView update status in the UnifyrOS app, refresh it and start an update from the secure update page.
View changesThe familiar desktop background and version display are part of UnifyrOS.
View changesOne UnifyrOS package includes the agent runtime and its required dependencies. Updates preserve conversations, skills and files, and restore the previous version if startup fails.
View changesYour One’s settings show its installed version and available updates.