# CLI configuration

Source: /docs/reference/cli/configuration.md

| Setting | Purpose |
| --- | --- |
| `VORTEXIFY_ORG_ID` / `--org-id` | Default organization; the explicit flag overrides the environment variable |
| `VORTEXIFY_TOKEN` | Explicit bearer token overriding stored credentials |
| `vortexify.project.yaml` | Project identity and managed resource paths |

`vortexify login` opens the browser to sign in to Vortexify.

Browser credentials are stored under `~/.vortexify/credentials.json`. Stored OAuth credentials can refresh; an explicitly supplied token cannot be refreshed by the CLI.

`vortexify connector NAME --configure` edits server connection values against the committed schema. `vortexify secret set NAME` prompts for a project secret. Neither requires placing secret values in local resource source.

For React development, use `vortexify dev` from the app directory. It supplies project/organization settings and a same-origin authenticated proxy. The provider and proxy setup are described in [React configuration](/docs/reference/react/configuration).

## Resource configuration and secrets [#resource-configuration-and-secrets]

Keep connector/sync configuration schemas in `config.json`, with actual values stored through platform configuration. Mark secret schema fields with `x-vortexify-secret`. The API exposes separate connector and sync configuration services, which validate values against each resource's committed schema and save a new version. The current CLI has an interactive connector form but no equivalent sync configuration command, and the mounted frontend resource workspace has no dedicated sync form yet. Supply required sync values through `data/syncs/configure` in the configured platform integration before running it.

Create a project secret with `vortexify secret set NAME` and reference it through `Secret("NAME")` in Python. Configuration changes can create saved versions; saving values does not deploy or execute a resource.

## Secret names and connector schemas [#secret-names-and-connector-schemas]

`secret set NAME` creates or replaces a project secret through a hidden prompt. Names begin with a letter or underscore and contain only letters, digits, and underscores. The current command group exposes set; it has no list/read/delete subcommands.

`connector NAME_OR_ID --configure` reads the committed JSON Schema and prompts for configuration values. Save schema edits before configuring them. Required fields, types, and secret annotations belong to `config.json`; actual values remain separate. Use an explicit ID for ambiguous names.

For app development ports and proxy behavior, see [Local development](/docs/reference/cli/local-development). Use each command's help to check its flags; authentication/global options and operation-specific options are separate.