Configuration

Most configuration lives in @repo/config (packages/config/src/index.ts) - one typed config constant the backend and every frontend import, so a value changed once propagates everywhere. UI menus are the exception: they're per-app files so each frontend owns its own navigation and banners.

Where configuration lives

The rest of this page covers the central config object; follow the links above for each surface's detail.

How flags gate features

Toggleable features are a discriminated union - { enabled: false } | { enabled: true; ... } - so reading config.X.enabled narrows the type and exposes provider fields only when on.

import { config } from "@repo/config";

if (config.payment.enabled) {
  // config.payment.provider is now available ("stripe" | "polar")
}

Feature flag reference

Each feature page documents the same three things you should reason about: the flag, what hides when off, and the shipped default.

Two flags are bare booleans, not the { enabled } union - read config.apiDocs and config.waitlist directly (no .enabled). config.performanceMonitor.enabled toggles the Hono request logger; fullstack projects generate with it false (Next.js logs requests natively, so the mounted API would double-log) and separate-backend projects with it true - see api. config.observability.sentry is nested one level deeper than the rest and needs both enabled: true and a non-empty dsn before anything is reported; it lives in its own env-free packages/config/src/observability.mjs so the desktop app can read it - see error reporting.

Some capabilities are presence-gated, not boolean: config.analytics, config.support, and config.affiliate activate per provider key you add - see integrations.

The desktop app's AI orchestration gates on config.desktop.agents.enabled, which a desktop project derives from your AI option (not a separate switch). The app always ships that AI source, so flipping the flag on turns the screens back on - but the bundled companion daemon is not runtime-toggleable: a project generated without AI never received apps/companion. Leaving the flag off costs nothing (the staging step skips itself and the app packages fine); it is turning it on that requires re-running the CLI with AI on first - see desktop AI.

Identity, branding, and SEO

Always-present fields drive titles, structured data, and the logo.

CORS origins

config.origins lists the origins allowed to call the backend.

• It reads process.env.TRUSTED_ORIGINS (comma-separated, trimmed), falling back to local dev ports.
• It is passed verbatim to both Hono CORS and Better Auth trustedOrigins with no baseUrl injection.
• Every origin you serve from - including production baseUrl - must be in TRUSTED_ORIGINS. See environment variables.

Routes - never hardcode paths

config.routes.* centralizes shared in-app paths (home, auth, loginRedirect, dashboard, pricing, onboarding, settings, chat, schedules, settingsModels, settingsIntegrations, settingsCompanions, settingsMcp, notifications, admin) so a path change is one edit.

import { config } from "@repo/config";

redirect(config.routes.loginRedirect); // "/dashboard" - survives a path change

Rule: use config.routes.* for any redirect or shared link - never hardcode "/dashboard". Framework-idiomatic route construction (locale prefixing, navigation helpers) lives in data fetching.

AI product - config.ai

config.ai configures the AI product (chat, scheduled runs, capabilities); the AI page covers what it ships. The fields below set who pays for inference and which models are pickable.

One AI sidebar flag is derived, not a config key: aiByok (AI on and byok on - the Models surface) is computed in sidebar-flags.ts, so it follows config.ai automatically and takes no separate setting.

Barrel exports

@repo/config also re-exports named values that are NOT keys on config - import them directly.

Frequently asked questions

How do I turn a feature off? Set its flag to { enabled: false } (or false for waitlist) in packages/config/src/index.ts. Every consumer reads the flag, so UI, routes, and jobs stand down automatically.

Where do the defaults live? In config itself - the shipped values in packages/config/src/index.ts are the defaults. Edit them in place; there is no hidden layer.

Why are provider fields sometimes missing in TypeScript? Toggleable configs are a discriminated union. Provider fields only exist after you narrow with config.X.enabled === true.

Where do secrets and API keys go? Not here. config holds non-secret behavior; keys and credentials live in environment variables.