Projects and sessions

Use multiple projects in the sidebar when you actively switch between repositories or workstreams.

• Add projects from the sidebar to keep separate codebases active in one app workspace.
• Rename project display names for clarity when folder names collide.
• Keep only active projects pinned in your current workspace to reduce switching friction.

Treat sessions as focused execution threads. One larger objective per session keeps context strong and response quality stable.

• Create a new session for each major task or milestone.
• Avoid mixing unrelated features in one long-running session.
• Pin high-priority sessions and close/archive completed ones.

• Project level: one project per repo or deployment unit.
• Session level: one session per major task (feature, bugfix, migration, release prep).
• Milestone boundary: after completion, start a fresh session to avoid context rot and unnecessary token spend.