Where Does Tinybird CLI Store Tokens and Project Files?
Tinybird .tinyb auth file, tinybird.config.json and env files in your project folder.
Last updated
Tinybird keeps auth next to your code, not in your home directory. Running tb login or tb auth writes a .tinyb JSON file in the current project with host, workspace id and token. The CLI searches upward through parent folders until home, so a subdirectory can share the root file with a cwd pointer.
Project shape is the second half. Datasources, pipes and connections live as .datasource, .pipe and .connection files (or TypeScript/Python definitions), listed in tinybird.config.json. SDK projects add .env.local with TINYBIRD_TOKEN and TINYBIRD_URL. Commit the config, never commit .tinyb or .env.local.
Where Tinybird stores this, by platform
.\.tinyb
Auth file in the project root (JSON with host, id, token, tokens map). Add to .gitignore on creation. tinybird.config.json beside it defines include paths and dev_mode branch or local.
./.tinyb
Same file model as Windows. SDK flows read TINYBIRD_TOKEN from .env.local first, then fall back to .tinyb. Use tb auth ls to list regions and tb login to refresh an expired token.
./.tinyb
Same layout on Linux and in CI (where the token should come from secrets, not a checked in file). Local dev container mode uses docker tinybirdco/tinybird-local with dev_mode local in the config.
Frequently asked questions
where is my Tinybird token stored locally
In .tinyb at the project root after tb login, under token and the tokens map keyed by host. SDK projects instead read TINYBIRD_TOKEN from .env.local. Rotate from the dashboard Tokens page, then log in again.
which Tinybird files should I commit to git
Commit tinybird.config.json plus datasources, pipes and connections. Ignore .tinyb and .env.local. In CI export TINYBIRD_TOKEN and TINYBIRD_URL as protected secrets and deploy with tinybird build against those.
Notice an outdated path? Let us know.