[BUG] claude command assums --print was used when it's not
Resolved 💬 4 comments Opened Sep 11, 2025 by bxm156 Closed Jan 9, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Originally reported: #6820 , butt the github-actions thought this was a duplicate and closed it prematurely.
Re-opening;
I'd like to use 1password to handle secrets instead of keeping them in my MCP config. Typically with 1password you run op run -- <cmd> to run a command in such a way that translates env vars from OP paths to values. The -- is pretty common in the CLI world when you want to use one command to kick off another command, so I expected Claude should handle this properly.
What Should Happen?
For some reason claude thinks I'm using --print. It should just run as normal.
Error Messages/Logs
Steps to Reproduce
op run -- claude
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
1.0.108 (Claude Code)
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗