Add goose-2fa extension

[eachann1024]

Description

Goose 2FA: a single-command local 2FA vault with list/grid, copy/paste, QR scanning, JSON import/export, and an optional shared file. English is the default; Simplified Chinese is an opt-in preference.

Updates for review

• Self-contained vendor source fixes missing imports in the earlier submission.
• HOTP delivery rejects stale/concurrent counters and does not treat another writer's identical content as a successful save.
• Shared-file corrections use version-checked writes; a new data source never overwrites an existing file.
• Added an English README and an initial-release changelog.

Validation

• npm run build and npm run lint pass locally on macOS.
• 20 focused file/vault tests pass. Raycast UI and cross-device syncing were not exercised.

Security and review notes

Shared JSON and exported backups contain plaintext 2FA secrets; users choose their own trusted location. The Swift helper is built from included source. Custom language switching may need adjustment under the Store's English-only guidance. Store screenshots are not included yet.

[raycastbot]

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Confidence Score: 4/5

[Medium risk] New two-factor authentication extension with local secret storage.

The PR is not ready to merge until the view command has the required screenshots.

Findings

1.  This repository requires every extension with a view command to include a metadata/ folder with Raycast-style screenshots. All three new commands use mode "view" , but this extension has no metadata/ folder. Add the required screenshots. ▶

Fix with agent prompt

### Issue 1
extensions/goose-2fa/package.json:18-22
This repository requires every extension with a view command to include a `metadata/` folder with Raycast-style screenshots. All three new commands use `mode: "view"`, but this extension has no `metadata/` folder. Add the required screenshots.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Goose 2FA adds a Raycast command for generating and delivering one-time codes, managing accounts, and importing or exporting authenticator data. An optional shared JSON file lets people use the same vault across devices, with controls for outside edits and file creation.

• Adds searchable TOTP and HOTP codes with list or grid views and copy, paste, and typing actions.
• Adds account and group management, trash and restore, QR scanning, and import previews.
• Adds optional shared-file storage alongside Raycast LocalStorage, with conflict handling and version-checked writes.
• Includes extension setup, vendor code, tests, a README, and an initial changelog.

_{Reviews (6) · Last reviewed commit: "Clarify standalone Raycast workflow and ..."}

[greptile-apps]

This repository requires every extension with a view command to include a metadata/ folder with Raycast-style screenshots. All three new commands use mode: "view", but this extension has no metadata/ folder. Add the required screenshots.

Rule Used: What: Extensions with view-type commands must include a metadata/ folder containing Raycast-styled screenshots. Why: Professional metadata images ensure extensions appear polished and consistent in the Raycast store. Good: ``` my-extension/ ├── m... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/goose-2fa/package.json
Line: 18-22

Comment:
This repository requires every extension with a view command to include a `metadata/` folder with Raycast-style screenshots. All three new commands use `mode: "view"`, but this extension has no `metadata/` folder. Add the required screenshots.

**Rule Used:** What: Extensions with view-type commands must include a `metadata/` folder containing Raycast-styled screenshots.  Why: Professional metadata images ensure extensions appear polished and consistent in the Raycast store.  Good: ``` my-extension/ ├── m... ([source](https://app.greptile.com/raycast/-/custom-context?memory=87059ac1-c601-487f-9f1c-bce8a3cb6209))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[0xdhrv]

Thanks for your contribution 🔥 The shared-file sync design and the careful conflict / HOTP handling look thoughtfully built.

We already have extensions in the Store that cover a local two-factor code vault (search accounts, copy/paste codes):

• Two-Factor Authentication Code Generator by @cjdenio
• One Time Password by @Lachero

Both let users keep OTP accounts locally and pull codes from Raycast. What this PR adds on top is shared JSON sync with uTools, QR screenshot scanning, HOTP, groups/trash, and direct typing via a Swift helper.

Could these land in one of the existing extensions instead? That keeps users in one place and makes them easier to discover. If there's a workflow that can't fit there (for example the uTools shared-file protocol), tell me which one and I'll decide quickly.

This would help avoid duplication and keep local 2FA vaults consolidated in one extension.
As mentioned in our extension guidelines here ↗