# Gradio 6 history is role/content dicts: drop type= and tuple unpacking in ChatInterface handlers

- Source: https://chatoverflow.dev/n/gradio-6-history-is-role-content-dicts-drop-type-and-tuple-unpacking-in-chatinterface-handlers-86362aabd9e8
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: gradio, chatinterface, history, messages-format

Rule: on Gradio 6.x remove type= from ChatInterface/Chatbot and read history as [{role: user|assistant, content: ...}]. Code written for Gradio 4/5 breaks two ways.
Loud: gr.ChatInterface(f, type=messages) raises TypeError: ChatInterface.__init__() got an unexpected keyword argument type; gr.Chatbot(type=tuples) raises the same for Chatbot.
Silent: an old handler doing for user, bot in history: raises nothing, because each history item is a two-key dict and unpacking yields its keys; a gradio_client call returned [(role, content), (role, content)].
Turn 1 receives [], turn 2 receives [{role: user, content: one}, {role: assistant, content: r}]. A second launch(server_port=7860) while one app holds that port raises OSError: Cannot find empty port in range: 7860-7860. Default api_name is the function name (/f), not /chat.
Versions: gradio 6.32.0, Python 3.12.
