Where should runtime non-LLM parameters be placed in RunAgentInput? (state vs context vs forwardedProps)

[user1500177]

Hi AG-UI team ,

I’m opening this discussion after implementing a pattern suggested in the AgentOS (Agno) forum, and I want to confirm the correct place in AG-UI to pass runtime parameters.

Background

We have some runtime parameters (example: id1, id2, etc.) that:

• are injected by the UI at runtime
• must NEVER be generated or modified by the LLM
• must always be available to tools
• are not visible to users
• are used for safe routing / multi-tenant separation

We previously passed them inside prompts and relied on instructions telling the LLM to copy them into tool calls.
This worked most of the time but occasionally the model hallucinated or dropped them, which is unsafe.

Based on AgentOS guidance, we moved to (agno-agi/agno#7439):

• Passing these parameters via RunAgentInput.state
• AgentOS mapping them into RunContext.session_state
• Injecting them into tools via tool_hooks

This will work technically i suppose , but I want to confirm the intended AG-UI design.

What triggered the question

Looking at the docs:
https://docs.ag-ui.com/sdk/js/core/types#runagentinput

RunAgentInput includes (which is the best place to pass such ids- all our mcp tools supports these IDs so that if going by what agno said we could use the tool_hook to inject in these Ids like that - agno-agi/agno#7439)

• state
• context
• forwardedProps

Example payload:

{
  "threadId": "t1",
  "runId": "r1",
  "tools": [],
  "context": [],
  "forwardedProps": {},
  "state": {
    "param1": "value",
    "param2": "value"
  },
  "messages": [
    {
      "id": "m1",
      "role": "user",
      "content": "User prompt"
    }
  ]
}

From reading AgentOS code and discussions, it appears that state is mapped into the agent runtime (session_state) and its avaible in the tool_hooks (**Is THIS THE BEST APPRACH and intended use case of the state paramter i needed to confirm**)

Main Question

For runtime parameters like id1, id2:

Which field in RunAgentInput is the intended place to send them?

Specifically:

Should we treat the fields like this?

messages → LLM-visible conversation
state → runtime / non-LLM parameters
context → ?
forwardedProps → ?

Is state the recommended place for passing those ids ??

Why this matters

We want to follow the intended AG-UI architecture and avoid inventing our own conventions.

Right now we assume:
state = non-LLM runtime context

We’d love confirmation (or corrections) from the team so as to make it a Standard design.