> ## Documentation Index > Fetch the complete documentation index at: https://docs.meshagent.com/llms.txt > Use this file to discover all available pages before exploring further. # MeshAgent Studio [MeshAgent Studio](https://studio.meshagent.com) is the browser-based workspace for building, testing, and operating MeshAgent projects. With [MeshAgent Studio](https://studio.meshagent.com) you can: * Create projects and rooms and jump between them. * Inspect [sessions](../room_api/sessions) (logs, traces, metrics) for live debugging. * Create and rotate [API keys](../project_admin/api_keys). * Manage room-scoped and project-scoped [services](../services/deployment/deploy_services). * Manage project registries, [routes](../project_admin/routes), [scheduled tasks](../project_admin/scheduled_tasks), [mailboxes](../project_admin/mailboxes), [feeds](../project_admin/feeds), [integrations](../project_admin/integrations), and [OAuth clients](../project_admin/oauth). * Inspect files, messages, datasets, memory, images, containers, services, and terminals inside a room. * Open [billing](../project_admin/billing) when a project needs more credits. ## Project selector and account menu MeshAgent Studio opens to an active project. Use the dropdown in the upper-left corner to switch between projects you belong to or create a new one. Use the menu in the upper-right corner to sign out. Admins may also see an **Account management** entry that opens [MeshAgent Accounts](./accounts). ## Project navigation The main project sidebar and available actions depend on your project role: * **Everyone**: **Rooms**, [**Feeds**](../project_admin/feeds), [**LLM Proxy**](../agents/routing/llm_proxy) * **Developers and Admins**: [**Sessions**](../room_api/sessions), **Registries**, [**Routes**](../project_admin/routes), [**Scheduled Tasks**](../project_admin/scheduled_tasks), [**Mailboxes**](../project_admin/mailboxes), [**System Services**](../services/deployment/deploy_services) * **Admins and focused project roles**: create and management actions for services, routes, scheduled tasks, mailboxes, and [**OAuth Clients**](../project_admin/oauth) * **Admins only**: [**API Keys**](../project_admin/api_keys), [**Integrations**](../project_admin/integrations) Some project pages are opened contextually instead of living in the permanent sidebar. For example, Studio links to **Billing** when a project is out of credits or after checkout flows. ## Rooms Use rooms to isolate agent runtime environments. Rooms are secure environments where humans and agents can collaborate and share context. Rooms can have their own services, scheduled tasks, routes, mailboxes, and feed subscriptions. From the MeshAgent Studio UI you can: * **Create** a room with **New Room** when your project role allows room creation * Toggle between **My Rooms** and **All Rooms**. **All Rooms** is available to developers and admins. * Open a room from the list to enter its workspace. * Use the room menu to open **Edit**, **Services**, **Scheduled Tasks**, **Mailboxes**, **Feeds**, **Routes**, **Permissions**, or **Delete**. ## Sessions Monitor and debug live and recent room sessions. A session starts when a room starts and stops when the room stops. For the API and data model behind what you see here, see [Sessions](../room_api/sessions). From the **Sessions** page you can: * Create a session with **New Session** * Toggle between **Active Sessions** and **Recent Sessions** * Open a session to inspect **Logs**, **Traces**, and **Metrics** * Stop an active session from the row menu ## Room Workspace (inside a Room) From both **Rooms** and **Sessions** you can open the **Room Workspace**. This is where you develop, test, and debug agents and tools. Opening a room starts or joins a live session. Room-scoped services remain available to the room beyond any single session. ### Layout * **File Browser (left)**: Browse room files. Depending on your permissions, you can create folders and text files, upload and download files, and remove files. * **File Previews (center)**: Open documents, code, tables, markdown notes, memory viewers, and other room resources in tabs. * **Messaging (right)**: Chat with human and agent participants in the room. * **Developer Console (bottom)**: Live debugging tabs for **Logs**, **Traces**, **Metrics**, **Images**, **Containers**, **Services**, and **Terminal**. The container-related tabs serve different jobs: * **Images** shows images already pulled or built for the room runtime. * **Containers** shows running and stopped room containers, along with logs and runtime actions. ### Room Menu (upper left) * **Leave Room**: Exit the room and return to the project view * **Call Agent**: Invoke a room-connected agent directly * **Toolkits**: View available tools and toolkits in the room and invoke them directly * **Queues**: View room queues and the number of messages in each queue * **Dataset**: Open the room dataset and work with tables * **Memory**: Open room memory viewers * **Room Services**: View, add, remove, and update services tied to this room * **Scheduled Tasks**: Manage tasks that enqueue work on a schedule * **Mailboxes**: Manage mailboxes that route into this room * **Feeds**: Manage visible feeds and storage subscriptions for this room * **Routes**: Manage domains and ports that route into this room * **Keychain**: Review and manage user-owned credentials as the new secret workflows roll out * **View Toggles**: Show/hide File Browser, File Previews, Messaging, and Developer Console ## API Keys Issue and rotate project-scoped credentials used by automations, CI, and services that call MeshAgent APIs. See [API Keys](../project_admin/api_keys) for the full reference. You can: * Create, relabel, and revoke keys * Track when a key was created for audit and rotation ## System Services Services turn your agents, toolkits, or connectors into reusable building blocks. Project-wide services are managed from the **System Services** page. Room-scoped services are managed on the room itself, either from the room list or from inside the **Room Workspace**. For deployment flows and service packaging, see [Service YAML](../services/deployment/deploy_services). From **System Services** you can: * Inspect what’s deployed to the project * Create, update, or remove deployed services * Change the **Room Server Version** if you need to pin a project to a specific version of MeshAgent or return to `latest` Service inspection is available to users with service inventory access. Creating services requires the project `service_creator` role, and updating or deleting services requires `service_manager`. ## Integrations Bring your own model routing and observability settings. See [Integrations](../project_admin/integrations) for the full configuration reference: **LLM provider settings** * Use MeshAgent-managed routing by default, or configure your own provider credentials and base URLs for providers such as OpenAI and Anthropic. * Services, coding agents, and compatible SDK clients can use [MeshAgent LLM Proxy](../agents/routing/llm_proxy) to route requests through those project settings. **Telemetry (OTEL)** * Export room/runtime metrics and traces by providing an OTEL endpoint and optional bearer token. * Optionally configure an OTEL filter endpoint before MeshAgent processes and forwards telemetry. ## LLM Proxy Open [**LLM Proxy**](../agents/routing/llm_proxy) from the project navigation when you want the project's provider-compatible base URLs or want to inspect routed usage for your own account. From this page you can: * open the **About** tab to copy the OpenAI-compatible and Anthropic-compatible base URLs * open the **My Usage** tab to inspect your routed LLM usage for the current project * open the main LLM Proxy docs from the built-in **Read docs** link ## OAuth Create OAuth2/OIDC clients to enable MeshAgent to sign in for your apps. A client is used to identify a single app to MeshAgent's OAuth servers. OAuth client actions require the project OAuth client inventory, creator, or manager roles. See [OAuth Clients](../project_admin/oauth) for the full setup flow. * Register a client with redirect URIs, scopes, grant types, and response types. * Create, edit, and delete clients from the project. ## Routes Use **Routes** to map project or room traffic to the right room. See [Routes](../project_admin/routes) for the full route model and setup details. From this page you can inspect routes, and users with route creator or manager access can create, edit, refresh, and delete routes, including the domain and port that should route into a room. ## Scheduled Tasks Use **Scheduled Tasks** to enqueue work on a schedule. See [Scheduled Tasks](../project_admin/scheduled_tasks) for the full behavior and examples. From this page you can inspect scheduled tasks, and users with scheduled task creator or manager access can create tasks at the project or room level, edit schedules, toggle tasks on or off, and delete tasks that are no longer needed. ## Mailboxes Provision room-scoped mailboxes that agents can read from or send through. See [Mailboxes](../project_admin/mailboxes) for the full setup flow: * Inspect mailboxes, or create mailboxes and assign them to rooms when you have mailbox creator or manager access * Map incoming mail to queues so worker agents can process it asynchronously * Edit or delete mailboxes when your routing changes ## Feeds Use **Feeds** to manage project feeds and room storage subscriptions. See [Feeds](../project_admin/feeds) for the full model and examples: * Inspect feeds, or create feeds and choose visibility, schema validation, and paused state when you have feed creator access * Publish a single JSON message or import a JSONL file into a feed * Open a room-scoped **Feeds...** view to manage which feed subscriptions deliver into that room * Inspect subscriptions that write feed batches into room storage paths ## Billing Billing is available through direct Studio flows when a project needs attention, but the underlying billing surface lives in [MeshAgent Accounts](./accounts). From the billing page you can: * View current credit balance and spend * Purchase credits * Configure automatic recharge ## Next Steps * Follow the [Quickstart](../introduction/cli_quickstart) to create your first project, room, and agent from the CLI. * When you are ready for production, read [Service YAML](../services/deployment/deploy_services) to write and deploy service manifests.