Skip to content

[Bug]: The guard blocks the user for changing scope #37

Description

@shahidbeig-a11y

What happened?

Codex will activelt refuse to do something because the hook labels its instructions as developer instructions which outrank user instructions. As a result, I am completely blocked from an agent doing anything because the hook forbid tool use. This should be a funnel and not a block. For the tool to recognize that the bash command was used read only and still issue block instructions is concerning when the agent refuses to use any tools after scopey issues the hook.

Reproduction

Ask Sol on High to perform a read only review with no tool use and to write it's report to a .md doc. Sol will run bash command to read and scopey will issue the no tool verdict which will then lead to sol not writing the report.

Scopey version or commit

Document v0.2.1

Harness

Codex

Environment

Rust

Data safety

  • I removed credentials, private prompts, transcripts, and personal data.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions