Tweak: claude run error state propagation

[pelikhan]

The claude log contains a final result message with the error state of the agent cli. This flag is currently ignored by our plumbing code.

The generated code in the lock.yml file should scan the output log and fail the action if the agent cli is an error state.

[github-actions]

🎯 Agentic Issue Triage

This issue reports a bug where Claude CLI error states are not being properly propagated to GitHub Actions, causing workflows to pass when they should fail.

Technical Analysis

Problem: The current workflow generation in lock.yml files ignores the Claude CLI's final result message that contains error state information. This means failed agent runs appear as successful GitHub Actions.

Impact:

• Failed agentic workflows may appear successful in GitHub Actions
• Downstream processes may continue when they should stop
• Reduced reliability of automated workflows
• Difficult to debug actual CLI failures vs successful runs

Root Cause: Missing error state parsing and propagation in the generated GitHub Actions workflow files.

Implementation Strategy

Recommended Approach:

1. Log Parsing Enhancement

   • Add error state scanning to the generated lock.yml workflow files
   • Parse Claude CLI output for final result messages
   • Extract error state indicators from the log output

2. Action Failure Propagation

   • Implement proper exit code handling in the workflow steps
   • Use GitHub Actions workflow commands to signal failure states
   • Ensure error messages are clearly visible in workflow logs

3. Testing Strategy

   • Create test scenarios with intentional Claude CLI failures
   • Verify workflow correctly fails when CLI reports errors
   • Test both successful and failed CLI runs

Example Implementation Pattern:

# In generated lock.yml
- name: Run Claude Agent
  run: |
    claude-cli run ... 2>&1 | tee /tmp/claude-output.log
    
    # Check for error patterns in output
    if grep -q "ERROR\|FAILED\|Agent CLI error state" /tmp/claude-output.log; then
      echo "::error::Claude CLI reported error state"
      exit 1
    fi

Related Areas

Files Likely Affected:

• Workflow generation logic in Go codebase
• lock.yml template files
• CLI output parsing utilities
• GitHub Actions step implementations

Testing Areas:

• Error state detection
• Workflow failure propagation
• Log parsing accuracy
• GitHub Actions integration

Resources & Documentation

Relevant Resources:

• GitHub Actions: Workflow commands
• GitHub Actions: Setting exit codes
• Bash exit codes and error handling

Similar Issues: Issue #85 discusses post-job error handling patterns that could inform this implementation.

AI-generated content by Agentic Triage may contain mistakes.

[pelikhan]

@dsyme as part of the agentic refactoring: extract error state from log?

[dsyme]

This was fixed by @pelikhan I believe