Repository navigation
fix(agent): a fenced folder no longer closes folders that start with its name - #255
Merged
Merged
Conversation
…its name The Codex fence matched by text, so a crew named Suite fenced Suite2\Ana and the agent's edits there were refused without a card. The folder name has to end where the fence ends. Spec 30.4 records what was seen with the real Codex on 2026-10-10, and that file reads stay open.
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.
A real Codex run found that the fence matched folders by text: with crews
SuiteandSuite2, an agent inSuite2had its edits refused without a card. The folder name now has to end where the fenced path ends (Suite2,Suite.oldare other folders).Spec 30.4 records what was seen with the real Codex (suggest_bot, browser, desktop without a grant, messages and tasks, deny/allow, plan mode) and the findings on reads: a permission profile needs the elevated Windows sandbox and breaks new folders, so reads stay open.
Checks: unit test for look-alike names;
cargo clippy/fmtpass.Manual step: with two crews named like
DocsandDocs 2, ask a Codex agent in the second to create a file and see the approval card.