feat(ccwidgets): Implementing Real Time Assistance feature within cc widgets by Kesari3008 · Pull Request #722 · webex/widgets

Kesari3008 · 2026-07-21T18:23:54Z

COMPLETES #https://jira-eng-sjc12.cisco.com/jira/browse/CAI-8037

This pull request addresses

Implementing Real Time Assistant Widget within existing cc widgets

by making the following changes

Added new widget: AI Assiatnt under which real time assistance feature is implemented

Change Type

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update
Tooling change
Internal code refactor

The following scenarios were tested

The testing is done with the amplify link
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >

The GAI Coding Policy And Copyright Annotation Best Practices

Checklist before merging

I have not skipped any automated checks
All existing and new tests passed
I have updated the testing document
I have tested the functionality with amplify link

Make sure to have followed the contributing guidelines before submitting.

…x#668) Co-authored-by: Shreyas Sharma <shreyassharma9912@gmail.com>

Co-authored-by: Cursor <cursoragent@cursor.com>

…ed response feature

… helper

aws-amplify-us-east-2 · 2026-07-21T18:30:27Z

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-722.d1b38q61t1z947.amplifyapp.com

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 65e4090194

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-07-21T18:30:58Z

@@ -0,0 +1,70 @@
+{
+  "name": "@webex/cc-ai-assistant",


Add the AI assistant spec alongside the module

This introduces a new workspace package/widget, but the change contains no ai-assistant module spec or standing-doc/router update, so the new public surface cannot be routed or validated by the repo's SDD docs. Please add the module spec/standing doc updates in the same change as the code.

AGENTS.md reference: AGENTS.md:L68-L68

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-21T18:30:58Z

+    );
+  }
+
+  if (status === 'listening' || hasFiredInitialRequest) {


Show errors before the listening placeholder

When the first getRealTimeAssistance call rejects, the hook has already set hasFiredInitialRequest to true and then sets status to error; this branch runs before the error branch, so the panel keeps showing “Listening for information” and never exposes the retry/error message. Please check status === 'error' before the hasFiredInitialRequest listening fallback.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-21T18:30:58Z

+        oninput={(e: CustomEvent<{value: string}> & {target: HTMLInputElement}) =>
+          onChange(e.detail?.value ?? e.target?.value ?? '')
+        }


Use React's input handler for context changes

For the Momentum React Input, the repo's existing usage is the camel-cased onInput; this lowercase oninput prop is not handled by the React wrapper, so typing in the “Add context” field never calls onChange and the controlled value stays empty. That blocks agents from submitting extra context after starting a suggestion session.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-21T18:30:58Z

+    onClose: 'function',
+    onClearChat: 'function',
+    onFullScreenToggle: 'function',
+    onSuggestionReceived: 'function',


Bridge the exposed suggestion callback

For Web Component consumers this is the only arrival callback exposed, but the AI assistant hook only reads and invokes onRealTimeAssistReceived, never onSuggestionReceived. As a result <widget-cc-ai-assistant onSuggestionReceived=...> will not fire when a suggestion arrives; please either expose onRealTimeAssistReceived here or bridge the deprecated prop to the new callback.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-21T18:30:58Z

+                        <label key={widget}>
+                          <input
+                            type="checkbox"
+                            name={widget}
+                            checked={selectedWidgets[widget]}
+                            onChange={handleCheckboxChange}
+                            data-testid={`samples:widget-${widget}`}
+                          />


Remove the duplicate widget checkbox

Each widget now renders this second label in addition to the original one above it, producing duplicate checkboxes with the same name and data-testid. In WebRTC-locked mode the duplicate also omits the disabled guard, so users can still toggle widgets that the first checkbox correctly disables, and tests querying by test id become ambiguous.

Useful? React with 👍 / 👎.

Shreyas281299

There are no UTs and SnapshotTesting for new components in cc-components.

Shreyas281299 · 2026-07-22T09:58:51Z

+                          />
+                          &nbsp;
+                          {formatWidgetName(widget)}&nbsp;
+                          {widget === 'outdialCall' && (


I think this is redundant

Shreyas281299 · 2026-07-22T09:59:34Z

@@ -1,5 +1,16 @@
 import {Profile} from './store.types';

+export const AI_FEATURE_SUGGESTED_RESPONSES_KEY = 'isSuggestedResponsesEnabled';


This should be in the constants file

Shreyas281299 · 2026-07-22T10:00:14Z

+export const AI_FEATURE_SUGGESTED_RESPONSES_KEY = 'isSuggestedResponsesEnabled';
+
+const getValueAtPath = (obj: unknown, path: string): unknown => {
+  return path.split('.').reduce<unknown>((acc, segment) => {
+    if (acc && typeof acc === 'object' && segment in (acc as Record<string, unknown>)) {
+      return (acc as Record<string, unknown>)[segment];
+    }
+    return undefined;
+  }, obj);
+};


Do we not have correct types for this? we are typecasting and using unknown alot

Shreyas281299 · 2026-07-22T10:00:42Z

 const TASK_MULTI_LOGIN_HYDRATE = 'task:multiLoginHydrate';
+// Mirrored from the SDK's CC_TASK_EVENTS — importing the runtime const breaks
+// our jest transform setup.
+const SUGGESTED_RESPONSE_EVENT = 'SUGGESTED_RESPONSE';


These shoudl be in the constants file

Moved. I have moved MULTI_LOGIN_HYDRATE as well which is not part of this PR

Shreyas281299 · 2026-07-22T10:01:40Z

    task.on(TASK_EVENTS.TASK_PARTICIPANT_LEFT_FAILED, this.refreshTaskList);
    task.on(TASK_EVENTS.TASK_CONFERENCE_TRANSFERRED, this.refreshTaskList);
    task.on(TASK_EVENTS.TASK_CONFERENCE_TRANSFER_FAILED, this.refreshTaskList);
-    task.on(TASK_EVENTS.TASK_POST_CALL_ACTIVITY, this.refreshTaskList);


Why are we removing this?

It was already present, please check before task.on(TASK_EVENTS.TASK_CONFERENCE_ESTABLISHING, this.refreshTaskList);

Shreyas281299 · 2026-07-22T12:51:47Z

+  const getRealTimeAssistance = jest.fn().mockResolvedValue({});
+  return {
+    __esModule: true,
+    default: {
+      cc: {
+        apiAIAssistant: {
+          getRealTimeAssistance,
+        },
+      },
+      clearRealTimeAssist,
+    },
+  };
+});


we should be using mocks from test-fixtures. And use the complete mock cc object

Shreyas281299 · 2026-07-22T12:52:10Z

+import {useAiAssistant} from '../src/helper';
+import store from '@webex/cc-store';
+
+jest.mock('@webex/cc-store', () => {


[nitpick ]If we can avoid mocking store that would be better.

Shreyas281299 · 2026-07-22T12:53:47Z

+  onFullScreenToggle,
+  onRealTimeAssistReceived,
+}: UseAiAssistantInput) => {
+  const [chrome, setChrome] = useState<AIAssistantChromeState>('closed');


Is this chrome googleChrome?? or something new?

Shreyas281299 · 2026-07-22T12:54:02Z

+  onRealTimeAssistReceived,
+}: UseAiAssistantInput) => {
+  const [chrome, setChrome] = useState<AIAssistantChromeState>('closed');
+  const [isFullScreen, setIsFullScreen] = useState(false);


Why are we worrying about fullscreen?

Shreyas281299 · 2026-07-22T12:54:35Z

+const REAL_TIME_ASSIST_FLAG = 'isSuggestedResponsesEnabled';
+const GREETING_TEXT = "I'm here to help! I'll keep listening and suggest responses as the conversation evolves.";
+
+interface UseAiAssistantInput extends IAIAssistantProps {
+  interactionId?: string;
+  agentId: string;
+  isFeatureEnabled: boolean;
+  realTimeAssist: RealTimeAssistPayload[];
+}
+
+type UserMessage = {id: string; text: string; sentAt: number};


we can move these to a types/constants file

akulakum and others added 8 commits May 27, 2026 14:12

fix(cc): migrate widgets to SDK state-machine-driven uiControls (webe…

f28dd98

…x#668) Co-authored-by: Shreyas Sharma <shreyassharma9912@gmail.com>

fix(deploy): add task-refactor in deploy yml (webex#689)

76ef8f7

fix(store): fixes after bug bash (webex#691)

cb89e5f

Co-authored-by: Cursor <cursoragent@cursor.com>

fix(task-refactor): bug bash fixes (webex#692)

01bd548

chore(ci): stop publishing docs from task-refactor (webex#696)

8c26ab3

feat(ai-assistant): add new AI Assistant Widget and implement suggest…

225c822

…ed response feature

refactor(ai-assistant): collapse ref-sync effects and inline swapIcon…

bb18632

… helper

feat(ccwidgets): implementing real time assist feature

65e4090

Kesari3008 requested a review from a team as a code owner July 21, 2026 18:23

Kesari3008 added the validated Indicates that the PR is ready for actions label Jul 21, 2026

chatgpt-codex-connector Bot reviewed Jul 21, 2026

View reviewed changes

Shreyas281299 requested changes Jul 22, 2026

View reviewed changes

		@@ -1,5 +1,16 @@
		import {Profile} from './store.types';

		export const AI_FEATURE_SUGGESTED_RESPONSES_KEY = 'isSuggestedResponsesEnabled';

Uh oh!

Conversation

Kesari3008 commented Jul 21, 2026

COMPLETES #https://jira-eng-sjc12.cisco.com/jira/browse/CAI-8037

This pull request addresses

by making the following changes

Change Type

The following scenarios were tested

The GAI Coding Policy And Copyright Annotation Best Practices

Checklist before merging

Uh oh!

aws-amplify-us-east-2 Bot commented Jul 21, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jul 21, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 21, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 21, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 21, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 21, 2026

Choose a reason for hiding this comment

Uh oh!

Shreyas281299 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants