generated from amazon-archives/__template_Custom
-
Notifications
You must be signed in to change notification settings - Fork 379
Sync prod with main #2661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Sync prod with main #2661
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
* feat: add github action for release notification
* changes prompt list result to be sent over via messenger * changes tool manager orchestrator tasks to keep prompts * changes mpsc to broadcast * restores prompt list functionality * restore prompt get functionality * adds api on tool manager to hotswap * spawns task to send deinit msg via messenger * adds slash command to hotswap agent * modifies load tool wait time depending on context * adds comments to retry logic for prompt completer * fixes lint * adds pid field to messenger message * adds interactive menu for swapping agent * fixes stale mcp load record * documents build method on tool manager builder and refactor to make the build method smaller
- Add globset-based pattern matching to support wildcards (* and ?) in allowedTools - Create util/pattern_matching.rs module with matches_any_pattern function - Update all native tools (fs_read, fs_write, execute_bash, use_aws, knowledge) to use pattern matching - Update MCP custom tools to support wildcard patterns while preserving exact server-level matching - Standardize imports across tool files for consistency - Maintain backward compatibility with existing exact-match behavior Enables agent configs like: - "fs_*" matches fs_read, fs_write - "@mcp-server/tool_*" matches tool_read, tool_write - "execute_*" matches execute_bash, execute_cmd
* first pass * add notification when /mcp & /tools * clear all tool related filed in agent * store mcp_enabled in chatsession & conversationstate * delete duplicate api call * set mcp_enabled value after load * remove clear mcp configs method * clippy * remain@builtin/ and *, add a ut for clear mcp config
* adds warnings for when tool settings are overridden by allowed tools * adjusts tool settings eval order * modifies doc * moves warning to be displayed after splash screen * canonicalizes paths prior to making glob sets * simplifies overridden warning message printing logic * adds more doc on path globbing
evanliu048
approved these changes
Aug 21, 2025
Comment on lines
+10
to
+26
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Send Release Details to Slack | ||
| uses: slackapi/slack-github-action@v1.23.0 # Or the latest version of this action | ||
| with: | ||
| payload: | | ||
| { | ||
| "release_name": "${{ github.event.release.name }}", | ||
| "tag_name": "${{ github.event.release.tag_name }}", | ||
| "release_url": "${{ github.event.release.html_url }}", | ||
| "author_name": "${{ github.event.release.author.login }}", | ||
| "repository_name": "${{ github.event.repository.name }}", | ||
| "repository_url": "${{ github.event.repository.html_url }}", | ||
| "release_description": ${{ toJSON(github.event.release.body) }} | ||
| } | ||
| env: | ||
| SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }} # Use the secret for the webhook URL |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {}
kensave
approved these changes
Aug 21, 2025
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.
Issue #, if available:
Description of changes:
As titled.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.