Limitation: codex cannot write GITHUB_STEP_SUMMARY

[pelikhan]

codex is not able to write the file pointed by GITHUB_STEP_SUMMARY.

> AI-generated content by [Test Codex](https://github.com/githubnext/gh-aw/actions/runs/16927310025) may contain mistakes.' >> "'$GITHUB_STEP_SUMMARY' in /home/runner/work/gh-aw/gh-aw
[2025-08-13T04:14:18] bash -lc "echo '## 🤖 Codex PR Summary
Error: Pull request #16927310025 not found.

> AI-generated content by [Test Codex](https://github.com/githubnext/gh-aw/actions/runs/16927310025) may contain mistakes.' >> "'$GITHUB_STEP_SUMMARY' exited -1 in 0ms:
bash: line 4: /home/runner/work/_temp/_runner_file_commands/step_summary_626a95b3-92c0-4a4c-b82a-57e6686afa4d: Permission denied
[2025-08-13T04:14:18] tokens used: 14608

https://github.com/githubnext/gh-aw/actions/runs/16927310025/job/47965557571#step:8:208

[github-actions]

🎯 Agentic Issue Triage

Summary

This issue reports that the Codex engine cannot write to the GITHUB_STEP_SUMMARY file in GitHub Actions workflows, failing with "Permission denied" error. This prevents Codex workflows from generating job summaries.

📋 Technical Analysis

Error Details

• Engine: Codex (OpenAI)
• Command: echo '...' >> "$GITHUB_STEP_SUMMARY"
• Error: Permission denied when writing to temporary step summary file
• File Path: /home/runner/work/_temp/_runner_file_commands/step_summary_626a95b3-92c0-4a4c-b82a-57e6686afa4d
• GitHub Actions Run: 16927310025

Impact

• Codex workflows cannot generate job summaries
• Breaks workflow transparency and reporting capabilities
• May affect workflow completion status reporting

🔧 Debugging Strategies

Immediate Investigation Steps

1. Check file permissions:

   ls -la "$GITHUB_STEP_SUMMARY"
   stat "$GITHUB_STEP_SUMMARY"

2. Verify directory permissions:

   ls -la "$(dirname "$GITHUB_STEP_SUMMARY")"

3. Test write access:

   touch "$GITHUB_STEP_SUMMARY.test" && rm "$GITHUB_STEP_SUMMARY.test"

Potential Root Causes

• File ownership: Step summary file may be owned by different user/process
• Directory permissions: Parent directory may have restrictive permissions
• GitHub Actions runner environment: Issue with runner setup or environment variables
• Codex engine execution context: Process may be running with different privileges

Alternative Approaches

• Use tee instead of redirection: echo '...' | tee -a "$GITHUB_STEP_SUMMARY"
• Check if file exists and is writable before attempting write
• Use temporary file and copy approach if direct write fails

🧪 Reproduction Steps

To Reproduce

1. Set up a GitHub Actions workflow using Codex engine
2. Configure workflow to write to GITHUB_STEP_SUMMARY
3. Execute workflow and observe permission error

Test Environment Requirements

• GitHub Actions runner (ubuntu-latest)
• Codex engine configuration
• Workflow attempting to write job summary

Verification Steps

1. Check if issue is specific to Codex engine vs other engines (Claude, Gemini)
2. Test with different GitHub Actions runner environments
3. Verify if issue occurs consistently or intermittently

📚 Resources & Documentation

GitHub Actions Step Summary

• Creating job summaries
• GITHUB_STEP_SUMMARY environment variable

Related GitHub Issues

• GitHub Actions: Permission denied writing to step summary
• Step summary file permissions in self-hosted runners

Debug Tools

• GitHub Actions debugging: Add ACTIONS_STEP_DEBUG: true to workflow
• Runner diagnostics: Check runner logs for permission-related warnings

💡 Implementation Ideas

Short-term Fixes

1. Defensive programming: Check file writability before attempting write
2. Error handling: Gracefully handle permission errors with fallback behavior
3. Alternative output: Use standard output if step summary fails

Long-term Solutions

1. Permission management: Ensure proper file ownership/permissions in workflow setup
2. Cross-engine consistency: Standardize step summary handling across all engines
3. Testing: Add automated tests for step summary functionality across engines

Task Breakdown

• Investigate file permission differences between engines
• Add error handling for step summary write failures
• Test alternative write methods (tee, temporary files)
• Create unit tests for step summary functionality
• Document step summary usage patterns for different engines

AI-generated content by Agentic Triage may contain mistakes.

[dsyme]

Moving to a later milestone

[dsyme]

We have moved to deterministic logs rather than self-reporting AI logs