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

> ## Agent Instructions
> Use Stable documentation by default. Honor an explicit Beta request or a URL under /docs/beta/. If the requested version conflicts with the installed CLI package or API origin, clarify the target before writing integration code.
> Pages under /docs/beta/ document Beta; other product pages document Stable. Keep the CLI package, commands, API origin, and credentials within the selected version. State the documentation version in your answer.
> For MCP search, always pass version: Stable or version: Beta. Unfiltered search mixes both versions. For filesystem reads, keep Beta queries under /beta/ and exclude /beta/ from Stable queries; discover paths before reading them.
> The public docs base is https://photon.codes/docs. Convert MCP page paths to public URLs under that base, preserving /beta/ when present. Read https://photon.codes/docs/skill.md for version selection and https://photon.codes/docs/llms.txt for the version indexes.

# OAuth connections

> Inspect OAuth scopes and the applications you have authorized.

`photon account oauth` covers the OAuth side of your account:

* **Connections** are applications *you* have authorized to act on your behalf.
* **Scopes** are the delegated permissions Photon offers.

OAuth clients — applications you build — belong to an organization and are
managed with [`photon org oauth-client`](/docs/beta/cli/organizations/oauth-clients).

[Browse the automatic command reference](/docs/beta/cli/reference/index).

## Scopes

```sh theme={null}
photon account oauth scope list
```

This reads the live scope catalogue from Photon's public
`/v1/auth/oauth/scopes` endpoint. The CLI never exposes Photon's internal scope
contract or calls the upstream identity provider directly.

## Connections

Connections are applications you authorized, not clients you own. Revoking one
removes your grant without deleting the underlying OAuth client.

```sh theme={null}
photon account oauth connection list --limit 25 --order desc
photon account oauth connection list --after connect_app_123
photon account oauth connection revoke connect_app_123 --force
```

Listing is cursor-based rather than token-based: use `--after`, `--before`,
`--limit`, and `--order`, and JSON output includes the server's next and
previous cursors.

Revocation prompts interactively and needs `--force` in scripts. The
application must be authorized again before it can get another token for you.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.