feat(agents): allow session idle timeouts up to 240 minutes - #10276
Open
Deeksha Sharma (Deeksharma) wants to merge 1 commit into
Open
Deeksha Sharma (Deeksharma) wants to merge 1 commit into
Deeksha Sharma (Deeksharma) wants to merge 1 commit into
Conversation
Raise the hosted-agent idle timeout ceiling to 14,400 seconds in\nclient validation and both authoring schemas. Preserve the 120-second\nminimum and omitted-setting behavior (900-second server default).\n\nUpdate documentation and cover the old and new boundaries, API\nserialization, code deployment, and both JSON schemas. Authored-by: GitHub Copilot CLI v1.0.89 Model: GPT-6 Astra (gpt-6-astra) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9fc49c48-e2df-41d0-ae12-d852fc9653c8
|
Azure Pipelines: 3 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Copilot started reviewing on behalf of
Deeksha Sharma (Deeksharma)
October 1, 2026 08:24
View session
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The implementation consistently updates validation, schemas, documentation, and focused boundary coverage.
Review effort: Balanced
Findings: None
What changed in this PR
Raises hosted-agent session idle timeout validation from 60 to 240 minutes while preserving existing minimum and default behavior.
Changes:
- Updates both authoring schemas, models, validation, and documentation.
- Adds boundary, serialization, code-deployment, and schema tests.
- Aligns client behavior with the related Foundry contract change.
| File | Description |
|---|---|
schemas/azure.ai.agent.json |
Raises the service schema maximum. |
schemas/Agent.json |
Raises the standalone agent schema maximum. |
README.md |
Documents the new supported range. |
internal/project/doc_examples_test.go |
Tests both schema boundaries. |
internal/pkg/agents/agent_yaml/yaml.go |
Updates validation constants and comments. |
internal/pkg/agents/agent_yaml/map_test.go |
Tests mapping and wire serialization. |
internal/pkg/agents/agent_api/models.go |
Updates API model documentation. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Raise the hosted-agent session idle timeout maximum from 3,600 seconds (60 minutes) to 14,400 seconds (240 minutes).
Agent.json,azure.ai.agent.json, model comments, and README guidance.Related contract change: Azure/azure-rest-api-specs#46925
Previous minimum-bound change: #9728
Validation
From
cli/azd/extensions/azure.ai.agents:All passed. Go formatting and
git diff --checkpassed. No live Azure deployment was run.Rollout
This PR enables authoring and client-side acceptance only. Values above 3,600 seconds require the corresponding Foundry service support to be deployed. No TypeSpec dependency bump, extension release-version change, or registry update is included.
For optional live deploy regression coverage, use the
foundry-extension-scenario-orchestratoragent with thefoundry-extension-scenario-pr-regressionskill to select the relevant deploy scenarios.