If you call claude -p from inside Codex and get Not logged in · Please run /lo… · @qi9098 · TwKit

@qi9098

If you call claude -p from inside Codex and get Not logged in · Please run /login you're probably still logged in. Codex runs commands in a sandbox by default. On macOS, the sandbox blocks Claude Code from reading its login in Keychain and ~/.claude. So it fails in under a second. I keep Codex on Approve for me instead of full access, because I think it's safer. When I let the same command run outside the sandbox, it worked right away. Codex doesn't notice this by itself while it's in the sandbox. If you don't want to approve it every time, the Codex rules docs say you can put a .rules file in ~/.codex/rules/ with one line: prefix_rule(pattern=["claude"], decision="allow") allow means it runs outside the sandbox without asking you. Rules are still experimental, and that command loses the sandbox protection. cursor-agent and grok break in the Codex sandbox for the same reason, just with different errors 😂

曝光 24 · 评论 0 · 点赞 0 · 书签 0