Skip to content

[codex] Document Windows print-mode issue #2

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.

Sign up for GitHub

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

Merged
sysCat64 merged 1 commit into from
Jun 20, 2026
Merged

[codex] Document Windows print-mode issue #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,12 @@ plugins/codex-agy-plugin/scripts/agy-print.sh -- "-starting prompt text"
For review and second-opinion requests, Codex should ask `agy` to return findings only and not modify files.
For release-readiness or repeated reviews, Codex should pass a blocker-only prompt: report only High/Medium issues that can break install, runtime, validation, CI, or distribution; return `APPROVED` when there are no blockers.

## Known Issues

On Windows, there is a report that `agy --print` can exit with code `0` but produce empty stdout when launched from Codex/non-interactive PowerShell, while the same command works from an interactive PowerShell session. See [Issue #1](https://github.com/sysCat64/codex-agy-plugin/issues/1).

This plugin relies on `agy --print` writing the final response to stdout. It does not read Antigravity internal transcript or log files as a fallback because those files are not a stable integration boundary.

## Validate

```bash
Expand Down
Loading