Planning Namespace Settings Project and Database Design
Planning Namespace Settings Project and Database Design
Agent
OpenCode
Model
GPT-5.3 Codex
Shared
Feb 13, 7:29 PM
Messages472
Please create a new project in a new worktree to start working on a new project called "Namespace Settings" to add more namespace config options. Follow project guidelines like others in @docs/projects/
One question is
i'm not sure if the right approach is to create a namespaceSettings table with columns for more configuration options, or just add more columns into namespaces. Settings will be things like
Please recommend an option after studying this repo
Done — I set this up in a fresh worktree and drafted the project plan.
/Users/tarunsachdeva/code/traces-worktrees/feat-namespace-settingsfeat/namespace-settingsdocs/projects/namespace-settings.mdI recommend using a dedicated namespaceSettings table (not adding config columns directly to namespaces), and handling sensitive values like OPENAI_API_KEY in a separate namespaceSecrets table (or secret-manager reference).
Why this is the safer fit for this repo:
api/convex/namespaces.ts:14 serves namespace profile data from namespaces on public paths.api/convex/internal/namespaces.ts:9 returns full namespace docs and is used broadly in auth/session flows.api/convex/services/traces.ts:125 and api/convex/services/traces.ts:166.api/convex/utils/ai.ts:60.So: keep namespaces as identity/profile, move configurable behavior to settings, and isolate secrets from general namespace reads.
If you want, I can now start Part 2 in this worktree and scaffold the schema + internal functions.
Okay, lets start
drop visibility as a setting this will just be a bheaviour inherited from the org
i just want to do openai_api_key / anthropic_api_key etc at namespace level
still wanna do namespaceSettings as a table but how do i set it up mimially