If creating a new chat, add these tags to it. This is ignored if the chat already exists.

[LEGACY] A mapping of tool_call_id to approval boolean. When submitting tool approvals, the input payload must match the original inputs used to generate the tool calls (same as the previous API call). If tool_approvals is provided, the message parameter is ignored and the tool calls are executed or skipped. Prefer using 'approvals' field for new integrations.

A mapping of function name to approval decision for codemode agents. Applies to functions decorated with @requires_approval. Use 'approve' for one-time approval, 'approve_session' for session-level approval, 'deny' for one-time denial, or 'deny_session' to deny for the session.

Optional list of skill IDs to use. When provided, only these skills are
fetched and applied. Useful for testing a specific skill in isolation.

Optional table metadata from the DQ monitor setup flow.

Each column includes a column_id (integer) which must be used as the key
in the output checks dict. Example structure:
{
"table_id": 24,
"table_name": "data_products",
"schema_name": "public",
"ds_title": "Alation Analytics",
"columns": [
{
"column_id": 1629,
"column_name": "contact_email",
"column_type": "text"
},
{
"column_id": 1501,
"column_name": "delivery_system_count",
"column_type": "int8(64,0)"
}
]
}