Repository navigation
Conversation
Keep one summary entry per interaction and role in the store. Requests are a plain await, and a result applies only while its entry is still loading. The SDK already owns task capabilities, request correlation and the 15s timeout. - Remove ownership generations, pending-request records, the deadline fence, post-call freeze state, capability seeding and the status queue - Follow Agent Desktop for responses: viewed once when received, edited as a flag, DEFAULT / NOT_RECEIVED / IGNORED states, fire-and-forget consult and transfer responses, and no wrap-up gating on summary generation - Update the vendored SDK and its contract test to the new Task wiring - Make the SDK lock tests independent of git hook env and the host Node version
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
rsarika
force-pushed
the
ai-assistant-summary
branch
3 times, most recently
from
October 8, 2026 05:15
be8828a to
950dc67
Compare
Keep only what the AI summary feature needs and follow Agent Desktop where the widgets differed. - Drop the AI-pipeline tooling (SDK lock, release verifier, publish boundary), design and requirement artifacts, the Playwright visual/E2E harness and the sample-app fixtures. - Request mid-call and post-call summaries only when the task's SDK capabilities enable them. - Keep the initiator's like/dislike local until the consult or transfer response instead of sending it twice. - Send the post-call response with the wrap-up reason name and do not wait for it; wrapupCall resolves a boolean. - Fold the task summary modules into helper.ts with one mid-call view, and derive the summary view types from the AISummary props. - Make AISummary store-driven and WrapUpSummary a controlled component with an always-visible reason list; scope the wrap-up popover padding override. - Use the SDK summary types directly: store entries keep the SDK summary fields (sections record, summaryText, resolution, adaptiveCard), feedback uses thumbs_up/thumbs_down and the action is AISummaryAction. The store defines only AISummaryRole, AISummaryEntry and AISummaryStatusDetail. - Drop the Adaptive Card resource sanitizer and renderability check that Agent Desktop does not have; keep resetting the renderer error boundary when a replacement card arrives. - Revert changes unrelated to summaries (type widenings, mediaResourceId, test script excludes, Real-time Assist typing) and trim the test fixtures.
rsarika
force-pushed
the
ai-assistant-summary
branch
from
October 8, 2026 07:07
950dc67 to
1d3bc54
Compare
This branch has not been deployed
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
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.
COMPLETES Issue link pending
This pull request addresses
AI summaries for voice interactions in the Contact Center widgets: the initiating agent's consult/transfer summary, the receiving agent's summary in the AI Assistant, and the post-call summary at wrap-up.
This branch carries the two feature commits from #744 plus simplification and scope cleanup. The changes keep the summary UI in the existing widget/helper/store flow over the Task SDK and preserve the existing consult and wrap-up behavior when summaries are disabled.
by making the following changes
aiSummaries[interactionId][role]) and calls the Task SDK methods for requests and responses. It requests a summary only whentask.aiSummaryCapabilitiesenables that kind. Like Agent Desktop, the initiator's and the wrap-up feedback stay local and go out once with the consult/transfer or post-call response; the receiving agent's feedback is sent right away. It uses the SDK summary types directly (sections record,summaryText,resolution,adaptiveCard,thumbs_up/thumbs_downfeedback,AISummaryAction) and defines onlyAISummaryRole,AISummaryEntryandAISummaryStatusDetail.getAISummaryPropsbuilds the mid-call and wrap-up summary views for CallControl. Consult and transfer send the initiator's response as they start.wrapupCallresolves a boolean and sends the post-call response with the wrap-up reason name aswrapUpCode, without waiting for it.AISummarycomponent;WrapUpSummary(searchable reason list plus summary); the summary in the consult/transfer popover; a "View summary" branch for the receiving agent in the AI Assistant.onAISummaryStatusChangeon the call-control web component.resolutionspoints@webex/contact-centeratvendor/contact-center-cc-summaries.tgz.findMediaResourceId, test script excludes).Before merge:
Change Type
The following scenarios were tested
yarn test:cc-widgetson Node 24 passes for every workspace, including store, task, cc-components and ai-assistant.yarn test:toolingand eslint (test:styles) pass; the pre-commit hook passed.yarn.lockresolves unchanged from a clean worktree.The GAI Coding Policy And Copyright Annotation Best Practices
Checklist before merging
Make sure to have followed the contributing guidelines before submitting.
🤖 Generated with Claude Code