Practical tools for the things you already do on the web. Here is what you can use, and what each feature needs.
Arrange several web pages in one window. Resize the layout, move panes between groups, and focus or minimize a pane without losing the rest of your work.
Read documentation beside your editor. Compare sources without repeatedly switching tabs.
Desktop browserKeep layouts, tab groups and open URLs together in named workspaces. Switch projects, save a local backup, and import an exported workspace when you need it again.
Keep a daily dashboard separate from a research project. Export a backup before making a major change.
Local saving · Account needed for cloud syncAssign a separate storage partition to a group or pane. Each partition keeps its own cookies and website storage, so different accounts can stay signed in side by side.
Open a work account and a personal account on the same service. A partition is account separation, not a guarantee of anonymity.
Desktop browser · Quotas depend on accountCapture selected text or page content into notes, retain the source title and URL, and work with Markdown alongside your pages.
Collect useful passages while reading. Keep enough source context to find the original page later.
Desktop browserCapture a page with the screenshot tools. Share a URL, tab group or workspace through the account sharing flow; recipients can open supported shared content in Yuki.
Send the references for a project, or capture what a page looked like. A shared workspace does not transfer your website login cookies.
Screenshots locally · Account needed for sharingOpen an AI conversation beside your browsing. Configure an available model or provider in settings before using it; provider availability and data handling depend on that configuration.
Ask questions while keeping the page in view. Check generated answers against the original source.
Requires AI configurationCompanion connects paired devices with Yuki. The current implementation includes pairing and file transfer; it requires compatible Companion and local service versions, and a working connection.
Use the Companion Hub to manage a paired device. Check the build you have before relying on a device workflow.
Version-dependent · Device setup requiredLayouts and project context are different from website sessions, saved passwords and every other kind of browser data. Do not assume all of those move together.
You can start browsing locally. Cloud sync, account sharing and connected-device features need the corresponding service and account access.
Desktop packages, AI providers and Companion versions have their own requirements. The download page lists the packages actually published.
