feat(personal-community-sentiment-triage): add opt-in Slack rich blocks#54
Draft
wscurran wants to merge 2 commits into
Draft
feat(personal-community-sentiment-triage): add opt-in Slack rich blocks#54wscurran wants to merge 2 commits into
wscurran wants to merge 2 commits into
Conversation
Signed-off-by: Will Curran <wcurran@nvidia.com>
Signed-off-by: Will Curran <wcurran@nvidia.com>
Collaborator
Author
|
Keeping in draft until #53 is merged in. |
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.
Description
Depends on #53.
This is a stacked draft based on #53's Hermes 0.18 upgrade. While #53 remains
open, GitHub will show its dependency changes in this PR; after #53 merges, the
diff will reduce to this follow-up.
Hermes 0.18 includes optional Slack Block Kit rendering, but this example owns
its configuration generator and does not inherit NemoClaw's Slack manifest.
Upgrading the base image alone therefore leaves rich-block rendering disabled.
This change completes the Community-side integration:
agent.verify_on_stop: false.NEMOCLAW_SLACK_RICH_BLOCKS, accepting onlytrueorfalseanddefaulting to
false..env.example, the staged Dockerfile arguments, andgenerate-config.ts.platforms.slack.extra.rich_blockswhen Slack isconfigured.
renderer.
request.bodyandresponse.assistant_messageNeMo Relay hook payloads while retaining thelegacy rich-kwargs fallbacks.
The default remains backward-compatible. Existing deployments retain
plain-text Slack responses unless they explicitly set
NEMOCLAW_SLACK_RICH_BLOCKS=true.No additional Slack OAuth scopes or app reinstall are required.
Verification
python scripts/check_license_headers.py --checkgit diff --checkbash -n.verify_on_stop: false, default-off, explicittrue/false, invalid-value rejection, and Slack-disabled behavior.
provider responses, and paired tool-call IDs.
plugins.platforms.slack.block_kit.render_blocksAPI and requires one nativethree-column
tableblock.in the authoring environment; every image build now executes the renderer
smoke automatically.
Release And Compliance
.envfiles, private certificates, snapshots, or tokencaches are included.
details.
git commit -s).