Feature: Workspace repo context persistence and branch switching

[wjhrdy]

🚀 Feature Description

Is your feature request related to a problem?
I'm always frustrated when I have to reconfigure repository context every time I start a new workspace, and I can't easily switch branches without re-pulling context.

Describe the solution you'd like
I want repository context to persist across workspace sessions and have a quick way to switch branches in the interface.

💡 Proposed Solution

Detailed Description:

1. Repo Context Persistence: Store repository context associations so that when a new workspace is created, it automatically pulls the same repo context from the previous session.
2. Branch Switching Interface: Add a UI component or command to quickly switch branches without having to re-pull context.

User Experience:

• Users start a new workspace and see their previous repo context already loaded
• Users can switch branches via a dropdown menu or quick command
• Branch changes are reflected immediately in the workspace

API Changes:

• Add workspace context storage/retrieval endpoints
• Add branch switching API endpoint
• Update context management to support branch switching

🎯 Use Cases

Primary Use Case: Developers who work with the same repositories across multiple sessions and need to switch between branches frequently.

User Stories:

• As a developer, I want my workspace to remember my repository context so that I don't have to reconfigure it every time
• As a developer, I want to quickly switch branches in the interface so that I can work on different features without losing my context

🔧 Technical Considerations

Component: vTeam Tools / Workspace Management

Implementation Approach:

• Add workspace context persistence in backend
• Create branch switching UI component in frontend
• Update context pulling logic to support branch changes

Dependencies:

• Backend storage for workspace context
• Frontend UI components for branch selection

Breaking Changes: No

📊 Success Metrics

How will we measure the success of this feature?

• Metric 1: Reduced time to set up workspace (measured in seconds)
• Metric 2: Increased usage of branch switching (tracked via analytics)
• User feedback: Improved developer experience scores

🔄 Alternatives Considered

Alternative 1: Manual context reconfiguration every session - rejected due to poor UX
Alternative 2: CLI-only branch switching - rejected because users want GUI interface
Do nothing: Users continue to face friction in workspace setup and branch management

📋 Additional Context

Screenshots/Mockups: [Add any visual aids]

Related Issues: [Link to related issues or discussions]

External References: [Links to similar features in other IDEs like VS Code]

✅ Acceptance Criteria

• Feature requirements clearly defined
• Technical design reviewed and approved
• Implementation completed and tested
• Documentation updated
• User acceptance testing passed
• Feature flag implemented (if applicable)

🏷️ Labels

• Priority: medium
• Effort: M
• Component: frontend/backend
• Type: enhancement