claude-code - 💡(How to fix) Fix support.claude.com Fin AI Agent chat: composer input field missing after accepting terms [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46126Fetched 2026-04-11 06:28:23
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1
RAW_BUFFERClick to expand / collapse

Bug Description

On https://support.claude.com, after opening the Fin AI Agent (Intercom chatbot) and accepting the privacy terms, the text input composer does not render. The bot asks "請告訴我們您的詢問是關於什麼的" (Please tell us what your inquiry is about) but there is no way to type a response.

Steps to Reproduce

  1. Go to https://support.claude.com
  2. Click the Intercom chat widget (bottom right)
  3. Open "Fin AI Agent"
  4. Accept the privacy/data usage terms
  5. Bot responds with a conversation ID and asks what your question is about
  6. No text input field appears — cannot type anything

Technical Details

Inspected the Intercom messenger iframe DOM:

  • composer-suggestions-container div exists but has height: 0
  • A suggestion button ("使用與限制") exists inside but has display: none
  • No <input>, <textarea>, or [contenteditable] element exists in the entire iframe
  • The DOM jumps straight from the last message to #anchor-bottom

The composer shell is present in the DOM structure, but the actual text input element was never rendered.

Expected Behavior

After accepting terms, a text input field should appear at the bottom of the chat so the user can describe their support issue.

Environment

extent analysis

TL;DR

The issue can likely be resolved by investigating and fixing the CSS styling or JavaScript code responsible for rendering the text input element in the Intercom chat widget.

Guidance

  • Verify that the CSS styles applied to the composer-suggestions-container div are not causing the text input element to be hidden or have zero height.
  • Check the JavaScript code that handles the rendering of the text input element after the user accepts the privacy terms, to ensure it is correctly creating and appending the input element to the DOM.
  • Inspect the network requests and console logs for any errors that may indicate why the text input element is not being rendered.
  • Test the Intercom chat widget in different browsers and environments to see if the issue is specific to Chrome or the specified URL.

Example

No code snippet can be provided without more information about the specific JavaScript or CSS code used in the Intercom chat widget.

Notes

The issue may be caused by a combination of CSS styling and JavaScript code, and further investigation is needed to determine the root cause. The fact that the composer-suggestions-container div has a height of 0 and the suggestion button has display: none suggests that there may be a styling or layout issue.

Recommendation

Apply a workaround by inspecting and modifying the CSS styles and JavaScript code responsible for rendering the text input element, to ensure it is correctly displayed after the user accepts the privacy terms. This is recommended because the issue appears to be related to the rendering of the text input element, and modifying the code may provide a quick fix.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING