fix: use correct app slug for status reporting #344
Merged
Conversation
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
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a bug where the wrong app slug was being used for status reporting in the tasks-docker template. The change corrects the CODER_MCP_APP_STATUS_SLUG environment variable from "claude-code" to "ccw" to match the actual app slug.
- Updates the app status slug environment variable to use the correct value
- Addresses a customer-reported issue where status reporting was broken
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
johnstcn
approved these changes
Aug 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
I don't know how long this was broken for, but we had a customer run into this. I also noticed that the MCP seemed to still report "ok" when this was reported with the wrong slug. Ultimately, I'm not sure if this should even be in our example template or if it should be in the module itself, or if its needed at all. Perhaps @35C4n0r, @matifali, or @DevelopmentCats has thoughts on how we can improve this UX overall.
Type of Change