[azure-ai-agentserver-responses] get_history_item_ids uses resolved[:limit] — truncates newest history instead of oldest

[arychin]

Bug Report

Package: azure-ai-agentserver-responses
Version: 1.0.0b9 (also present in b10)
Python: 3.14

Description

get_history_item_ids() in both InMemoryResponseProvider and FoundryResponseProvider
truncates history from the wrong direction. It uses resolved[:limit] which keeps the
oldest N items and drops the newest — the opposite of correct behavior for
conversation history.

Affected files

• azure/ai/agentserver/responses/store/_memory.py
• azure/ai/agentserver/responses/store/_foundry_provider.py (same pattern)

Expected behavior

resolved[-limit:] — keep the most recent N items, drop the oldest.

Actual behavior

resolved[:limit] — keeps the first N items (oldest), drops recent turns.

Impact

In multi-turn hosted agents (20+ turns), the agent loses visibility of recent
user messages, feedback, and decisions. It retains old context (initial setup)
but can't see what just happened — causing it to repeat steps or ignore recent
user input. The default default_fetch_history_count=100 makes this trigger
around turn 25-30 in tool-heavy workflows.

Workaround

Set ResponsesServerOptions(default_fetch_history_count=500) to delay the
truncation, but this doesn't fix the direction bug.

Suggested fix

# _memory.py , _foundry_provider.py equivalent
return resolved[-limit:]  # keep newest N, not oldest N

Suggested labels

bug, Hosted Agents, Client

[github-actions]

Thank you for your feedback. Tagging and routing to the team member(s) best able to assist.

//cc: Shiva S (@Shivakishore14) Ankit Sinha (@ankitbko) Pranav Pandit (@vangarp) Ravi Pidaparthi (@RaviPidaparthi)

[github-actions]

🎯 Agentic Issue Triage

Summary: get_history_item_ids() in both InMemoryResponseProvider and FoundryResponseProvider uses resolved[:limit] instead of resolved[-limit:], causing conversation history to truncate the newest turns rather than the oldest — breaking multi-turn hosted agents.

📋 Issue Details

Package: azure-ai-agentserver-responses v1.0.0b9 / b10
Affected API: get_history_item_ids() in InMemoryResponseProvider and FoundryResponseProvider
Scenarios:

• Multi-turn hosted agents (20+ turns) lose visibility of recent user messages, feedback, and decisions
• With default_fetch_history_count=100, truncation begins around turn 25–30 in tool-heavy workflows

Root ask: Fix the slice direction: resolved[:limit] → resolved[-limit:] to keep the most recent N items

🔎 Debugging / Reproduction Notes

The bug is a straightforward off-by-one in slice direction. Both affected files use resolved[:limit] (keeps oldest N items), where the correct behavior is resolved[-limit:] (keeps newest N items).

Suggested investigation steps:

1. Reproduce by running a 25–30 turn conversation with default_fetch_history_count=100 and observing the agent replaying old context
2. Apply resolved[-limit:] in azure/ai/agentserver/responses/store/_memory.py
3. Apply the same fix in azure/ai/agentserver/responses/store/_foundry_provider.py
4. Verify that after fix the agent correctly sees recent turns and drops the oldest ones

🏷️ Label Confidence

• Category: Client — azure-ai-agentserver-responses is a data-plane client library under /sdk/agentserver/
• Service: Hosted Agents — matches the CODEOWNERS description sdk/agentserver/* and the PRLabel %Hosted Agents associated with the agentserver path
• Confidence: High — package name, affected files, and SDK path all unambiguously point to this label pair

👥 Owner Routing

• Matched CODEOWNERS entry: # ServiceLabel: %Hosted Agents (line 282) — only ServiceLabel entry matching "Hosted Agents" in a bottom-to-top scan
• AzureSdkOwners: none listed
• ServiceOwners: @Shivakishore14, @ankitbko, @vangarp, @RaviPidaparthi
• Routing action: Added "Service Attention" and "needs-team-attention"; ServiceOwners pinged via routing comment
• Scan notes: No other # ServiceLabel: %Hosted Agents entries exist in CODEOWNERS; a path-specific entry at line 280 (azure-ai-agentserver-ghcopilot) was skipped as it is not a ServiceLabel entry

Generated by Agentic Triage for issue #48514 · 33.4 AIC · ⌖ 5.7 AIC · ⊞ 9.6K · ◷

[kashifkhan]

Thank you for the feedback Achintya Tiwary (@arychin) . Ill forward this to the right folks that can help you further