-
Notifications
You must be signed in to change notification settings - Fork 46
Remove timeout requirement for strict mode and set default timeout to 20 minutes #1432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
pelikhan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot set a default timeout of 20min for Agentic workflows
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Done! Updated the default timeout to 20 minutes for agentic workflows in commit 5c4e5dc. The changes were made in three places:
Documentation updated to reflect the new 20-minute default. |
|
@copilot move default timeout to a constant in constants.go and use it instead of literal numbers in the .go compiler |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Done! Moved the default timeout to a constant in commit d8f9e3a. Added
|
|
Agentic Changeset Generator triggered by this pull request |
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Remove timeout requirement for strict mode and set default timeout to 20 minutes
Based on the problem statement, I have successfully completed:
docs/src/content/docs/reference/frontmatter.mdto remove timeout requirementdocs/src/content/docs/guides/security.mdto remove timeout requirementChanges Made:
Code Changes:
validateStrictTimeout()function call fromvalidateStrictMode()inpkg/workflow/strict_mode.govalidateStrictTimeout()function implementation (lines 36-82)pkg/workflow/strict_mode_test.go:TestStrictModeTimeout: Now tests that timeout is NOT required and is still valid when specifiedTestStrictModeFromFrontmatter: Updated to expect success without timeoutTestStrictModeIsolation: Updated to expect success for strict workflow without timeoutTestCLIStrictFlagTakesPrecedence: Updated to test write permission error instead of timeout errorDefault Timeout Changes (per user request):
DefaultAgenticWorkflowTimeoutMinutesconstant topkg/constants/constants.go(value: 20)pkg/workflow/tools.go: Changed to use constant instead of hardcoded valuepkg/workflow/claude_engine.go: Changed to use constant instead of hardcoded valuepkg/workflow/copilot_engine.go: Changed to use constant instead of hardcoded valueDocumentation Changes:
Updated
docs/src/content/docs/reference/frontmatter.md:timeout_minutes: 10from the example strict mode workflowUpdated
docs/src/content/docs/guides/security.md:timeout_minutes: 10from exampleWorkflow Files:
Testing & Validation:
Summary:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.