When a User Input block is configured with a compiled Custom Interface (Interface Designer Beta) and connected to a Chat block, the submission does not hand off.

  1. What problem does this feature request solve?
    The Custom Interface (Interface Designer Beta) cannot hand off to a Chat block. When a compiled custom interface submits user input, the Chat block ignores it and resets to its own fresh interface instead of processing the submission and returning a response. The only workaround is replacing the Chat block with a Generate Text block, which eliminates conversation memory entirely.

  2. What is the use case for this feature?
    Anyone building a branded companion, coach, or assistant app needs both a custom visual entry experience AND a continuous conversation. These are not optional extras — they are the core of what makes a companion app feel like a companion. Right now you have to choose one or the other.

  3. Please describe the functionality of this feature request.
    When a User Input block with a compiled Custom Interface is connected to a Chat block, the submitted variable should be passed into the Chat block as the first user message — triggering the RAG pipeline and returning a response exactly as if the user had typed it directly into the Chat block’s own input. The Chat block should treat the handoff as the conversation opener, not a reset trigger.

  4. Is there anything else we should know?
    The Interface Designer is genuinely impressive. The Chat block with RAG is genuinely powerful. Right now they can’t talk to each other and that gap makes both significantly less useful. I don’t think I’m the only one hitting this wall.