A few things
worth knowing.

An AI workspace that brings your conversation, the work it produces, and supported tools together. You can work with visible artifacts beside the conversation and keep developing the result.

That’s a useful starting point: you already know how to describe a task and discuss a result. Unified’s current setup requires installing and running a host, plus configuring supported AI access. The getting started page explains that commitment.

This site points to the current install-and-configure path. It does not provide a hosted Unified session. Follow the repository’s current setup guide for the available ways to run the app.

The app is open source under the MIT license. Model usage, subscriptions, voice, image generation, hosting, and connected tools can have separate costs and terms. Check the services you configure; one account does not automatically include every capability.

On the host you set up. You open its workspace in a browser. Keep that host running and available for ongoing tasks. A locally running app can still use external AI providers and connected tools.

Voice is an optional capability that depends on configured services, access, and device support. Consult the voice documentation for your setup. You can start with typed conversations.

Supported documents and interactive surfaces have their own controls and editing options. People and agents can use common actions on supported surfaces. Available actions depend on the artifact and installed capabilities.

Accepted work can continue after a call ends while the host remains running and available. Ending a call and stopping a task are different actions. Inspect the task’s status and use its stop controls when needed.

Access depends on your configured tools, connected accounts, files, and permissions. A conversation is not permission to see every application or file on your computer. Review the setup and access granted to each capability.

Unified retains conversation history and supported artifacts on your configured host. You can return to work through the app’s history and artifact views. Storage and recovery depend on your deployment; keep appropriate backups.

They are interactive website examples with illustrative data. They demonstrate possible ways of working, but do not call an AI provider or connect to your files.

Start with the source repository’s documentation and issue tracker. Include what you were trying to do, what happened, and your app version. Review logs before sharing them and omit credentials or private content.