Skip to content

Conversation

@matifali
Copy link
Member

@matifali matifali commented Oct 24, 2025

We only need the single coder_report_task tool for task reporting. Also, you don't need to use all Coder tools when no task reporting is required.

Coder MCP tools are usually helpful when used from an external system rather than within Coder Tasks.

Description

Type of Change

  • New module
  • New template
  • Bug fix
  • Feature/enhancement
  • Documentation
  • Other

Module Information

Path: registry/coder/modules/claude-code
New version: v3.3.1
Breaking change: [ ] Yes [x] No

Testing & Validation

  • Tests pass (bun test)
  • Code formatted (bun fmt)
  • Changes tested locally

Related Issues

We only need the single `report tasks` tool for tasks reporting. Also, you don't need to inject all Coder tools when no task reporting is required. Coder MCP tools are usually useful when used from an external system rather than within Coder Tasks.
@matifali matifali requested a review from johnstcn October 24, 2025 10:46
@matifali matifali self-assigned this Oct 24, 2025
@matifali matifali requested a review from johnstcn October 24, 2025 11:25
matifali and others added 2 commits October 24, 2025 16:32
Moved the `CODER_MCP_ALLOWED_TOOLS` export to the `start.sh` script for task reporting. This change clarifies tool permissions at startup.
@matifali
Copy link
Member Author

@DevelopmentCats can you help here? Mainly testing. I moved the env to start.sh. But it feels weird.

@DevelopmentCats
Copy link
Contributor

@matifali This seems fine to me after testing.

The ai seems to only be aware of the coder_report_task tool as expected.

image
@matifali
Copy link
Member Author

What if we move it back to the install.sh?

@DevelopmentCats
Copy link
Contributor

What if we move it back to the install.sh?

setting up to pull locally so I can test this

@DevelopmentCats
Copy link
Contributor

@matifali

It indeed does not properly set when done in install.sh instead of start.sh

image
@matifali
Copy link
Member Author

@DevelopmentCats can I get an approval then?

@matifali matifali added the version:patch Add to PRs requiring a patch version upgrade label Oct 24, 2025
@github-actions
Copy link

❌ Version Bump Validation Failed

Bump Type: patch

Module versions need to be updated but haven't been bumped yet.

Required Actions:

  1. Run the version bump script locally: ./.github/scripts/version-bump.sh patch
  2. Commit the changes: git add . && git commit -m "chore: bump module versions (patch)"
  3. Push the changes: git push

Script Output:

🔍 Detecting modified modules... Found modules: registry/coder/modules/claude-code 📦 Processing: coder/claude-code Found git tag: release/coder/claude-code/v3.3.0 (v3.3.0) Current version: 3.3.0 New version: 3.3.1 Updating version references for coder/claude-code in registry/coder/modules/claude-code/README.md 🔧 Running formatter to ensure consistent formatting... 📋 Summary: Bump Type: patch Modules Updated: - coder/claude-code: v3.3.0 → v3.3.1 READMEs Updated: - coder/claude-code ✅ Version bump completed successfully! 📝 README files have been updated with new versions. Next steps: 1. Review the changes: git diff 2. Commit the changes: git add . && git commit -m 'chore: bump module versions (patch)' 3. Push the changes: git push 

Please update the module versions and push the changes to continue.

@matifali
Copy link
Member Author

@DevelopmentCats this is a false positive
and suggesting

- boundary_version = "main" + boundary_version = "3.3.1"
@matifali matifali merged commit 0ff3dbc into main Oct 24, 2025
4 of 5 checks passed
@matifali matifali deleted the atif/limit-tools branch October 24, 2025 18:14
@johnstcn
Copy link
Member

post-merge 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

version:patch Add to PRs requiring a patch version upgrade

3 participants