-
Notifications
You must be signed in to change notification settings - Fork 2.1k
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
.NET: [Bug]: Inner agent failure does not fail workflow in declarative workflow
.NETUsage: [Issues, PRs], Target: .NetUsage: [Issues, PRs], Target: .NetStatus: Open.Python: [Bug]: Foundry Agent client spans are not showing up in Foundry tracing UI
foundryUsage: [Issues, PRs], Target: all Foundry integrationsUsage: [Issues, PRs], Target: all Foundry integrationshostingUsage: [Issues, PRs], Target: all hosting related solutionsUsage: [Issues, PRs], Target: all hosting related solutionsobservabilityUsage: [Issues, PRs], Target: observability related featuresUsage: [Issues, PRs], Target: observability related featurespythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythonStatus: Open.#7492 In microsoft/agent-framework;Python: [Bug]: AG-UI
MESSAGES_SNAPSHOTre-factors streamed messages under fresh ids — the reference@ag-ui/clientmerge then renders every mid-run tool call after the final textneeds-maintainer-triageUsage: [Issues], Target: all issues that the automated triage flow failed to processUsage: [Issues], Target: all issues that the automated triage flow failed to processpythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythontriageUsage: [Issues], Target: All issues that still need to be triagedUsage: [Issues], Target: All issues that still need to be triagedStatus: Open.Python: [Bug]: with
predict_state_configset, EVERY tool result emits a fullStateSnapshotEvent— including for tools the config never namesneeds-maintainer-triageUsage: [Issues], Target: all issues that the automated triage flow failed to processUsage: [Issues], Target: all issues that the automated triage flow failed to processpythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythontriageUsage: [Issues], Target: All issues that still need to be triagedUsage: [Issues], Target: All issues that still need to be triagedStatus: Open..NET: [Feature]: Add tool search capability and sample
.NETUsage: [Issues, PRs], Target: .NetUsage: [Issues, PRs], Target: .NetfoundryUsage: [Issues, PRs], Target: all Foundry integrationsUsage: [Issues, PRs], Target: all Foundry integrationshostingUsage: [Issues, PRs], Target: all hosting related solutionsUsage: [Issues, PRs], Target: all hosting related solutionsStatus: Open.#7489 In microsoft/agent-framework;Python: [Bug]: Foundry Hosted agent - delay before final response when streaming
pythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythontriageUsage: [Issues], Target: All issues that still need to be triagedUsage: [Issues], Target: All issues that still need to be triagedStatus: Open.Python: [Bug]: Duplicate function call in Foundry Hosted agent when streaming
needs-maintainer-triageUsage: [Issues], Target: all issues that the automated triage flow failed to processUsage: [Issues], Target: all issues that the automated triage flow failed to processpythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythontriageUsage: [Issues], Target: All issues that still need to be triagedUsage: [Issues], Target: All issues that still need to be triagedStatus: Open.Python: [Bug]: Encrypted content is not supported with this model for GPT-4.1 model
needs-maintainer-triageUsage: [Issues], Target: all issues that the automated triage flow failed to processUsage: [Issues], Target: all issues that the automated triage flow failed to processpythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythontriageUsage: [Issues], Target: All issues that still need to be triagedUsage: [Issues], Target: All issues that still need to be triagedStatus: Open.#7483 In microsoft/agent-framework;.NET: [Bug]: Sample can make endless "loop" resulting in Millions on tokens spent if you do not terminate process yourself :-(
.NETUsage: [Issues, PRs], Target: .NetUsage: [Issues, PRs], Target: .NetagentsUsage: [Issues, PRs], Target: Single agentUsage: [Issues, PRs], Target: Single agentStatus: Open.Python: RedisHistoryProvider ignores source_id in its key, so two providers on one session share and overwrite each other's history
agentsUsage: [Issues, PRs], Target: Single agentUsage: [Issues, PRs], Target: Single agentpythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythonStatus: Open.#7471 In microsoft/agent-framework;Python: RedisHistoryProvider: max_messages=0 retains every message instead of none
agentsUsage: [Issues, PRs], Target: Single agentUsage: [Issues, PRs], Target: Single agentpythonUsage: [Issues, PRs], Target: PythonUsage: [Issues, PRs], Target: PythonStatus: Open.#7469 In microsoft/agent-framework;.NET: Suggesting adding mem0sharp samples
.NETUsage: [Issues, PRs], Target: .NetUsage: [Issues, PRs], Target: .NetmemoryUsage: [Issues, PRs], Target: memory related featuresUsage: [Issues, PRs], Target: memory related featuresStatus: Open.#7467 In microsoft/agent-framework;