> ## 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.

# Projects

> Create projects, choose the active project in the CLI, and understand where project-level settings live.

Projects are the top-level workspace in MeshAgent.

A project owns your [rooms](../room_api/overview), [deployed services](../services/deployment/deploy_services), [API keys](./api_keys), [OAuth clients](./oauth), [integrations](./integrations), [routes](./routes), [mailboxes](./mailboxes), [feeds](./feeds), [scheduled tasks](./scheduled_tasks), [billing and usage](./billing), and [membership](./project_roles).

First run `meshagent setup` to sign in, or continue with the current account if you are already signed in, then choose or create a project and activate that project from the CLI. If Codex or Claude are installed, setup can also configure them to use MeshAgent for the active project, reuse or update existing MeshAgent integrations, or remove them later. For the full command surface, see [MeshAgent CLI](../reference/meshagent_cli_help).

By default MeshAgent provides OpenAI and Anthropic access for the project through MeshAgent-managed routing. Use [Integrations](./integrations) only when you want to switch the project to your own provider accounts or override the upstream base URLs.

```bash theme={null}
meshagent setup
```

Use [MeshAgent Accounts](../interfaces/accounts) for membership, billing, and usage. Use [MeshAgent Studio](../interfaces/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:

```bash theme={null}
meshagent project create my-project
```

List the projects you can access:

```bash theme={null}
meshagent project list
```

Switch the active project:

```bash theme={null}
meshagent project activate PROJECT_ID
```

Use interactive selection when you do not want to paste the ID:

```bash theme={null}
meshagent project activate -i
```

Once a project is active, commands for [rooms](../room_api/overview), [services](../services/deployment/deploy_services), [API keys](./api_keys), [routes](./routes), [mailboxes](./mailboxes), [feeds](./feeds), and [scheduled tasks](./scheduled_tasks) use that project by default.

## What lives at the project level

* [Project Roles and Access](./project_roles): members, roles, and room-creation permissions
* [API Keys](./api_keys): project-scoped credentials for automation and backend services
* [OAuth Clients](./oauth): sign users in to your own app with project-owned OAuth clients
* [Integrations](./integrations): project-level model routing, telemetry, and related shared settings
* [Billing and Usage](./billing): project credits, usage, and recharge settings
* [Routes](./routes): map domains and published ports into rooms
* [Mailboxes](./mailboxes): route email into room queues
* [Feeds](./feeds): publish JSON once and deliver it into room storage subscriptions
* [Scheduled Tasks](./scheduled_tasks): enqueue recurring work on a schedule

Secrets are managed through user-owned and service-account-owned APIs covered in [Secrets and Credentials](../secrets/overview). Project-wide service deployment is covered in [Deploy & Manage](../services/deployment/deploy_services). Sessions and room services are covered with [Rooms](../room_api/sessions) and service deployment docs because they are tied to a room runtime rather than project administration alone.

## Related docs

* [MeshAgent Accounts](../interfaces/accounts)
* [MeshAgent Studio](../interfaces/meshagent_studio)
* [Feeds](./feeds)
* [CLI Quickstart](../introduction/cli_quickstart)
* [MeshAgent CLI](../reference/meshagent_cli_help)
* [Secrets and Credentials](../secrets/overview)
* [Sessions](../room_api/sessions)