Sign in and select your drive

Use a profile for each account or server connection. Within a profile, save the workspace and drive you use most often, or choose them for one command.

Check your current connection


flashdrive whoami
flashdrive config list
flashdrive workspace list
flashdrive drive list

whoami reports the signed-in account. config list shows saved settings. Check these before uploading or changing files in a different project.

Save defaults or choose once


flashdrive workspace use WORKSPACE_ID
flashdrive drive use DRIVE_ID
flashdrive file list

Use an explicit drive for a single command without changing the saved default:


flashdrive --drive DRIVE_ID file list

For operations that accept folder scope, add --folder FOLDER_ID. A workspace or drive ID comes from its list command; a folder ID comes from flashdrive folder list.

Use another profile

Set up a profile named work for this FlashDrive deployment:

flashdrive --profile work config set base_url 'https://api.flashdrive.space'
flashdrive --profile work login

Select it for later commands:


flashdrive config use work
flashdrive whoami

Or prefix one command with --profile work. Mounted drives retain their original connection; select that same profile and API address when resuming a saved mount.

For a script or a workspace key, create an appropriately scoped API key in the Console and enter it at the hidden prompt:


flashdrive login --api-key
flashdrive whoami

Choose reading/search permissions for a reading task, or write permission when the script needs to change content. Keep credentials in your secret store, outside source files and shell history.

Where the CLI keeps settings and credentials

Settings and profiles are stored in ~/.config/flashdrive. A browser sign-in is kept in your operating system’s credential store. A key entered with login --api-key is saved in that settings folder in a file only your user account can read; prefer environment variables from a secret manager on shared or automated machines.

Browser sign-in needs an operating-system credential store. On a server or headless Linux machine without one, use an API key instead.

Use environment variables

For a script, CI runner, or sandbox, provide the credential in the environment instead of saving it:

Variable	Purpose
`FLASHDRIVE_API_KEY`	API key for this process. Set only one of this and `FLASHDRIVE_ACCESS_TOKEN`.
`FLASHDRIVE_ACCESS_TOKEN`	Short-lived access token, such as a sandbox token.
`FLASHDRIVE_BASE_URL`	API origin. Leave it unset for the production service.
`FLASHDRIVE_PROFILE`	Profile to use when `--profile` is not given.
`FLASHDRIVE_DRIVE`, `FLASHDRIVE_WORKSPACE`	Drive or workspace to use when no flag is given. Overrides the saved choice.
`FLASHDRIVE_CONFIG_DIR`	Alternative settings folder.
`FLASHDRIVE_NO_UPDATE_CHECK`	Set to `1` to skip the automatic update check.

Command-line flags take precedence over environment variables, which take precedence over saved settings. Remove credential variables left by earlier clients with other prefixes; the CLI stops rather than guess which credential to use.

Update or sign out


flashdrive update --check
flashdrive update
flashdrive logout

update --check reports the available release without installing it. update upgrades the CLI using its installation method. logout first stops this profile’s mounted drives and clears their local caches. A mount that cannot be stopped stays mounted, and a cache with unsaved changes is kept; the command reports both. It then removes this profile’s CLI login. It leaves the browser’s Console session signed in.