metadata retrieval not available by design?

[sarunas-zebra]

So we can add metadata with model_settings.
But there is no way of getting it anywhere (ModelResponse, RunResult, context_wrapper doesn't have it)

Is it by design? (for reasons)
Or is it because it's just not implemented yet?

Thank you very much!

[EbadullahJ]

📌 metadata retrieval not available by design?

You're right — you can add metadata via model_settings,
but currently there's no way to retrieve it from:

• ModelResponse
• RunResult
• or context_wrapper

---

✅ Why?

This behavior is intentional (by design for now).
Metadata is mainly used internally (e.g., tagging, tracking) and isn’t exposed in the outputs — likely to keep response payloads cleaner or for security/design consistency.

---

💡 What You Can Do

If you need to track values like IDs, tags, or flags across runs:

• Store metadata externally in your app or agent logic
• Or attach that data to the message content or tool inputs

---

This might change in future updates if there's enough demand — feel free to 👍 or comment to signal interest!

Hope this helps!

[sarunas-zebra]

Thank you for response!
Would be nice to have a way to remain stateless in application, but have name of last used agent in metadata for multi agent applications without extra complexity.

[sibblegp]

Last used agent in multi agent applications is actually pretty useful. I second that.

Or going back and reviewing the entire trace of how it arrived at a certain spot. I.e.

• Orchestration agent
• Agent 1 - Tool 1
• Agent 1 - Tool 2
• Agent 2 - Tool 1

Would be great to be able to see that.

[github-actions]

This issue is stale because it has been open for 7 days with no activity.