Skip to content
Chatvia Docs

Workspace

Agent surfaces

Get in touch: Ahmad Mayahi, creator of Chatvia, Spectra and Shakomako

Every Chatvia agent has three surfaces at once: a Hosted Chat page, an embeddable Widget, and a Bar trigger. You configure the agent once in Setup, and the same persona, model, sources, and branding apply across all three.

Agents index

TL;DR

You do not pick a surface upfront. A single agent serves all three at the same time. Turn off any surface you don't want exposed on the agent's Deploy page.

Hosted Chat

A standalone chat page, ChatGPT-style: a sidebar with conversation history, a main thread, and an input box at the bottom.

  • Lives at chat.example.com/chat/{agent}. The chat address is generated when the agent is created. With a license key it can also have a custom domain, such as help.yourshop.com.
  • Multiple conversations per chatter.
  • Conversation starters appear on the empty state.
  • Optionally protected, so only signed-in chatters can access it. New agents start protected.

Good for: customer self-service portals, single-agent embeds, "talk to our docs" pages.

Widget

An embeddable chat bubble: a small button on a host page that opens a panel with the conversation.

  • Embedded with a single <script> tag.
  • Its own position, window size, theme (auto, light or dark) and language. The color comes from Branding.
  • Allowed sites: limit which sites may load the widget.
  • Live Chat (on by default): the chatter can hand off to a teammate.
  • Lead capture: the agent can show a form in the chat to collect a name, email or phone.
  • The admin decides, for the whole server, what happens when a visitor removes a chat, and whether the header says "AI assistant". Both are in Settings → Widget.

Good for: marketing sites, support pages, in-app help.

Bar

A search-style trigger that opens a full-screen chat modal, the kind of "ask anything" command bar your team expects from modern apps.

  • Embedded with a single <script> tag, same as the Widget.
  • Configured per agent, like the other two surfaces.
  • Its own Keyboard trigger (⌘K by default) and Placement of the launcher on the page. The placeholder and look come from the shared Info and Branding sections.

Good for: in-app command-bar assistants, internal tools, knowledge lookup from inside your product.

Cross-surface behavior

The Setup page has a tab for each surface (Hosted Chat, Chat Widget, Command Bar) and a list of sections:

  • Shared across all three surfaces: Info, Persona, Starters, Languages, Model, Branding, Settings. Edit once, applies everywhere.
  • Per-surface: Behavior changes with the active tab, so each surface gets its own behavior options. Chat Bubbles shows only on the Chat Widget tab.

Every section and option is explained in The Setup page. The embed code for each surface is on the separate Deploy page.

This means a workspace can ship the same agent on a marketing site (Widget), inside its product (Bar), and as a public help portal (Hosted Chat) without re-authoring the agent three times.

What every agent has

  • A name and chat address.
  • A persona (system instructions). See Persona & instructions.
  • A model assignment. See Model & generation.
  • A branding configuration (colors, avatar, copy). See Appearance & branding.
  • Sources: at least one is required before the agent can answer usefully. See Sources overview.
  • A Playground for testing without going through a public surface.
  • Chatlog, Analytics, and Forms (whose submissions hold the contacts the agent collects).

Chatters with several agents

A chatter can be granted more than one agent. In the Hosted Chat, the account menu at the bottom of the sidebar has My Agents: a list of every agent they can use, to switch between them. One sign-in serves all of them.

Each agent's three surfaces (Hosted Chat, Widget, Bar) are about exposing one agent to the outside world. My Agents is about giving a chatter one way to reach all their agents inside the workspace.

Search guides, settings and commands.