6 ms·

Yeah this has been my experience as well. The Claude Code UI is still so much better, and the permissioning policy system is much better. Though I'm working on

Yeah this has been my experience as well. The Claude Code UI is still so much better, and the permissioning policy system is much better. Though I'm working on closing that gap by writing a custom policy https://github.com/openai/codex/blob/main/codex-rs/execpolicy/README.md https://github.com/openai/codex/blob/main/codex-rs/execpolic... Kinda sick of Codex asking for approval to run tests for each test instance

rtfeldman 1y ago
You don't have to use Codex in its terminal UI - e.g. you can use it in the Zed IDE out-the-box: https://zed.dev/blog/codex-is-live-in-zed https://zed.dev/blog/codex-is-live-in-zed
- PantaloonFlames 1y ago
  And also in emacs or neovim https://xenodium.com/introducing-acpel https://xenodium.com/introducing-acpel
mmaunder 1y ago
Ah the tension between cybersecurity best practices and productivity is brutal right now.
- maherbeg 1y ago
  lol yeah, but mostly just want to allow more types of reads for getting context, and primarily for test running / linting etc. I shouldn't have to approve every invocation of `pytest` or `bazel test`.
  - fragmede 1y ago
    --dangerously-bypass-approvals-and-sandbox isn't enough for you?
    - maherbeg 1y ago
      I don't want unlimited writes. I basically want to unlock nearly everything but approve writes in some scenarios.
      - fragmede 1y ago
        Where do unix permissions and a different user and extended attributes fall short for that?