MedAssistConfig is the optional third argument to renderMedAssist. Every field is optional — anything you omit falls back to the agent config you set in console.eka.care.
MedAssistConfig
Header text shown to the user.
Icon URL for the widget launcher.
Which backend environment to connect to.
Custom API base URL. Only used in development mode.
Auth token sent when the session is created.
Sent as the
x-auth-token header on the create-session API call.Key-value context object sent with the session to the backend. Used by the agent and its tools.
Real-time transport. Usually inherited from agent config.
full is fullscreen; widget is a floating window. Mobile always uses the widget layout.Show a resize toggle in the header.
Input types to show. Omit to show all.
A pre-loaded greeting and suggestion pills shown before the user types.
Hide the “Powered by Eka Care” footer branding.
Callback fired when the user closes the widget.
Show the close (✕) button in the header.
Brand colors and styling. See Theming & design system.
How config maps to the console
Many fields can be set either here or on the agent in the console. When both exist, the agent config seeds the defaults and yourconfig overrides them.
| Field | Console relationship |
|---|---|
agentId | Resolves the agent’s config — name, theme, allowed inputs, nudges, initial message. |
environment | Selects which backend (dev/staging/prod) hosts the agent. |
context | Passed to the backend session; used by the agent and tool chain. |
theme | Seeded from the agent config’s theme, overridable here. |
initialMessage | Can come from the agent’s configured greeting and suggestion pills. |
allowed | Input-type restrictions can also be sourced from the agent config. |

