.NET & Python: [Durable Agents] Automatic thread/session cleanup TTL
Maintainers usually reply within 3 days
@larohra is already working on this.
Since Jul 13, 2026.
Assessment
This issue has not been assessed yet.
Description
The Durable Task extension for Agent Framework ("Durable Agents") provides built-in thread storage. However, there's no clear way to cleanup the thread storage data, which will accumulate in either the Azure Storage account or in the Durable Task Scheduler resource owned by the user.
This issue tracks a proposal to create configurable TTLs on durable agents that allow them to be "garbage collected" if there aren't any interactions after a period of time. For example, if a particular agent session is idle for 30 days, the underlying entity state (e.g., the conversation history) gets deleted. Each new interaction with the agent would reset the TTL. Any messages to an "expired" agent session will result in a new conversation history.
This is needed for each language we support:
- .NET
- Python
- Dominant language
- Python
- Stars
- 19
- Forks
- 11
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from microsoft/agent-framework-durable-extension
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/agent-framework-durable-extension#87 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/agent-framework-durable-extension#75 · 1 comment ·
Maintainers usually reply within 3 days
-
.NET: [Guide] Running Durable Agents & Workflows inside Foundry Hosted Agents across scale-to-zeroOpen
Difficulty 5/5 Over a week Newbie friendliness 22/100
microsoft/agent-framework-durable-extension#149 ·
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
microsoft/agent-framework-durable-extension#143 ·
Maintainers usually reply within 3 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/agent-framework-durable-extension#122 ·
Maintainers usually reply within 3 days
All issues in microsoft/agent-framework-durable-extension
Similar issues
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog checkPossibly taken @ocelotl claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-telemetry/opentelemetry-python#5825 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cuga-project/cuga-agent#1020 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
microsoft/playwright#43640 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
stac-utils/stac-fastapi-elasticsearch-opensearch#965 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day