> ## Documentation Index
> Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects: Organize Agents & Connections

> Group agents, connections, and rules into projects. Each project has its own dashboard, audit log, and team members.

Projects group your agents, secrets, policy rules, and app connections into isolated workspaces. Every agent in a project automatically sees all secrets in that project, no manual assignment needed.

## Why projects?

Without projects, everything lives in a flat list. Two agents working on different tasks share the same secrets and rules. With projects, you create natural boundaries:

* **payments-app**: Stripe agent + Stripe API key + rate limit rules
* **ai-assistant**: Claude agent + Anthropic key + Gmail connection
* **staging**: test agents with sandbox credentials

Each project is isolated. An agent in `payments-app` can't see secrets in `ai-assistant`.

## Default project

Every OneCLI account starts with a **Default** project. If you only have one use case, you never need to think about projects. Everything goes into Default automatically.

## Creating a project

<Tabs>
  <Tab title="Dashboard">
    Click the project dropdown in the sidebar and select **New project**. Enter a name and you're done.
  </Tab>

  <Tab title="CLI">
    ```bash theme={null}
    onecli projects create --name "payments-app"
    ```
  </Tab>
</Tabs>

## Switching projects

<Tabs>
  <Tab title="Dashboard">
    Use the project dropdown in the sidebar to switch. The Agents, Connections, and Rules pages show only the active project's data.
  </Tab>

  <Tab title="CLI">
    Set a default project for all commands:

    ```bash theme={null}
    onecli config set project payments-app
    ```

    Or pass `--project` to any command:

    ```bash theme={null}
    onecli agents list --project payments-app
    onecli secrets list --project staging
    ```
  </Tab>
</Tabs>

## Renaming a project

<Tabs>
  <Tab title="Dashboard">
    Open the project settings page and update the name in the **Rename** card.
  </Tab>

  <Tab title="CLI">
    ```bash theme={null}
    onecli projects rename --id proj_abc123 --name "new-name"
    ```
  </Tab>
</Tabs>

## Running agents in a project

When you run an agent with `onecli run`, the project is resolved from the agent's identity:

```bash theme={null}
onecli run -- claude
```

The agent belongs to a project. The gateway injects that project's secrets automatically. No `--project` flag needed for `onecli run` because the agent knows which project it's in.

## How access works

Every agent in a project sees **all secrets and app connections** in that project. There's no per-agent secret assignment. The project is the access boundary.

To restrict what an agent can do within a project, use [policy rules](/guides/rules). Rules let you block endpoints, rate-limit operations, or require manual approval per agent.

## Plan limits

|          | Free | Pro (\$25/mo)                 | Team (\$20/user/mo)       |
| -------- | ---- | ----------------------------- | ------------------------- |
| Projects | 1    | 3                             | Unlimited                 |
| Agents   | 2    | 5 included, +\$5/mo per extra | 5/seat, +\$5/mo per extra |
| Secrets  | 10   | Unlimited                     | Unlimited                 |

Limits are pooled across the organization, not per project.