Profiles, Paths, and Status

A profile maps your local machine to a user, project, and one or more local paths.

Why Profiles Matter

Profiles tell the CLI:

• which Convex deployment to use
• which API key to use
• which project the commands should target by default
• which local folders belong to the profile

Profile Resolution

The CLI resolves a profile in roughly this order:

• explicit --profile
• OPENSANA_PROFILE
• path match from the current working directory
• configured default profile

Useful Commands

opensana config list
opensana config show
opensana config default work
opensana paths list
opensana paths add /path/to/repo
opensana status

Typical Practice

• keep one profile per project or workstream
• add every worktree path that should resolve to the same profile
• use opensana config show when resolution is unclear