microsoft / microsoft/agent-framework
Python: Clarify request info naming and HITL event filtering
Open
Nobody has claimed this yet.
orchestration
python
workflows
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
Summary
The "request info" naming is unclear, and users need better control over which events trigger HITL pauses.
Files
| File | Line | Concern |
|---|---|---|
sample: sequential_agents.py |
with_request_info() |
Name is unclear, need explicit HITL filtering |
Context
# TODO: change name with request info / make explicit that function approval will still bubble up
# The request_info name is not clear enough
# Should we add a filter on event types to pause to ask for HITL
workflow = SequentialBuilder().participants([writer, reviewer]).with_request_info().build()
Issues:
- "request_info" does not clearly convey its purpose (human-in-the-loop)
- Function approval events bubble up but this is not explicit
- No way to filter which event types trigger HITL pauses
Action Items
- Rename
with_request_info()to something clearer (e.g.,with_human_approval(),with_hitl()) - Document that function approval events bubble up through nested workflows
- Add event type filtering for HITL (e.g.,
with_hitl(event_types=[...]))
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.