Share pages should support linking to specific messages via query parameter #8344

Open
opened 2026-02-16 18:09:44 -05:00 by yindo · 1 comment
Owner

Originally created by @Zeko369 on GitHub (Feb 2, 2026).

Originally assigned to: @adamdotdevin on GitHub.

Problem:
Currently, when viewing a shared session page (e.g., https://opncd.ai/share/abc123), users can navigate between different messages in the session, but this state is only stored in local component state. There's no way to share a link that opens directly to a specific message.

Desired Behavior:
Allow users to share links to specific messages by supporting a query parameter like ?message=msgId. For example:

  • https://opncd.ai/share/abc123 - opens the first message (current behavior)
  • https://opncd.ai/share/abc123?message=msg_456 - opens directly to message with ID msg_456

This would make it easier to reference specific parts of a conversation when sharing with teammates.

Implementation Notes:
The current implementation uses a SolidJS store to track the active message ID locally. This should be replaced with useSearchParams from @solidjs/router to sync the message ID with the URL query parameters, making it both reactive and shareable.

Originally created by @Zeko369 on GitHub (Feb 2, 2026). Originally assigned to: @adamdotdevin on GitHub. **Problem:** Currently, when viewing a shared session page (e.g., `https://opncd.ai/share/abc123`), users can navigate between different messages in the session, but this state is only stored in local component state. There's no way to share a link that opens directly to a specific message. **Desired Behavior:** Allow users to share links to specific messages by supporting a query parameter like `?message=msgId`. For example: - `https://opncd.ai/share/abc123` - opens the first message (current behavior) - `https://opncd.ai/share/abc123?message=msg_456` - opens directly to message with ID `msg_456` This would make it easier to reference specific parts of a conversation when sharing with teammates. **Implementation Notes:** The current implementation uses a SolidJS store to track the active message ID locally. This should be replaced with `useSearchParams` from `@solidjs/router` to sync the message ID with the URL query parameters, making it both reactive and shareable.
yindo added the web label 2026-02-16 18:09:44 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 2, 2026):

This issue might be a duplicate of or related to existing issues. Please check:

  • #7993: Bad UX on /share website - discusses how message navigation on share pages is only-on-hover with poor affordances
  • #11650: Shared session view fails to represent all messages on its sidebar for long (40+) sessions - related to navigation issues on share pages
  • #10032: /share session only includes the first message + reply - related message visibility issue

Additionally, this issue is also related to:

  • #9241: Content of share session URL is blank - blank share pages
  • #11372: Stale data appears when resharing sessions - share data consistency issues

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 2, 2026): This issue might be a duplicate of or related to existing issues. Please check: - #7993: Bad UX on /share website - discusses how message navigation on share pages is only-on-hover with poor affordances - #11650: Shared session view fails to represent all messages on its sidebar for long (40+) sessions - related to navigation issues on share pages - #10032: /share session only includes the first message + reply - related message visibility issue Additionally, this issue is also related to: - #9241: Content of share session URL is blank - blank share pages - #11372: Stale data appears when resharing sessions - share data consistency issues Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8344