[53, 54] Can I use purpose or id in the item get --fields?

Yes, that would help.

Suggestions are in my first post in this topic.

Oh, it seems that I misunderstood you here. My answer was related to editing items more granularly, while your question actually is related to filtering fields on different attributes.
While filtering on PURPOSE and ID is definitely on the roadmap, there are a couple of ways to achieve this in the current version of the CLI too.
For example op read op://<your-vault>/<your-item>/<your-field> accepts both names and IDs, while op item get --fields <field-id> should be able to retrieve a field by UUID as well. However, this are only workarounds, and we are working towards developing a more user-friendly way to do this.
Does this help in your use case? Do you have any specific suggestions towards how you would like this functionality to be integrated in the CLI?

Best,
Horia

--otp works great!

I wish there was something similar for username/password, since labels are not safe.

I don't understand how templates play a role here?

(I only want to fetch username and password for this particular use case)

Hey XIII , and thank you for trying out our beta!

Being able to edit items more granularly is definitely on our roadmap. Currently, the way we envision this is by making use of template files, and allowing users to edit and pipe their jsons to op item edit directly, in the same fashion op item create --template works. Would this work for your use-case? Do you have any suggestions that would help you in your workflow?

For the second part of the question: starting from 2.0.0-beta.10, the command op item get features a --otp flag, which has a behaviour similar to 1Password CLI 1's op get totp. Let us know if this helps, or if you have any suggestions.

Thanks for the input, and keep the feedback coming! We're here to listen and to help.

Best,
Horia