microsoft / microsoft/agent-framework
.NET: agent-hooks: bounded-exposure incremental streaming mode (buffered_output: false)
@westey-m is already working on this.
Since Aug 18, 2026.
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
Follow-up from #7564 (same thread): the full answer to streaming UX for long-running agents under enforcement is the spec's sanctioned incremental mode — AGENT-HOOKS-0.1 §12.1's exception for hosts declaring buffered_output: false with a stated exposure bound (four normative conditions: verdict-covered release within the bound; terminating deny withholds the unreleased remainder including withheld-but-permitted content; fail-closed residue; §6.1-gated durability). A worked implementation pattern exists (rune-range exposure accounting, agent-control-spec spec §18.1, engine/src/stream_session.rs).
Substantially larger than the fast path (separate issue) and applies to both Python and .NET implementations. The CTK ships capability-gated vectors for this surface (AH-CTK-110..113), so an implementation lands with conformance coverage ready.
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.