Project Configuration

An app needs no Telbase configuration file. It is registered with telbase apps create, and its settings live with Telbase and its provider. This page lists the files in your app's folder that Telbase and your agent use, and how the CLI picks the app a command acts on.

Which app a command acts on

Commands that act on one app (db, env, domain, logs, deploys, rollback, the service controls) take the app from, in order:

--project <app>;
a .telbase/project.json in the folder, which the earlier CLI wrote there (nothing writes it now; delete it to stop it applying);
the current project, set with telbase projects switch <name>.

bash

telbase apps list                # the organization's apps
telbase logs --project my-app
telbase projects switch my-app   # then commands without --project use it

Files in your app's folder

.vercel/project.json — written by telbase apps create --provider vercel. It links the directory to the app, and telbase vercel deploy deploys from that directory.
.vercelignore and .gcloudignore — the files a deploy leaves out. The skills have the agent write one when the folder holds files that are not part of the app (agent folders, .env files, local data).
.claude/skills/, .cursor/skills/, .windsurf/skills/, .agents/skills/ — the Telbase skills, written by telbase skill install.

Secrets stay out of files

Connection strings and storage keys are set on the provider from a command, never written to a file. See Environment Variables.

Settings

telbase config shows the current project's settings: name, slug, region, framework and status.

bash

telbase config list
telbase config get region

An app's URL, deploy command, database commands and sign-in state:

bash

telbase apps info my-app

Next Steps

Full-Stack & Monorepos — apps with several services
CLI Reference — every command
Supported Frameworks — where each kind of app runs