Skip to content

Align hosted Foundry Memory update behavior - #2

Merged
shibayan merged 1 commit into
masterfrom
codex/remove-hosted-memory-wait
Aug 27, 2026
Merged

Align hosted Foundry Memory update behavior#2
shibayan merged 1 commit into
masterfrom
codex/remove-hosted-memory-wait

Conversation

@shibayan

Copy link
Copy Markdown
Member

Removes the request-level memory update wait middleware from the TypeScript hosted sample, keeps asynchronous extraction off the response path, and aligns the documentation with the .NET hosted sample. Validation: npm run typecheck and npm run build.

@shibayan
shibayan requested a lite review from Copilot August 27, 2026 08:58
@shibayan shibayan self-assigned this Aug 27, 2026
@shibayan shibayan added the enhancement New feature or request label Aug 27, 2026
@shibayan
shibayan merged commit 26a8355 into master Aug 27, 2026
@shibayan
shibayan deleted the codex/remove-hosted-memory-wait branch August 27, 2026 08:59

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the TypeScript hosted Foundry Memory sample to avoid waiting on memory extraction as part of the request lifecycle, aligning runtime behavior and documentation with the .NET hosted-agent sample.

Changes:

  • Removed the request-level middleware that awaited FoundryMemoryProvider.whenUpdatesCompleted() after agent runs (including streaming).
  • Updated the local-scope error guidance to clarify when x-agent-user-id is expected and how it’s injected in Foundry.
  • Revised README guidance to reflect asynchronous extraction (including a short delay before verifying newly taught memories) and clarified the per-user scoping equivalence to .NET.

Reviewed changes

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

File Description
samples/typescript/hosted-agents/agent-framework/responses/13-foundry-memory/src/main.ts Removes the memory-update wait middleware so extraction stays off the response path; updates the missing-user-scope error message.
samples/typescript/hosted-agents/agent-framework/responses/13-foundry-memory/README.md Aligns documentation and examples with asynchronous memory extraction and .NET scoping semantics.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants