---
schema_version: 1
route: /t/turso.md
tool: "turso"
---

# sincecutoff.com /t/turso — Turso CLI

- name: Turso CLI
- kind: cli
- children: none
- homepage: <https://github.com/tursodatabase/turso-cli>

Changes to the tools coding agents drive, since a model's training cutoff, each linked to its first-party source. Check installed versions and limitations before acting; a cutoff date does not establish what a model knows.
Original editorial content: [Apache 2.0](https://sincecutoff.com/v1/data-license.txt), by [0xPatrick](https://0xpatrick.dev). Preserve applicable license and [NOTICE](https://sincecutoff.com/notice.txt) attribution when redistributing. Third-party source text and examples retain their own rights. [License scope and attribution](https://sincecutoff.com/v1/license.json).
To stay current, read the changes feed: [`/v1/changes.md?tool=turso`](https://sincecutoff.com/v1/changes.md?tool=turso) (or `.json`), adding `since=YYYY-MM-DD` for your training cutoff. Entries for registered children are included; the registry itself is `/v1/tools.json`. How to page and save your place: [llms.txt](https://sincecutoff.com/llms.txt).

### turso auth API tokens support org-wide scopes (2026-10-07)
- slug: turso-auth-api-tokens-support-org-wide-scopes-f9efbe92c4cd
- score: 0.96

How to use it:

When creating an organization-wide token with explicit permissions, run `turso auth api-tokens mint` with `--org` and one or more `--scope` flags, omitting `--group`. Use `group:create`, `group:delete`, or `org:read` only without `--group`; `--full-access` expands to the group-level scope set.

Examples:

```
turso auth api-tokens mint <token-name> --org <organization-slug> --scope group:create --scope group:delete --scope org:read
```

- why_it_matters: Create or review an organization-wide API token with explicit permissions.
- sources: <https://github.com/tursodatabase/turso-cli/releases/tag/v1.0.34>, <https://github.com/tursodatabase/turso-cli/pull/1071>, <https://github.com/tursodatabase/turso-cli/blob/v1.0.34/internal/cmd/auth_createapitokens.go>, <https://github.com/tursodatabase/turso-cli/blob/v1.0.34/internal/turso/apitoken_scope.go>
- gotchas: "Version: v1.0.34"; "<token-name> (required): Name of the API token."; "--org <organization-slug>: Restricts the token to this organization; omitted value defaults to the selected organization."; "--scope <permission>: Repeatable permission scope. Organization-only values: `group:create`, `group:delete`, `org:read`; these are invalid with `--group`."; "--read-only: Shorthand scope preset. Mutually exclusive with `--scope` and `--full-access`."; "--full-access: Shorthand for full access; mutually exclusive with `--scope` and `--read-only`. Its scope set is group-level only."; "--group <group>: Restricts token to a group within `--org`; requires at least one scope and rejects organization-level scopes. Omit for an organization-wide token."; "Prerequisite: The CLI obtains an authenticated Turso client before minting the token; authenticate with `turso auth login` if needed."; "The org-level scopes `group:create`, `group:delete`, and `org:read` are rejected with `--group`."; "The `full-access` label matches the group-level set only, as the platform expands it."; "Docs conflict: Current Turso CLI docs list `--scope` as group-scoped and omit the organization-level scope values, differing from the v1.0.34 release behavior. https://github.com/tursodatabase/turso-docs/blob/main/cli/auth/api-tokens/mint.mdx"

### turso db branch command (2026-03-19)
- slug: turso-db-branch-command-b525594925a7
- score: 0.93

How to use it:

When you need a branch from an existing Turso database, run `turso db branch` with the source and target database names.

Examples:

```
turso db branch <source-database> <target-database>
```

- why_it_matters: Create or manage a database branch while working on a repository’s database changes.
- sources: <https://github.com/tursodatabase/turso-cli/releases/tag/v1.0.18>, <https://github.com/tursodatabase/turso-cli/blob/v1.0.18/README.md>
- gotchas: "Version: v1.0.18"; "<source-database> (required): Name of the existing database to branch from."; "<target-database> (required): Name for the new branch database."; "Prerequisite: Authenticate with `turso auth login` to access an existing account; it obtains an access token."

### turso API tokens can be scoped to an organization (2026-01-29)
- slug: turso-api-tokens-can-be-scoped-to-an-organization-1240fefa108b
- score: 0.95

How to use it:

When minting an API token for an organization, pass its slug with `--org`. The v1.0.17 source does not show `--org` on the list command; see conflicts.

Examples:

```
turso auth api-tokens mint <api-token-name> --org <organization-slug>
```

```
turso auth api-tokens list
```

- why_it_matters: Create or list API tokens scoped to an organization.
- sources: <https://github.com/tursodatabase/turso-cli/releases/tag/v1.0.17>, <https://github.com/tursodatabase/turso-cli/pull/1022>, <https://github.com/tursodatabase/turso-cli/blob/v1.0.17/internal/cmd/auth_createapitokens.go>, <https://github.com/tursodatabase/turso-cli/blob/v1.0.17/internal/cmd/auth_listapitokens.go>, <https://github.com/tursodatabase/turso-cli/blob/v1.0.17/README.md>
- gotchas: "Version: v1.0.17"; "<api-token-name> (required): Name for the token."; "--org <organization-slug>: Restricts the minted token to the organization with this slug."; "Prerequisite: Install the Turso CLI and authenticate with `turso auth login` before using authenticated commands."; "Docs conflict: The release note says `--org` scopes both creation and listing. In v1.0.17 source, mint defines `--org`, while list accepts no arguments and defines no `--org` flag."

### turso db shell connects to local databases by name (2026-01-21)
- slug: turso-db-shell-connects-to-local-databases-by-name-2e43af559b65
- score: 0.93

How to use it:

When the database is running locally, connect by name with `turso db shell sunny-doomsday`; in v1.0.16, the CLI falls back to HTTP for local databases.

Examples:

```
turso db shell sunny-doomsday
```

- why_it_matters: Connect to a local database server by database name while working on a repository.
- before: Specify the full local URL, for example `turso db shell http://sunny-doomsday-local-user.localhost:9090`.
- sources: <https://github.com/tursodatabase/turso-cli/releases/tag/v1.0.16>, <https://github.com/tursodatabase/turso-cli/pull/997>, <https://github.com/tursodatabase/turso-cli/blob/v1.0.16/internal/cmd/db_shell.go>, <https://docs.turso.tech/cli/db/shell>
- gotchas: "Version: v1.0.16"; "database-name (required): Database name or replica URL to connect to."; "sql: Optional SQL command to execute instead of opening an interactive shell."; "Prerequisite: For a database name, the CLI requires the user to be logged in; authenticate with `turso auth login`."; "The fallback applies when the database is found to be running locally."