The Channels rewrite is finally done
Channels is the part of Onevium that bridges your AI sessions into the messaging platforms a team actually lives in — DingTalk today, Feishu and Discord on the same shape. The original UI grew organically from a single bridge into a multi-bridge surface, and it showed: nested dialogs to edit a single field, separate creation flows for bots and team channels, mismatched dialog styles between the channels list and the rest of the app.
v1.1.2 ships the redesign that closes that gap. The list and detail views now mirror Automations one-to-one, so moving between the two surfaces feels like the same product. Every field on a channel is editable inline — name, working directory, credentials, member assignments — without opening a dialog. Creating a channel is a single flow with explicit step labels: register credentials, choose bot or team, start receiving chats. No more guessing whether you need to click 'Add bot' or 'Add team' first.
Underneath the UI, two reliability fixes that have been quietly biting power users: DingTalk @-mentions now resolve to real display names instead of internal staff IDs, and an AI Card streaming failure no longer drops the reply on the floor — the bridge holds the response and delivers it as a fallback message. Running bridges show a small indicator in the sidebar so you can see at a glance which sessions are live.
The Browser is now a browser
v1.1 introduced the Sandbox Browser as a popover preview surface — open any URL inside the app, pin it, click an element to capture a selector. It was good for short loops. It was not good for anything that required logging in, or holding a session across launches, or treating the in-app browser the way you treat your default browser.
v1.1.2 makes that jump. The browser now runs on a persistent profile: cookies, history, and sessions survive across launches, so signing into your dashboard once means it stays signed in. ⌘ / Ctrl + click on any Markdown link in chat opens it inside the in-app browser with a clear hover badge — plain clicks still go to your default browser, so we are not hijacking the default behavior. Auto-fit width, navigation shortcuts, a dialog clipping fix, and `file://` support for managed temp HTML round it out.
The combination matters. A real browser pinned to your AI session, with persistent state, lets the agent operate against pages that require auth — the same pages you actually work against. The loop tightens from 'open this URL in your browser, screenshot it, paste it back' to 'open it inline, click an element, ask the agent to fix the spacing.'
Automations v2 ships in full
Automations is Onevium's scheduled-task surface — recurring AI workflows that run without you. The first version landed last cycle and was usable but unpolished; v1.1.2 ships the 1:1 redesign that brings spacing, dialogs, and the run history list in line with the rest of the app, and retires the legacy v1 path completely.
If you have been on the fence about scheduling anything because the surface felt like an early prototype, this is the version to revisit it on.
Smaller wins worth calling out
Three more changes in this release that punch above their size:
- Proxy: Global mode now supports authenticated proxies (HTTP Basic auth), shows the real outbound IP for verification, and routes the embedded terminal through proxy-bridge so nothing leaks around the global setting.
- Platform-aware keyboard shortcuts: ⌘ on macOS, Ctrl on Windows/Linux, with the platform-native modifier order across menus, tooltips, and the inspector. No more cross-platform shortcut translation in your head.
- Multi-column split view: active column focus is distinguished by font weight, opacity, and a unified hairline instead of background tints. Working in three columns no longer looks like a Christmas tree.
How to get it
v1.1.2 is available now for macOS (Apple Silicon and Intel) and Windows (x64). Download the installer from the Releases page or update from inside the app — your data, sessions, and settings carry over untouched.
If you are jumping in fresh, the channels redesign and the persistent-profile browser are the two surfaces to try first. Both shape what 'AI workflow desktop' means for the next phase of the product.