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

# Companion workspace tabs

> Use the tabs beside the Companion chat to review drafts, mini apps, sequences and test conversations, and to place a test call to a phone agent.

On the Companion page, a tabbed browser sits beside the chat. Whatever Companion builds or edits opens there, so you can review it, ask for changes and publish without leaving the conversation.

> [!NOTE]
>
> The browser is part of the full [Companion page](https://platform.open.cx/companion). From the **Ask Companion…** bar on other pages, selecting a card in a reply takes you to the Companion page and opens the tab there.

## Open and arrange the browser

* **It opens on its own** when Companion starts building a mini app or creates a sequence.
* **Select a card** in a reply (an instruction, the AI Profile, an article, a test conversation) to open that item in a new tab. Selecting the same card again brings its tab back into focus.
* **Open browser** at the top right reopens it after you close it.
* Drag the divider to resize the chat and the browser. **Maximize** gives the browser the full window; **Restore split** brings the chat back.
* **+** opens a new tab. Each tab has its own ✕; closing the last tab closes the browser. **Close browser** hides it and keeps your tabs.

Tabs aren't tied to one chat: they stay open as you switch between chats. Reloading the page brings back only the tab in focus.

If you can't build apps and none are shared with you, the browser appears once a card in a reply opens a tab.

## Tabs you can open

| Tab | Opens from | What you do there |
| - | - | - |
| **New tab** | **+** | Go to **Apps** or **Sequences**, with live counts, or reopen a recent app or sequence. |
| **Apps** | **New tab → Apps** | Browse your apps. **New app** starts a chat to build one (requires **Mini apps** Write). |
| Mini app (its name) | Companion builds it, or you open it from **Apps** | Authors preview, save and publish it; everyone else uses the published app. |
| **Sequences** | **New tab → Sequences** | Browse sequences. **New sequence** starts a chat to build one. Requires **Outbound sequences** Read. |
| Sequence (its name) | Companion creates it, or the card **Open to review who it goes to** | Review the audience, messages and settings. |
| Instruction (its title) | The card **Created as draft** or **N changes suggested** | The AI Instructions editor: accept or reject each suggestion, then publish. |
| **AI profile** | The **AI Profile Draft** card | The same editor, on the AI Profile. |
| Article (its title) | The card **N suggested changes to review** | The article's draft, with its language and publish controls. Requires access to the help center. |
| **Test conversation** | The **Test conversation** card | Watch the AI reply in a test session. Several open at once are named **Test 1**, **Test 2**. |
| **Setup** | The **Setup** button in a chat | The [setup guide](https://docs.open.cx/companion/setup-guide.md). |

## Ask about the tab in front of you

The mini app, sequence or article in focus is attached to your next message, so "why does this app show zero?" or "shorten the second step of this sequence" needs no name or link. Switch tabs to change what Companion works on.

## Test a change in a test conversation

After you change instructions, the AI Profile, training or escalation rules, Companion offers to test the change.

**1. Accept the offer**

Reply yes, or ask for a test yourself, such as "test how the agent handles a late refund".

**2. Open the test conversation**

Companion creates a test contact with your email, starts a session and writes as a customer. Select the **Test conversation** card to watch your AI agent reply.

**3. Review the result**

Companion reads the replies and tells you what worked and what to fix. Ask it to make the fix, then test again.

> [!NOTE]
>
> A test conversation is a real session in your workspace, answered by your AI agent the same way as a customer's, so it also appears in your inbox.

## Place a test call to a phone agent

When Companion creates or changes a phone agent, its reply includes the agent's card. On agents that support calls from the browser, the card shows **Test via web**.

**1. Select Test via web**

A test call opens in a dialog on the Companion page.

**2. Allow your microphone**

Your browser asks for microphone access. Talk to the agent as a caller would.

**3. Tell Companion what you heard**

End the call, then describe what to change. Test calls use the agent's draft, so you can test changes before they're published. See [Phone agent configuration](https://docs.open.cx/phone/agent-config.md#drafts-testing-and-publishing).

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| **You don't have access to sequences. Ask an admin to grant your role access.** | Your role lacks **Outbound sequences** Read | Ask an admin to grant it in **Settings → Roles**. |
| **Microphone access denied. Please allow microphone access and try again.** | The browser blocked the microphone | Allow it in your browser's site settings and start the test again. |
| **Your agent is still being prepared. Wait for preparation to complete before testing.** | The phone agent is still being set up | Wait a moment, then select **Test via web** again. |
| None of the above | | Ask Companion what went wrong, or contact support. |

***

## Related Documentation

> [card] [Companion introduction](https://docs.open.cx/companion/introduction.md)
>
> What Companion does and who can use it.

> [card] [Setup guide](https://docs.open.cx/companion/setup-guide.md)
>
> Train, go live and grow your team.

> [card] [AI Instructions](https://docs.open.cx/ai-instructions/overview.md)
>
> Drafts, publishing and the AI Profile.

> [card] [Mini-app access](https://docs.open.cx/build-agents/mini-apps.md)
>
> Who can edit the apps you build.


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