CLI 2: op run removes colors, ignores terminal size

Thanks for sharing seanboult!

Jack

Just wanted to share for those here it's possible to set the environment variable FORCE_COLOR for most programs to force color output.

Not quite sure about the compatibility from program to program but it works for node based loggers 😅.

However, it seems to be working now in my contrived test somehow without --color or FORCE_COLOR 😬.

Hi @lukany:

We don't have anything to share just yet, so please keep an eye out for updates.

seanboult:

That's exactly right, support for the --color flag will depend on the program you're running. 1Password CLI masking secrets means that to the run program, it's no longer considered a terminal-type output, so generally tools that use auto-detection to decide whether or not to send colors will default to no color. If a program has a "force color" flag or similar, that should generally work with op run .....

Jack

Wait maybe it's really only the downstream program needing support cause this seems to work for me.

Looking for this feature as well and here is example of where both programs seem to need to handle this.

Pass a color flag to watch and npm and that seems to let watch handle colors correctly, maybe the CLI needs something similar?
watch --color npm start --color always

So I'd imagine we'd want 1password CLI to support a --color flag.

Hi @"Horia.Culea_1P", has there been any progress? I am also using op run with a tool where I'd really appreciate coloured output.

+1

Hey Rotendahl,

We currently have a ticket tracking this very problem internally. Although not our top focus, we will try to prioritise it between our development cycles. We'll keep the thread updated with any progress on this!

Best,
Horia

I'm having the same problem.
I would really prefer having the output masked, but removing the colours from for instance compile output makes it hard to find errors.

Great! Let us know if we can help with anything else.