UI

A tour of the bundled UI. Every user sees the same search interface. Developers and administrators also see the platform pages their role allows. The source is at github.com/Search2o/ui.

Layout

The left rail has two stacks. Searches lists the user's conversations, pinned ones first, and is where a search starts. Platform lists the pages that build and run the system, grouped as Agents, Profiles, Guardrails, Operations, Reports, Admin and Billing. A user sees only the groups their role allows. The header carries the breadcrumb, the audit log for administrators, the docs icon for asking the documentation a question, and the message icon for reaching Search2o. Every page has a short description at the top. Every configuration field shows its description on hover, the same text as in the Agent runtime reference.

• How the UI runsThe UI is Search2o’s official interface: a single-page application bundled with the agent server. It uses the server’s REST API and nothing else, and you can…
• Search and conversationsWhere every user starts. Type what you need; the matching agent runs and answers in the same view.
• AgentsThe developer's workspace: private drafts and the published agents that everyone shares.
• ProfilesThe named configurations that agents refer to: LLMs, REST APIs, databases and MCP servers. Each list shows which agents use each profile. A profile that is i…
• GuardrailsWhat agent expressions may do. Developers edit these settings, and they apply to every agent.
• OperationsAdministrator pages for the agent servers and the systems they connect to.
• ReportsFour reports over the retained executions, the last 7 days. The paid service has no such limit. Each report has a date range, a trend chart and a table, and …
• Admin and billingTwo groups. Admin holds Users, Service accounts, Authentication and License, for administrators and the owner. Billing holds Account and Invoices, for the ow…
• Profile and docsThe pages every user has: the profile, the documentation, and messages to Search2o.