draft: feat: Add multi-conversation support (multi chats in worktree) #496
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit implements multi-conversation (multi-chat) support per workspace/worktree, allowing users to have multiple independent chat sessions within a single workspace.
Key changes:
- Add ConversationTabs component for tab-based conversation navigation
- Add NewConversationButton with simple + icon (removed fancy provider selection UI)
- Add useConversations hook for conversation state management
- Implement conversation CRUD operations in DatabaseService
- Fix issue where new tabs were starting with shared history by:
- Adding skipResume parameter to prevent resume flags (-c -r, --resume, etc.) on new conversations
- Pass skipResume=true when creating new terminal sessions
- Update PTY manager to conditionally skip provider resumeFlag
UI improvements:
- Simplified new conversation button (no animations, just basic + button)
- Tab styling with proper centering, padding, and close button
- Gradient fade effect on tab titles when hovering to show X button
- Remove provider icon from active tab
Technical details:
- Each conversation has unique terminalId: ${provider}-conv-${conversationId}
- Conversations persist across app restarts via SQLite database
- Tab state stored in localStorage per workspace
- Resume flags are skipped only for new conversations to avoid history sharing
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Resolved conflicts in: - src/main/services/ptyManager.ts (formatting and skipResume default value) - src/main/services/ptyIpc.ts (integrated snapshot-based skipResume logic) The merge brings in: - Environment variable cleanup for Linux AppImage (#485) - New AllChangesDiffModal component - Monaco diff colors and utilities - Improved file changes panel Our skipResume logic now works alongside the snapshot-based logic from main. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Musti7even
changed the title
The previous implementation was breaking history management by always setting skipResume=true for all sessions, including existing ones. The correct behavior is: - New conversations (first time): skipResume is handled by ptyIpc based on snapshot existence - Existing conversations (reopening): ptyIpc checks for snapshot and uses resume flag if present This fix removes the forced skipResume=true from SessionRegistry and lets the intelligent snapshot-based logic in ptyIpc.ts (lines 40-59) handle it. Now: - New conversations without snapshots: resume flag is skipped - Existing conversations with snapshots: resume flag is used to continue where left off 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Musti7even
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Key Features
Technical Changes
UI Components
ConversationTabs: New component for tab-based conversation navigation with:State Management
useConversations: New hook for conversation CRUD operationsDatabase Schema