ec790a2de6
- Modified addSessionToProject to correctly extract projectKey from virtual workingDirs
- Virtual workingDir format: /virtual/projects/{projectKey}
- Previously was converting slashes to dashes, causing mismatch
- Added console logging to track session-to-project assignment
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
66 lines
2.7 KiB
Markdown
66 lines
2.7 KiB
Markdown
# Project Isolation Bug - Scratchpad
|
|
|
|
## Task Overview
|
|
Fix project isolation bug where ALL sessions appear in every project's left sidebar instead of only that project's sessions.
|
|
|
|
## Files to Modify
|
|
- /home/uroma/obsidian-web-interface/public/claude-ide/project-manager.js (main logic)
|
|
- /home/uroma/obsidian-web-interface/public/claude-ide/chat-enhanced.js (left sidebar)
|
|
|
|
## Root Cause Analysis
|
|
|
|
After analyzing the code:
|
|
|
|
1. **project-manager.js line 365**: `switchProject()` calls `loadChatHistory(project.sessions)` - this passes the correct sessions
|
|
2. **chat-enhanced.js line 52**: `loadChatHistory()` accepts `sessionsToRender` parameter
|
|
3. **BUT** - When `loadChatHistory()` is called without parameters (initial load), it fetches ALL sessions from API
|
|
|
|
The issue: The left sidebar `loadChatHistory` function is being called in multiple places:
|
|
1. Initial page load (no filter) - loads ALL sessions
|
|
2. When switching projects (with filter) - should load only project sessions
|
|
3. When sessions are created/updated
|
|
4. After archiving/unarchiving sessions
|
|
5. After resuming sessions
|
|
|
|
The problem is that `loadChatHistory` caches and reuses all sessions, and the filtering mechanism wasn't working correctly.
|
|
|
|
## Progress
|
|
|
|
### Iteration 1 - Analysis & Initial Fix - COMPLETED ✅
|
|
|
|
**Changes Made:**
|
|
|
|
1. **Modified `loadChatHistory()` in chat-enhanced.js** (lines 71-100):
|
|
- Added check for `window.projectManager.activeProjectId`
|
|
- If active project exists, use `activeProject.sessions` instead of fetching from API
|
|
- This ensures that even when `loadChatHistory()` is called without parameters, it respects the active project
|
|
|
|
2. **Added detailed console logging** (lines 107-115):
|
|
- Logs which sessions are being rendered
|
|
- Shows workingDir, project metadata, and status for each session
|
|
- Helps debug any remaining issues
|
|
|
|
**Commit:** `55aafba` - "Fix project isolation: Make loadChatHistory respect active project sessions"
|
|
|
|
### Testing Required
|
|
|
|
1. Create a new project (e.g., 'roman')
|
|
2. Add a session to 'roman' project
|
|
3. Check if only 'roman' sessions appear in left sidebar
|
|
4. Switch to another project
|
|
5. Verify only that project's sessions appear
|
|
|
|
### Potential Issues to Watch
|
|
|
|
1. **Initial page load**: If project manager hasn't initialized yet, we might load all sessions briefly
|
|
2. **Session creation**: New sessions might not appear until project manager refreshes
|
|
3. **Project switching timing**: Race conditions between loadChatHistory calls
|
|
|
|
### Next Steps
|
|
|
|
1. Test the current fix in browser
|
|
2. If issues remain, may need to:
|
|
- Add loading state to prevent showing wrong sessions during initialization
|
|
- Ensure project manager initializes before loadChatHistory runs
|
|
- Add event-based updates instead of polling
|