Add --timeout option to logs command for MCP server timeout prevention

[Copilot]

Problem

The logs command can take a long time to download workflow artifacts, especially when fetching logs for multiple runs or workflows with large artifacts. When running as an MCP server, this can cause timeouts that prevent the tool from completing successfully.

Solution

This PR adds a --timeout option to the logs command that limits execution time by stopping the download process when the specified time limit is reached. Any runs that were successfully downloaded before the timeout are processed and returned, providing partial results rather than failing completely.

Key Changes

• New --timeout flag: Accepts timeout value in seconds (0 = no timeout, default)
• MCP server integration: Automatically sets a 50-second timeout when running as an MCP tool
• Graceful degradation: Returns partial results if timeout is reached instead of failing
• Backward compatible: When timeout is not specified, behavior is unchanged

Implementation Details

The timeout is implemented using time.Since() to track elapsed time at the start of each download iteration. When the elapsed time exceeds the specified timeout:

1. The download loop exits immediately
2. Any already-downloaded runs are processed normally
3. A message indicates how many runs were processed before timeout
4. The command returns successfully with partial results

In the MCP server, the logs tool automatically applies a 50-second timeout unless explicitly overridden via the timeout parameter in the tool arguments.

Usage Examples

Command Line:

# Download logs with 50 second timeout
gh aw logs --timeout 50

# Combine with other filters
gh aw logs --timeout 60 -c 10 --engine claude -v

MCP Server:

{
  "workflow_name": "test-workflow",
  "count": 10
  // Uses 50 second timeout by default
}

Or override the default:

{
  "workflow_name": "test-workflow",
  "count": 10,
  "timeout": 120
}

Testing

• Added comprehensive unit tests for timeout functionality
• Updated existing tests to maintain compatibility
• All tests pass successfully
• Verified MCP server integration

Fixes the issue where long-running log downloads could timeout when running as an MCP server.

Original prompt

Add option to "logs" command, --timeout, to limit the tool execution to a specified number of seconds. The goal is to prevent timeouts when running as mcp. When the time is up, stop downloading runs and process them.

Set timeout to 50 seconds when running in the mcp server.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[pelikhan]

@copilot

• add the --tool-timeout on mcp-server command to set the logs timeout
• the compiler should configure the gh-aw mcp server with the timeout from the engine

[github-actions]

Agentic Changeset Generator triggered by this pull request.