Two feature requests: 2FA recovery codes and per-project secrets management

Hi 1Password team,

Long-time user, two requests that would make a real difference in how we work.

1. Recovery codes as a first-class field

Right now 2FA recovery codes end up in notes fields or a separate item, and there's no way to track which ones have been used. I'd like a dedicated recovery codes section on login items where I can paste a set of codes, mark each one as used, see how many are left, and replace the whole set when a provider rotates them. Today it's easy to lose track of which codes are still valid.

2. Project-scoped developer secrets

I manage keys and secrets for several companies, each with multiple projects, each running across environments (dev, tst, stg, prd). The current vault and tag model doesn't fit that shape. The workaround is prefixing every item name with company, project and environment, which is unfriendly to developers and breaks down fast. What I'd want:

• Group secrets by organization > project > environment, with that hierarchy visible and filterable in the app and the CLI.
• Store and version a .env file per project per environment, and inject it with op run without hand-building a template.
• Filter and search by project, environment, or secret type (API key, DB credential, token, certificate).
• See at a glance which projects a given key is used in, and diff one environment against another so a missing variable in prd is obvious.
• Share a whole project or environment with a team in one step, rather than item by item.

The goal is to open one project and see every secret it needs across every environment, instead of hunting through vaults.

Happy to walk through my setup or test anything early.

Thanks,