getting started

Explore the OpenbirdAI interface

Find Ask, conversation history, integrations, workspace switching and account controls, and learn how the layout behaves on smaller screens.

· OpenbirdAI documentation

The OpenbirdAI dashboard keeps the intelligence workspace, conversation history, connected platforms and account controls inside one shell. This guide maps the main areas so you can find things quickly.

The main areas

The left navigation moves between dashboard areas. The areas that matter most when you are new are:

  • Ask — the OpenFeather conversation surface and the default place to work.
  • Conversations — your Ask history, grouped by recency, searchable, and resumable.
  • Integrations — connect, review and disconnect external accounts.
  • Workspace switcher — changes the active workspace context that answers are drawn from.
  • Plans and usage — credit balance, current plan and request history.

The Ask composer

The composer is the input surface for every question. It accepts typed text and voice input, and the controls above it change with the current state.

  • Plugin or channel selector — chooses which connected context the request should prefer.
  • Model and thinking mode — selects Core, Pro or Deep Strategy where your plan allows it.
  • Send and microphone controls — send the message, or dictate it. While a response is streaming, send becomes a stop control.
While a response is streaming, the composer stays usable for text but hides secondary controls so you can stop the run cleanly.

Conversation history

Every Ask conversation is saved and can be reopened. Opening a conversation restores its message context, so a follow-up behaves like a continuation rather than a new session. Start a new conversation only when you intentionally want a fresh context.

Workspace context

The active workspace determines which connected accounts, memory and team context OpenFeather may use. Switching workspace changes the answers you can get — it does not move data between workspaces. If an answer looks like it is missing data, check the workspace switcher first.

Responsive behaviour

On phones and tablets the navigation and contextual panels collapse into touch-friendly drawers. If a panel looks clipped, close any open drawer, scroll the page back to the top and reload before changing browser zoom. Known rendering issues are tracked in common issues.

Keyboard and accessibility

Every area is reachable by keyboard. The navigation and composer controls are focusable in document order, the plugin selector opens with a standard menu pattern, and focus outlines remain visible against the dark surface. A layout that only works with a mouse is a bug, not a preference.

If a control is unreachable or invisible to a keyboard or screen reader, report it with the page and the assistive technology used.

Common questions

Where do I switch between personal and team workspaces?

Use the workspace switcher in the dashboard. The active workspace is shown persistently so you always know which context answers will use.

Why does the Ask composer look different while a response is streaming?

Secondary controls are hidden so the stop control is unambiguous. The editable text area and voice input remain available.

The sidebar or a panel looks clipped. What should I try?

Close any open drawer, scroll to the top, reload, and confirm browser zoom is at 100% before reporting it as a defect.

Was this page helpful?