Stop replying with the dead by-key task link - #3
Open
Evillgranny wants to merge 1 commit into
Open
Conversation
The task-creation skill told the agent to answer with /#/issues/<key>, a path the app resolves to nothing — bridgeapp-links and the route map already warn about it. The reply now carries /#/projects/<projectId>/board/<taskId>, the same shape the app's own Copy-link action produces.
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
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.
The task-creation skill told the agent to answer with
/#/issues/<key>— a path the app resolves to nothing, whichbridgeapp-linksand the route map already warn about. The reply example now carries/#/projects/<projectId>/board/<taskId>, the shape the app's own Copy-link action produces, with a line on where both ids come from. The same dead link shape was just fixed in the web app's share prompt (MathAndMagic/bridgeapp-web#1889).