> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alysium.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Browsers and devices

> Understand how Alysium adapts navigation, builder controls and website widgets to browser and screen size, including phone layouts and menus.

Alysium runs in a browser and adapts its navigation and builder to the screen size. A phone can put controls in tabs or a collapsed menu where a desktop shows them beside each other. A website widget can also use more of a phone screen.

A responsive layout does not establish support for every browser or version. If you need confirmation for a particular browser or device, [ask the Alysium team](https://docs.alysium.ai/help/get-help-from-a-person.md).

## Find controls on a smaller screen

1. Open [Home](https://app.alysium.ai/spaces).
2. Open the navigation menu if the sidebar is hidden.
3. Select the destination you need, such as **Library**.

Home opens your current space. To work on an agent, select that agent there. Inside **Build**, use **Settings** or **Profile** for its settings and identity, or **Chat Preview** when the conversation is not beside the settings. Continue with [Test your agent while you build](https://docs.alysium.ai/build-your-agent/test-your-agent-while-you-build.md) to try a question in that preview.

For example, a fictional workshop owner might see the preview beside settings on a laptop and use **Build → Chat Preview** on a narrower screen. That layout change does not mean the agent is missing.

The task and save requirements stay the same when controls move. Design changes still require **Save Changes** before leaving, even if the small preview already looks different. [Preview your widget](https://docs.alysium.ai/design-your-widget/preview-your-widget.md) explains that separate Design task.

[Where things are in Alysium](https://docs.alysium.ai/help/where-things-are-in-alysium.md) distinguishes the main app and visitor navigation.

## Report a device-specific failure

If you cannot use a page or control, contact the team through [Get help from a person](https://docs.alysium.ai/help/get-help-from-a-person.md). Include:

* The device and browser name/version.
* The screen you were using and the action you tried.
* The exact message or result.
* Whether the same task works elsewhere, if you already checked.

These details help distinguish a moved control from a task that fails on that device. They do not require you to test every browser before asking for help.

## If only an installed widget fails

A creator's website widget has separate installation, access and visitor-session requirements. Use [When the widget will not load](https://docs.alysium.ai/widget-visitors/when-the-widget-will-not-load.md) to choose the matching symptom. Changing your app theme or opening another agent does not repair a website installation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.