Skip to main content
Projects are the top-level workspace in MeshAgent. A project owns your rooms, deployed services, API keys, OAuth clients, integrations, routes, mailboxes, scheduled tasks, webhooks, billing and usage, and membership. First run meshagent setup to sign in, choose or create a project, and activate that project from the CLI. For the full command surface, see MeshAgent CLI. 
meshagent setup
Use MeshAgent Accounts for membership, billing, and usage. Use MeshAgent Studio to work inside a project. Both surfaces, along with the CLI, operate on the same underlying project.

​
Manage projects from the CLI

Use meshagent project when you want to create, list, or activate projects from the terminal. Create a project: 
meshagent project create my-project
List the projects you can access: 
meshagent project list
Switch the active project: 
meshagent project activate PROJECT_ID
Use interactive selection when you do not want to paste the ID: 
meshagent project activate -i
Once a project is active, commands for rooms, services, API keys, routes, mailboxes, scheduled tasks, and webhooks use that project by default.

​
What lives at the project level

  • Project Roles and Access: members, roles, and room-creation permissions
  • API Keys: project-scoped credentials for automation and backend services
  • OAuth Clients: sign users in to your own app with project-owned OAuth clients
  • Integrations: project-level model routing, telemetry, and related shared settings
  • Billing and Usage: project credits, usage, and recharge settings
  • Routes: map domains and published ports into rooms
  • Mailboxes: route email into room queues
  • Scheduled Tasks: enqueue recurring work on a schedule
  • Webhooks: send project events to your external systems
Project secrets and project-wide service deployment are covered in Deploy & Manage. Sessions and room services are covered with Rooms and service deployment docs because they are tied to a room runtime rather than project administration alone.