Member Junction
    Preparing search index...

    Interface ProcessMessageInput

    Inputs to ConversationAgentRunner.processMessage. Replaces the original service's positional parameter list with a typed struct so call sites don't silently break when fields are added or reordered.

    interface ProcessMessageInput {
        appContext?: Record<string, unknown> | null;
        applicationId?: string | null;
        conversationDetailId: string;
        conversationId: string;
        explicitAgentId?: string | null;
        message: MJConversationDetailEntity;
        onProgress?: AgentExecutionProgressCallback;
        planMode?: boolean;
        requestedSkillIDs?: string[];
    }
    Index

    Properties

    appContext? applicationId? conversationDetailId conversationId explicitAgentId? message onProgress? planMode? requestedSkillIDs?

    Properties

    appContext?: Record<string, unknown> | null

    Application context to inject into the agent's system prompt. Used by embedders (Form Builder cockpit, Component Studio AI Assistant, future LXP) to ground the agent in their UI state.

    applicationId?: string | null

    Application context for default-agent resolution. App-scoped Application Settings beat the global default.

    conversationDetailId: string

    The MJ: Conversation Details row that tracks this agent run on the server. Required for the optimized RunAIAgentFromConversationDetail path, which loads conversation history server-side.

    conversationId: string

    The conversation this message belongs to.

    explicitAgentId?: string | null

    Optional explicit agent ID. When set, wins over the DefaultAgentResolver chain. Mirrors the widget's [DefaultAgentId] input.

    message: MJConversationDetailEntity

    The just-sent user message (used for latestMessageId plumbing).

    onProgress?: AgentExecutionProgressCallback

    Optional progress callback. Mirrors the original service's signature — embedders forward this through to the widget's progress UI.

    planMode?: boolean

    Per-request Plan Mode toggle. When true (and the resolved agent's SupportsPlanMode capability is on), the root agent must present a plan for human approval before it may execute Actions/Sub-Agents. Defaults off — no behavior change unless set.

    requestedSkillIDs?: string[]

    Skill IDs the user requested via /skill-name mentions in the composer. Forwarded to the server, which intersects them with the agent's accepted skills AND the user's Run permission before any activate. Defaults to none.

    Settings

    Member Visibility

    On This Page

    Properties