Fix workspace proxy dropping query parameters

[khaliqgant]

Summary

Fixes the trajectory viewer loading wrong data in cloud mode by preserving query parameters in the workspace proxy.

Root Cause

The workspace proxy route was constructing the target URL without the query string:

// Before (bug):
const targetUrl = `${targetBaseUrl}/api/${proxyPath}`;

This meant requests like:

/api/workspaces/{id}/proxy/trajectory/steps?trajectoryId=traj_xxx

Were forwarded as:

/api/trajectory/steps  (no trajectoryId!)

Without the trajectoryId parameter, the API returns ALL active trajectories (overview) instead of the specific one.

Solution

Preserve the query string when proxying:

const queryString = req.url.includes('?') ? req.url.substring(req.url.indexOf('?')) : '';
const targetUrl = `${targetBaseUrl}/api/${proxyPath}${queryString}`;

Additional Fix

Also includes server-side ID consistency fix:

• getTrajectoryHistory now uses file's internal ID instead of index key
• listTrajectorySteps scans by file ID if index key lookup fails

Test plan

• Deploy to cloud
• Open trajectory panel
• Click on a specific trajectory from history
• Verify correct trajectory steps load (not overview)
• Check server logs for [workspace-proxy] GET .../trajectory/steps?trajectoryId=...

🤖 Generated with Claude Code

[my-senior-dev-pr-review]

🤖 My Senior Dev — Analysis Complete

👤 For @khaliqgant

📁 Expert in src/dashboard/react-components/ (7 edits) • ⚡ 31st PR this month

View your contributor analytics →

---

📊 2 files reviewed • 3 need attention

⚠️ Needs Attention:

• src/cloud/api/workspaces.ts — Significant changes to proxy handling and query parameter processing that could introduce security risks.

---

🚀 Open Interactive Review →

The full interface unlocks features not available in GitHub:

• 💬 AI Chat — Ask questions on any file, get context-aware answers
• 🔍 Smart Hovers — See symbol definitions and usage without leaving the diff
• 📚 Code Archeology — Understand how files evolved over time (/archeology)
• 🎯 Learning Insights — See how this PR compares to similar changes

---

💬 Chat here: @my-senior-dev explain this change — or try @chaos-monkey @security-auditor @optimizer @skeptic @junior-dev

📖 View all 12 personas & slash commands

You can interact with me by mentioning @my-senior-dev in any comment:

In PR comments or on any line of code:

• Ask questions about the code or PR
• Request explanations of specific changes
• Get suggestions for improvements

Slash commands:

• /help — Show all available commands
• /archeology — See the history and evolution of changed files
• /profile — Performance analysis and suggestions
• /expertise — Find who knows this code best
• /personas — List all available AI personas

AI Personas (mention to get their perspective):

Persona	Focus
@chaos-monkey 🐵	Edge cases & failure scenarios
@skeptic 🤨	Challenge assumptions
@optimizer ⚡	Performance & efficiency
@security-auditor 🔒	Security vulnerabilities
@accessibility-advocate ♿	Inclusive design
@junior-dev 🌱	Simple explanations
@tech-debt-collector 💳	Code quality & shortcuts
@ux-champion 🎨	User experience
@devops-engineer 🚀	Deployment & scaling
@documentation-nazi 📚	Documentation gaps
@legacy-whisperer 🏛️	Working with existing code
@test-driven-purist ✅	Testing & TDD

For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews.