added agents

[ruchI9897]

No description provided.

[gemini-code-assist]

Code Review

This pull request introduces an on-page debugging panel, , which allows developers to inspect and troubleshoot embedded ThoughtSpot instances by interacting with an AI assistant and picking host page elements for style context. The panel is dynamically mounted when enableDebugAgent is enabled in the configuration. Feedback on these changes highlights several areas for improvement: correcting JSDoc tag ordering and versioning in src/types.ts per the style guide, making the SSE parser in toSseEvents more robust, clearing the hovered element state when the cursor leaves the viewport or enters the debug panel, using a temporary style block to prevent cursor flickering during element picking, and resolving a TypeScript type mismatch in the sendMessage event handler.

[gemini-code-assist]

The JSDoc tags for enableDebugAgent violate the Repository Style Guide rules on Tag Ordering (Rule 1). @version must be ordered before @default. Additionally, if this feature is backported or MCP'd to an earlier ThoughtSpot Cloud version, the @version JSDoc tag should reflect the actual release version where the feature is available, overriding the canonical SDK-to-ThoughtSpot version mapping style guide.

Suggested change

	* @default false
	* @version SDK: 1.53.0
	* @version SDK: 1.53.0 | ThoughtSpot Cloud: 26.10.0.cl
	* @default false

References

1. Enforce tag ordering: @Version (3) must come before @default (9). ^(link)
2. When a feature is backported or MCP'd to an earlier ThoughtSpot Cloud version, the @Version JSDoc tag should reflect the actual release version where the feature is available, overriding the canonical SDK-to-ThoughtSpot version mapping style guide.

[gemini-code-assist]

The current toSseEvents implementation splits the buffer by \n\n and assumes each block starts with data: . This can fail if there are leading newlines, keep-alive comments, or other SSE fields (like event: ) preceding the data: line in the same block. Additionally, if JSON.parse throws an error on a malformed line, the entire stream processing is aborted.

Splitting by \n and processing lines starting with data: is much more robust and standard for SSE parsing.

function toSseEvents(buffer: string): { events: Array<Record<string, unknown>>; rest: string } {
    const lines = buffer.split('\n');
    const rest = lines.pop() ?? '';
    const events: Array<Record<string, unknown>> = [];
    for (const line of lines) {
        const trimmed = line.trim();
        if (trimmed.startsWith('data: ')) {
            try {
                const data = JSON.parse(trimmed.slice(6));
                events.push(data);
            } catch (e) {
                // Ignore malformed JSON lines gracefully
            }
        }
    }
    return { events, rest };
}

[gemini-code-assist]

When the user moves the mouse over the debug panel itself or out of the viewport, the hovered state is not cleared, leaving the hover overlay stuck on the last hovered element. Clearing hovered when the target is null or inside the panel improves the user experience.

        const onMove = (e: MouseEvent) => {
            const target = document.elementFromPoint(e.clientX, e.clientY);
            if (!target || panelRef.current?.contains(target)) {
                setHovered(null);
                return;
            }
            setHovered(target);
        };

[gemini-code-assist]

Setting document.body.style.cursor = 'crosshair' does not override the cursor style of elements that have their own cursor defined in CSS (such as links, buttons, or inputs). This causes the cursor to flicker between a crosshair and other pointers during element picking. Appending a temporary <style> block ensures a consistent crosshair cursor across all elements.

        const style = document.createElement('style');
        style.textContent = '* { cursor: crosshair !important; }';
        document.head.appendChild(style);
        return () => {
            document.removeEventListener('mousemove', onMove, true);
            document.removeEventListener('click', onClick, true);
            style.remove();
        };

[gemini-code-assist]

The sendMessage function is typed to expect a React.FormEvent, but it is also called from onKeyDown with a React.KeyboardEvent. Under strict TypeScript compiler options, this will cause a type mismatch compilation error. Changing the parameter type to React.SyntheticEvent (and making it optional) resolves this cleanly.

Suggested change

	async function sendMessage(e: React.FormEvent) {
	e.preventDefault();
	async function sendMessage(e?: React.SyntheticEvent) {
	if (e) e.preventDefault();

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@thoughtspot/visual-embed-sdk@680

commit: 5a18469