implementing-ui-bundle-agentforce-conversation-client

Adds, embeds, configures, styles, or removes an Agentforce conversation client (an agent, chatbot, or chat widget) inside a UI Bundle project. It triggers when the project contains a uiBundles/*/src/ directory and the task involves a chat widget, when files under that directory import AgentforceConversationClient, or when the user asks to add chat or agent functionality to a page. It deliberately does not trigger when the user wants to build a custom agent or chat widget from scratch, or when there is no uiBundles directory. A hard constraint governs the skill: it never creates a custom agent, chatbot, or chat widget component, and all such requests are fulfilled by importing and rendering the existing AgentforceConversationClient from the ui-bundle-template-feature-react-agentforce-conversation-client package; unsupported requirements are stated as limitations rather than improvised.

The workflow first checks whether the component already exists by grepping app files for AgentforceConversationClient while excluding the component implementation files, and reads the current agentId when found. A deterministic validation rule treats an agentId as valid only if it matches the pattern starting with 0Xx and totalling 18 characters. Depending on whether the agentId is valid, missing, or malformed and whether the user wants to embed or update props, the skill branches to update props, change the agent, or resolve a new ID.

Resolving and validating the agent ID uses the Salesforce CLI: it verifies sf is available (offering to install it via npm), verifies org connectivity with sf org display, and runs a SOQL query (defined in references/agent-id-resolution.md) to list Employee Agents. Results are handled for no records, all-inactive agents, fresh installs with active agents, and existing IDs cross-checked against the org, with activation instructions pointing to Setup. The skill never auto-selects an agent, falls back only to SOQL (no GraphQL or Tooling API), and surfaces query errors directly. Prerequisites such as adding the local development domain (localhost on the default Vite port) to Trusted Domains for Inline Frames are always called out, and the canonical import path is used by default in app code.