Python: feat: forward function_invocation_kwargs through DevUI to agent.run

[Manjunath Janardhan (manjunathshiva)]

Motivation & Context

DevUI builds the kwargs passed to agent.run() by hand and only forwards stream and session, so tools that read request-scoped values via FunctionInvocationContext.kwargs (tenant id, auth token, user id) silently receive nothing when the agent is run through DevUI.

The same agent works correctly outside DevUI via a direct agent.run(..., function_invocation_kwargs=...) call. Parity matters when agents are first developed / debugged in DevUI before being promoted to a real deployment.

Fixes #7344.

Description & Review Guide

Two prior attempts exist for this issue (#7352 and #7355); both were closed by their authors (one a literal duplicate of the other) without maintainer review. This PR takes the smaller of the two approaches:

• What are the major changes?

  • _executor.py (_execute_agent): read function_invocation_kwargs from the request and merge it into the kwargs passed to agent.run(). Accepts both channels already present on the request payload:
    • extra_body.function_invocation_kwargs — the channel already used for response_id and checkpoint_id in this file
    • a top-level extra field — AgentFrameworkRequest has model_config = ConfigDict(extra="allow"), so a top-level function_invocation_kwargs key was already accepted (and silently dropped, which is what the issue reporter originally tried)
  • Top-level takes precedence when both are set. Missing or non-dict values are silently ignored for backward compatibility.
  • tests/devui/test_execution.py: parametrized regression test asserting the kwarg reaches run() via both channels, and is not forwarded at all when absent.

• What is the impact of these changes?

  • Additive and backward compatible. No AgentFrameworkRequest model change, no frontend changes — only the existing DevUI /v1/responses agent execution path gains forwarding behavior. When the field is absent, behavior is unchanged.

• What do you want reviewers to focus on?

  • Whether accepting the value from both extra_body.function_invocation_kwargs and a top-level model_extra field is desired, or extra_body alone (the prior extra_body-only attempt in Python: Forward function_invocation_kwargs through DevUI to agent.run… #7352 may be what maintainers prefer; easy to narrow).
  • Whether forwarding should also be added to the workflow execution path (_execute_workflow) — intentionally left out of this PR since the issue is specifically about per-tool invocation context on the agent path.

Related Issue

Fixes #7344

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

Pull request overview

Forwards request-scoped function invocation arguments from DevUI requests to agent tool invocations.

Changes:

• Supports nested and top-level function_invocation_kwargs.
• Adds regression coverage for both channels and omitted values.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
python/packages/devui/agent_framework_devui/_executor.py	Forwards validated invocation kwargs to agent.run().
python/packages/devui/tests/devui/test_execution.py	Tests forwarding and absence behavior.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

Python Test Coverage Report •

File	Stmts	Miss	Cover	Missing
TOTAL	47338	4369	90%

report-only-changed-files is enabled. No files were changed during this commit :)

Python Unit Test Overview

Tests	Skipped	Failures	Errors	Time
9643	36 💤	0 ❌	0 🔥	2m 33s ⏱️