Skip to main content
MeshAgent provides three main human-facing interfaces: All three are part of the same MeshAgent account and project model. That means a room is not “in Studio” or “in Powerboards.” It is the same room either way. You might manage the project in Accounts, build and debug it in Studio, then open that same room in Powerboards for a cleaner end-user experience.

​
When to use each interface

MeshAgent Accounts
  • Create or switch projects.
  • Manage project members and roles.
  • View billing, credits, auto-recharge, and usage reports.
  • Docs: MeshAgent Accounts
MeshAgent Studio
  • Create and organize projects and rooms.
  • Build, test, and debug agents, tools, and services.
  • Inspect room sessions with logs, traces, and metrics.
  • Manage services, secrets, webhooks, routes, mailboxes, and other project controls.
  • Docs: MeshAgent Studio
Powerboards
  • Start quickly with built-in agents.
  • Install shared agents and services into rooms.
  • Give non-technical users a focused UI for chat, voice, documents, and files.
  • Depending on room grants, open the developer console and inspect logs, traces, and metrics.
  • Use deployed room experiences without exposing the full project-administration surface by default.
  • Docs: Powerboards

​
How they work together

The usual split looks like this:
  1. Create or choose a project in Accounts, Studio, or the CLI.
  2. Use Accounts for members, billing, and usage.
  3. Use Studio and the CLI to build, test, deploy, and inspect what runs in rooms.
  4. Use Powerboards when you want people to install or use agents in a simpler end-user interface.
This is also why the same room can be useful to different people in different interfaces:
  • an admin can manage members and billing in Accounts
  • a developer can inspect logs and traces in Studio
  • a room member can talk to the agent and work with room files in Powerboards
  • both are working against the same room state, services, documents, and data

​
Next steps