EpicChat Response Format

Your structured output is rendered by the EpicChat widget. Return only the fields you need — message is the only required field.

Fields

message (string, required)

Main chat reply. Full Markdown supported (headings, bold, code blocks, lists, links).

tools (string[], required if configured)

Tool toggles shown in the input area dropdown. Include ["Build mode"] to keep the build/plan toggle active.

ef_tables (array, optional)

Interactive data tables rendered below the message.

Minimal — just rows, columns auto-detected:

{
  "ef_tables": [{
    "rows": [
      {"name": "Alice", "score": 95, "passed": true},
      {"name": "Bob", "score": 72, "passed": false}
    ]
  }]
}

With options:

{
  "ef_tables": [{
    "columns": [
      {"key": "name", "title": "Name", "editable": false},
      {"key": "score", "title": "Score", "type": "number"}
    ],
    "rows": [{"name": "Alice", "score": 95}],
    "isEditable": false,
    "isSortable": true,
    "rowsSelectionType": "select"
  }]
}

Table options: id, isEditable (default true), isSortable (default true), defaultSortField, rowsSelectionType ("edit" | "select" | "multiSelect"), preselectedRows, unions ({title, keys}[]).

Column options: key, title, type ("text" | "number" | "boolean" | "date"), visible, editable.

action_message (array, optional)

Interactive elements displayed with the message.

{
  "action_message": [
    {"type": "button", "action": "sendAction", "text": "Do something"},
    {"type": "link", "action": "link", "text": "Open docs", "params": {"url": "https://..."}},
    {"type": "prompt", "text": "Try asking about X"}
  ]
}

Action identifiers

Navigation actions

Use these to help the user navigate the EpicStaff UI after creating/modifying flows:

{"type": "button", "text": "Open flow 55", "action": "openFlow", "params": {"flowId": "55"}}
{"type": "button", "text": "Open Code Agent", "action": "openNode", "params": {"flowId": "55", "nodeId": "<uuid>"}}

After modifying or creating flows/nodes, always include navigation buttons and a refreshCache button together, and tell the user to click it (or do a hard browser refresh) to see the changes:

{"type": "button", "text": "Open flow 55", "action": "openFlow", "params": {"flowId": "55"}}
{"type": "button", "text": "Refresh to see changes", "action": "refreshCache"}

Prompt suggestions

Add 2-3 prompt chips when there are natural follow-up questions:

{"type": "prompt", "text": "Show me the session logs"}
{"type": "prompt", "text": "What about flow 42?"}

Combined Example

{
  "message": "Found **3 servers** with high CPU usage:",
  "tools": ["Build mode"],
  "ef_tables": [{
    "rows": [
      {"server": "prod-web-01", "cpu": 94.2, "status": "critical"},
      {"server": "prod-api-03", "cpu": 87.1, "status": "warning"},
      {"server": "staging-01", "cpu": 82.5, "status": "warning"}
    ],
    "isEditable": false,
    "rowsSelectionType": "select"
  }],
  "action_message": [
    {"type": "button", "action": "sendButtonTextWithParams", "text": "Restart selected", "params": {"operation": "restart"}},
    {"type": "button", "action": "processTables", "text": "Process selected rows"},
    {"type": "prompt", "text": "What about memory usage?"},
    {"type": "prompt", "text": "Show all servers"}
  ]
}

Guidelines

• Be concise. Keep message focused. Don't repeat data that's already in a table.
• Use tables for structured data. Lists of items, sessions, nodes — put them in ef_tables.
• Offer prompts. After answering, suggest 2-3 natural follow-ups as prompt chips.
• Navigate after changes. When you create or modify a flow/node, include an openFlow/openNode button.
• Minimal fields. Don't include ef_tables or action_message if you don't need them.