Repository navigation
Conversation
muguetdev
pushed a commit
to muguetdev/agent-office
that referenced
this pull request
Oct 27, 2026
…#376 and AgentSystemLabs#280) Codex runs its lifecycle hooks through cmd.exe or PowerShell on Windows, where the POSIX-quoted command never ran. Each hook is now an encoded PowerShell command that keeps the paths literal, pipes the hook its stdin as UTF-8 with PowerShell's progress output off (Agent Office AgentSystemLabs#376), and exits with the hook's own code (Agent Office AgentSystemLabs#280). From AgentSystemLabs#280 too: a building holds up to 32 project floors, not 16. Co-authored-by: schnepg1 <61694790+schnepg1@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codex workers on native Windows fail lifecycle hooks every turn because Office emits POSIX single-quoted commands. PowerShell does not invoke a quoted executable without its call operator, and Command Prompt does not recognize those quotes.
Generate an encoded PowerShell command on Windows, preserve UTF-8 stdin, quote paths literally, and suppress module progress output. POSIX commands retain their current quoting. Document how existing workers receive the updated commands.
Validation: