Update teak-raycast extension

[praveenjuge]

Description

• Save to Teak — new fallback command that captures text or URLs from Raycast root search (no-view, accepts an optional text argument).
• Save Selected Text — new command that sends the text currently highlighted in any app to Teak.
• Browse Tags — new view command that lists every tag with per-tag card counts and drills into cards by tag.
• AI tools — three new tools for Raycast AI:
  • Get Recent Teak Cards — fetch the newest cards without a query.
  • List Teak Tags — list the user's tags with counts.
  • Toggle Favorite — favorite or unfavorite a card by id.

Updated the ai.instructions block so the model picks the right tool for each action, and confirms before mutating.

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for the update! 🎉

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

[greptile-apps]

Greptile Summary

This PR adds five new commands (Save to Teak, Save Clipboard, Save Selected Text, Save Current Browser Tab, Browse Tags), three new AI tools (Get Recent, List Tags, Toggle Favorite), and refactors the core API layer to accept structured input objects rather than positional arguments.

• capture.ts shared helper sets toast.primaryAction and toast.secondaryAction ("Open Card" / "Open Source URL") and then immediately calls showHUD, which closes Raycast before the user can interact with those actions \u2014 the same dead-action pattern also appears in quick-save.tsx via addSuccessActions.
• CHANGELOG.md uses {PR_MERGED_AT} instead of the standard {PR_MERGE_DATE} placeholder that is substituted automatically on merge.
• save-text.ts manually defines Arguments and LaunchProps types that are auto-generated in raycast-env.d.ts, which can drift out of sync with package.json.

Confidence Score: 3/5

The new save commands will work, but users of every no-view capture path and the quick-save form will never see the "Open Card" / "Open Source URL" toast actions because showHUD dismisses Raycast before they can interact with them.

All five new save commands funnel through saveCardWithFeedback, which wires up toast actions and then immediately calls showHUD. Because showHUD closes Raycast, those actions are permanently inaccessible on every happy path — a meaningful UX regression for the newly advertised feature of opening a saved card directly from the capture flow.

extensions/teak-raycast/src/lib/capture.ts and extensions/teak-raycast/src/quick-save.tsx need the showHUD vs. toast-action conflict resolved.

Important Files Changed

Filename	Overview
extensions/teak-raycast/src/lib/capture.ts	New shared helper for no-view save commands; toast primaryAction/secondaryAction are set but then immediately discarded by showHUD, making "Open Card" and "Open Source URL" permanently unreachable for users.
extensions/teak-raycast/src/quick-save.tsx	Adds clipboard prefill, renames the API call to createCard with a source field, and introduces addSuccessActions — but those actions are also unreachable because showHUD closes Raycast immediately after.
extensions/teak-raycast/src/save-text.ts	New no-view fallback command for root-search; manually defines Arguments/LaunchProps types that should come from the auto-generated raycast-env.d.ts instead.
extensions/teak-raycast/src/tags.tsx	New Browse Tags view command; clean implementation with proper loading/error/empty states and tag-drill-through via CardsListCommand.
extensions/teak-raycast/src/lib/api.ts	Adds createCard, updateCard, getCardById, listTags; refactors searchCards/getFavoriteCards to accept a CardSearchInput object; fixes withLoopbackFallback to use URL parsing instead of string replacement.
extensions/teak-raycast/CHANGELOG.md	New changelog entry uses {PR_MERGED_AT} placeholder instead of the standard {PR_MERGE_DATE}, which will not be substituted automatically at merge.

Prompt To Fix All With AI

Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
extensions/teak-raycast/src/lib/capture.ts:58-76
**Toast actions unreachable after `showHUD`**

`saveCardWithFeedback` sets `toast.primaryAction` ("Open Card") and `toast.secondaryAction` ("Open Source URL") and then immediately calls `showHUD`, which closes the Raycast window. Once Raycast closes, the Toast is dismissed too, so users can never click those actions — they are dead code for every caller of this helper (`save-clipboard-url`, `save-selected-text`, `save-current-browser-tab`, `save-text`). The same issue exists in `quick-save.tsx` where `addSuccessActions` populates toast actions before `showHUD("Teak capture complete")` is called. Either skip `showHUD` and keep Raycast open long enough for the user to interact with the toast actions, or remove the actions and only use `showHUD` for a fire-and-forget confirmation.

### Issue 2 of 3
extensions/teak-raycast/CHANGELOG.md:3
The date placeholder `{PR_MERGED_AT}` does not match the standard Raycast convention `{PR_MERGE_DATE}` used for automatic date substitution at merge time. The `0.2.0` entry just below uses the correct form.

```suggestion
## 1.0.30 - {PR_MERGE_DATE}
```

### Issue 3 of 3
extensions/teak-raycast/src/save-text.ts:10-20
Manually defining `Arguments` and `LaunchProps` types for a Raycast command's argument interface is discouraged. The `Arguments` type is auto-generated in `raycast-env.d.ts` (as `Arguments.SaveText`) whenever the extension builds; a hand-rolled definition can drift out of sync with `package.json` and introduce silent type mismatches.

```suggestion
export default async function SaveTextCommand(props: LaunchProps<Arguments.SaveText>) {
```

_{Reviews (1): Last reviewed commit: "chore(raycast): update dependencies and ..." | Re-trigger Greptile}

[greptile-apps]

Toast actions unreachable after showHUD

saveCardWithFeedback sets toast.primaryAction ("Open Card") and toast.secondaryAction ("Open Source URL") and then immediately calls showHUD, which closes the Raycast window. Once Raycast closes, the Toast is dismissed too, so users can never click those actions — they are dead code for every caller of this helper (save-clipboard-url, save-selected-text, save-current-browser-tab, save-text). The same issue exists in quick-save.tsx where addSuccessActions populates toast actions before showHUD("Teak capture complete") is called. Either skip showHUD and keep Raycast open long enough for the user to interact with the toast actions, or remove the actions and only use showHUD for a fire-and-forget confirmation.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/teak-raycast/src/lib/capture.ts
Line: 58-76

Comment:
**Toast actions unreachable after `showHUD`**

`saveCardWithFeedback` sets `toast.primaryAction` ("Open Card") and `toast.secondaryAction` ("Open Source URL") and then immediately calls `showHUD`, which closes the Raycast window. Once Raycast closes, the Toast is dismissed too, so users can never click those actions — they are dead code for every caller of this helper (`save-clipboard-url`, `save-selected-text`, `save-current-browser-tab`, `save-text`). The same issue exists in `quick-save.tsx` where `addSuccessActions` populates toast actions before `showHUD("Teak capture complete")` is called. Either skip `showHUD` and keep Raycast open long enough for the user to interact with the toast actions, or remove the actions and only use `showHUD` for a fire-and-forget confirmation.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

The date placeholder {PR_MERGED_AT} does not match the standard Raycast convention {PR_MERGE_DATE} used for automatic date substitution at merge time. The 0.2.0 entry just below uses the correct form.

Suggested change

	## 1.0.30 - {PR_MERGED_AT}
	## 1.0.30 - {PR_MERGE_DATE}

Rule Used: What: In Raycast extension changelogs, `{PR_MERGE_... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/teak-raycast/CHANGELOG.md
Line: 3

Comment:
The date placeholder `{PR_MERGED_AT}` does not match the standard Raycast convention `{PR_MERGE_DATE}` used for automatic date substitution at merge time. The `0.2.0` entry just below uses the correct form.

```suggestion
## 1.0.30 - {PR_MERGE_DATE}
```

**Rule Used:** What: In Raycast extension changelogs, `{PR_MERGE_... ([source](https://app.greptile.com/review/custom-context?memory=799af734-ebd9-4b40-9ffd-97a70fc71c8a))

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Manually defining Arguments and LaunchProps types for a Raycast command's argument interface is discouraged. The Arguments type is auto-generated in raycast-env.d.ts (as Arguments.SaveText) whenever the extension builds; a hand-rolled definition can drift out of sync with package.json and introduce silent type mismatches.

Suggested change

	type Arguments = {
	content?: string;
	};
	type LaunchProps = {
	arguments: Arguments;
	fallbackText?: string;
	launchType: LaunchType;
	};
	export default async function SaveTextCommand(props: LaunchProps) {
	export default async function SaveTextCommand(props: LaunchProps<Arguments.SaveText>) {

Rule Used: What: Don't manually define Preferences for `get... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/teak-raycast/src/save-text.ts
Line: 10-20

Comment:
Manually defining `Arguments` and `LaunchProps` types for a Raycast command's argument interface is discouraged. The `Arguments` type is auto-generated in `raycast-env.d.ts` (as `Arguments.SaveText`) whenever the extension builds; a hand-rolled definition can drift out of sync with `package.json` and introduce silent type mismatches.

```suggestion
export default async function SaveTextCommand(props: LaunchProps<Arguments.SaveText>) {
```

**Rule Used:** What: Don't manually define `Preferences` for `get... ([source](https://app.greptile.com/review/custom-context?memory=d93fc9fb-a45d-4479-a6a4-b1b4af98ebc8))

How can I resolve this? If you propose a fix, please make it concise.

[0xdhrv]

Hi @praveenjuge 👋

Thanks for the contribution 🔥

Could you look into the suggestions from Greptile

---

I converted this PR into a draft until it's ready for the review, please press the button Ready for review when it's ready and we'll have a look 😊