Where Does Daytona Store Its Config and API Token?
Daytona stores CLI profiles and API tokens in config.json inside the OS user-config folder.
Last updated
Daytona resolves its config from the standard user-config dir: ~/.config/daytona on Linux, ~/Library/Application Support/daytona on macOS, %APPDATA%\daytona on Windows. The file is config.json, and daytona login writes the API token into its api token field.
Set DAYTONA_CONFIG_DIR to move the whole thing, which is how people keep separate dev profiles. The file is plain JSON, so backup is a copy. Treat the token like a password: anyone holding your config.json holds your Daytona access.
Where Daytona stores this, by platform
~/.config/daytona/config.json
Full path is config.json inside. DAYTONA_CONFIG_DIR overrides the whole directory for separate profiles.
~/Library/Application Support/daytona/config.json
Same config.json layout. Use Go to Folder in Finder since Library is hidden.
%APPDATA%\daytona\config.json
Same config.json layout under Roaming. DAYTONA_CONFIG_DIR works here too.
Frequently asked questions
Where is my Daytona API token stored?
In config.json under the Daytona config dir, in the api token accessToken field. Regenerate it server-side if it leaks, then log in again to rewrite the file.
Can I keep two Daytona accounts on one machine?
Yes. Point DAYTONA_CONFIG_DIR at a second folder and log in there. Each directory holds its own config.json, profiles, and tokens independently.
Notice an outdated path? Let us know.