#LWC35 人がディスカッション中

@Manas Datta

Thanks for testing that - a correct id still landing on the bare panel actually rules the id out and points to an enablement gap. open() drives the SAME native Agentforce side panel you'd get manually, and botId is only optional targeting - if that agent isn't the one wired to the panel for your running user, open() falls back to the default panel/picker no matter which id you pass. 

Quick way to confirm: open the native Agentforce panel manually (the Agentforce icon, not your LWC). If it also drops you on a picker or the wrong agent, it's the setup, not your code - check the agent is Active, is the one enabled for the Agentforce panel in that org, and your running user has access to it (permission set + the agent's assigned users). Fix that and open(botId) will land on it. 

If you need a specific agent guaranteed every time regardless of the panel, skip accApi and use the Agent API instead (Connect REST /einstein/ai-agent, or its Apex wrapper): you start a session against the exact agent id server-side and render the replies in your own LWC chat UI - no panel, no picker, fully deterministic.

こんにちは、 

これは公式のSalesforceドキュメントで確認できた事例ではありませんが、画像のパターンから判断すると、ページのCSS（スタイルシート）が正しく読み込まれず、ブラウザのデフォルトスタイルが表示されている可能性が高いです。「ユーザー名」「パスワード」が実線で囲まれた形で表示されるのは、HTMLの<fieldset><legend>要素にCSSが適用されない場合のブラウザ標準（未装飾）表示によく見られるパターンです。 

確認・対処方法： 

1. シークレットウィンドウ（Ctrl+Shift+N）で同じログインページを開いて再現するか確認 — 拡張機能やキャッシュの影響を切り分けられます。 

2. Chrome拡張機能（特に広告ブロッカー、翻訳ツール、WhatFixなどの業務用拡張機能）を一時的に無効化して再読み込み — 拡張機能がページのCSS読み込みを妨げているケースが報告されています。 

3. ブラウザのキャッシュとCookieをクリアしてから再読み込み。 

4. 会社のプロキシ／セキュリティソフトが外部CSSリソースをブロックしていないか、社内IT部門に確認（企業ネットワーク環境でよくある原因です）。 

上記で解決しない場合は、具体的な原因を断定できる公式情報が見つからなかったため、Salesforceサポートへの問い合わせをおすすめします。

Hi @Hitesh Sharma, 

You can use 

After authorizing the org, use SFDX: Retrieve Source from Org in VS Code to retrieve the required components. 

For JSON files, it depends on where they are stored: 

• Static Resource/LWC bundle → retrieve the corresponding metadata. 
• Salesforce record/data → use SOQL, Data Loader, or another data-export tool. 

Hope this helps! 

Hey Megan, 

Adding one thing to Himanshu's answer since it's mostly right but slightly understates option 2: Salesforce actually has a fully supported LWC-based header customization for Messaging (lightningSnapin__MessagingHeader target), you extend the base chat header component and can add whatever fixed text/markup you want inside it. This is documented and stays visible for the whole conversation, unlike the greeting-message approach, which scrolls away. 

So realistically you have two solid, supported paths: 

1. Custom LWC header (extends BaseChatHeader/MessagingHeader), gives you a persistent banner area inside the actual chat window that Salesforce won't overwrite on releases, since it's a supported customization point, not DOM hacking 

2. A banner on your host page around the widget (Himanshu's option 1), simplest if the disclaimer doesn't need to be inside the chat window itself 

Both are supported. The custom header route is probably closer to what you're picturing since it sits inside the widget alongside "Powered by Agentforce," not just around it. 

Reference: