[FEATURE] Allow Claude Code Web to update conversation branch/PR metadata

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code Web's conversation-to-PR linking is currently immutable once established. The branch/PR metadata is set by the client once at the start of the conversation and cannot be updated, even by Claude Code Web itself. This creates several workflow blockers:

• If I create a PR manually in GitHub instead of using the "Create PR" button, the conversation cannot link to it

<img width="1021" height="249" alt="Image" src="https://github.com/user-attachments/assets/929341d4-0bfb-4d25-aeb8-98101f28f542" />

<img width="1609" height="246" alt="Image" src="https://github.com/user-attachments/assets/00458bd0-0481-446e-b861-8c7f4e6d8743" />

• After merging a PR, I cannot reuse the conversation's built-up context for new branches - it remains locked to the merged PR
• If I ask Claude Code Web to rename a branch, the conversation still references the old name because Claude cannot update its own metadata, permanently disabling "Create PR" and "Open in CLI" buttons

<img width="459" height="120" alt="Image" src="https://github.com/user-attachments/assets/6de78146-d44a-42e1-9e85-8afe703ca1be" />

This means I cannot use the built-in UI buttons to interact with branches/PRs, and status labels (like "merged") become meaningless as they point to the wrong PR. The conversation ends up with with stale, incorrect metadata.

Proposed Solution

Give Claude Code Web a tool to update the conversation's linked branch/PR metadata. Users could request updates via natural language:

• "Link this conversation to PR 123"
• "Update to branch feature/new-name"
• "Point to branch feature/next-iteration"

Claude would update the metadata and the UI would reflect the change.

Alternative Solutions

Current workarounds:

• Start new conversations (loses context)
• Never create PRs manually (too limiting)
• Avoid branch renames (inflexible)
• Use multiple conversations for one logical workstream (fragments context)

None are satisfactory.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

Scenario 1: Manual PR creation

1. Claude creates branch "feature/new-feature"
2. I manually create the PR in GitHub to customize it
3. With this feature: I say "link to PR 123" and can now use the UI buttons

Scenario 2: Continuing work after merge

1. Claude creates a branch and PR, it gets merged
2. I continue in the same conversation and ask Claude to build related enhancements
3. Currently: Claude creates a new branch but the conversation remains linked to the old merged PR
4. With this feature: Claude would automatically update the conversation to link to the new branch it created

Scenario 3: Branch rename

1. Claude creates branch "feature/temp-name"
2. I ask Claude to rename it to "feature/better-name"
3. Currently: Buttons permanently disabled
4. With this feature: Claude updates metadata during the rename

Additional Context

This appears to be a metadata update operation on the conversation object. The capability should allow Claude to programmatically update the branch/PR reference it's tracking.

I think whatever is the easiest solution would be best. This doesn't need to be complex - just give Claude Code Web a tool to update the conversation metadata, since it currently lacks access to fix the problem.

Implementation note: This shouldn't require system prompt changes or cache invalidation. The system prompt could simply inform Claude that branch/PR metadata is mutable via a tool, allowing the actual metadata value to live outside the cached prompt. Claude would then naturally use the tool when needed without breaking existing caching behavior.

Example of Claude Code Web being unable to update the conversations linked branch even though it could rename the branch on Github:

<img width="1147" height="551" alt="Image" src="https://github.com/user-attachments/assets/06f193c1-c74a-451f-bb04-2c55ac505009" />