-
Notifications
You must be signed in to change notification settings - Fork 185
Open
Description
Problem
Users with multiple Letta Cloud projects cannot easily switch between them in the CLI. OAuth tokens are cached per-session and locked to a single project, causing 404 errors when trying to access agents in other projects.
Current behavior
letta loginauthenticates via OAuth but does not offer project selection- The cached token is tied to one project
letta --agent <id>returns 404 for agents in other projects- Project-specific
.letta/config.yamldoes not override the cached OAuth token
Workarounds
- Use
LETTA_API_KEYenv var per project (bypasses OAuth entirely) letta logout+letta logineach time (painful for frequent switching)
Proposed solutions (any of these would help)
--project <name-or-id>flag - Select project at runtime- Project picker during OAuth - Let users choose which project to authenticate to
/projectinteractive command - Switch projects within a session- Multi-profile support - Store multiple OAuth tokens keyed by project
User context
From Discord user audrebytes, who has multiple Letta Cloud projects and wants to use different agents across them without re-authenticating each time.
Discord thread: https://discord.com/channels/1161736243340640419/1475340286111776768
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels