- Developer Tools: we've introduced a new developer option,
Use file logging instead of OSLog
, to work around an OS issue that causes some users to not see any extension logs in the terminal during development.
- Form's Date Picker: Future dates will be prioritised when parsing the date, f.e. if you type "8am" and itrs already "10am", then the parsed date will be "tomorrow 8am".
- Fixed an issue where the
ray
CLI could not communicate with the app. - Fixed an issue where an OAuth authorization session triggered by a menu bar command would not be able to complete if a
background
launch was triggered between authorization starting and completing. - Fixed an issue on multi-monitor setups, where sometimes MenuBarExtra icons would not appear dimmed on inactive displays.
- Form: Introduced a new component
Form.LinkAccessory
to render a link displayed in the right-hand side of the search bar. - Arguments: Introduced a new Argument type:
dropdown
. You can now specify a list of options for the user choose from. - Developer Hub: User preferences are now included in error reports. Password and text preferences will be replaced with
[REDACTED]
, file/directory/appPicker preferences will be scrubbed of PII, and dropdown/checkbox preferences will be sent as-is.
- Window Capture: Added a warning when trying to take a screenshot of Raycast if that screenshot wonβt match the requirement for the Storeβs extensions guidelines (eg. if Raycast is too close to an edge or if the screen doesnβt have a high enough resolution).
- Types generation: Fixed the type of a required
appPicker
preference (even if it isrequired
, the app might be undefined because it is missing). - Empty View: Fixed an issue where the Empty View might not be showing in a certain case.
- Menu Bar Extra: ****icons tinted with
Color.PrimaryText
andColor.SecondaryText
should now change based on the menu barβs appearance. - List Metadata:
Link
s should be properly aligned again.
- Improved runtime error handling when using a Swift project
-
Lists: Fixed a race condition where the selected item would not be the first one after a list items update
-
MenuBarExtra:
alternate
are no longer supported on pre-Sonoma versions of macOS, as they would often appear alongside their parent items.
- Menu Bar:
MenuBarExtra.Item
s have a new prop,alternate
. If analternate
is defined, it will replace its parentMenuBarExtra.Item
when the user presses the β₯ (option) key. - The Node runtime has been updated to Node 20, the current Long-term Support (LTS) release.
- AI: You can now use the
gpt-4
model withAI.ask
. If a user does not have access to this model, it will gracefully fall back to an available model. You can check if a user has access usingenvironment.canAccess('gpt-4')
.
- Error Handling:
Could not communicate with command worker
errors should not be reported anymore.
- Toast: Fixed an issue that caused toast actions to not work after a toast was updated.
- Error Handling: Fixed an edge case that could cause an out-of-memory error while an uncaught exception was processed, obfuscating the original error.
- Performance: Fixed an issue where some keyboard events would be dropped while an extension was loading.
- Markdown: Fixed a regression where HTML comments would show up in the rendered Markdown.
- Date Picker: When specifying a min and/or max date, the suggestion will now always be within those bounds
- Fixed a bug that previously could cause a
no-view
command to display an error icon in the root search, with no means of removing the error.
The new Extension Issues Dashboard is designed to help you quickly troubleshoot and resolve issues in any of your extensions by providing real-time visibility into errors encountered by users. You can access it at https://www.raycast.com/extension-issues, or by using the new View Issues
action.
- It is now possible to write extensions using ESM instead of CommonJS
- Updated NodeJS runtime to 18.18.2
- When copying a deeplink with some arguments in the root search, copy the deeplink with those arguments
- Fixed an issue where animated toasts would hang around after the command was unloaded.
- PickDate: Similar to
Form.DatePicker
, you can also check whether the user picked a full day or a specific time withAction.PickDate.isFullDay(date)
.
- Clipboard: The
transient
option is renamed toconcealed
.
- MenuBarExtra: Right-clicking
MenuBarExtra.Item
s should now work in macOS Sonoma.
- Alert: Add a new option
rememberUserChoice
to show a checkbox to remember the user choice the next time the same Alert would be shown. - DatePicker: You can know check whether the user picked a full day or a specific time with
Form.DatePicker.isFullDay(date)
.
- The βFork Extensionβ action is now also available in the Store for installed extensions.
- All the APIs that accepts a file path will now resolve
~
if necessary.
- Fix an issue where some Toasts would not disappear after the command was terminated.
- Fix an issue where List Itemβs accessories with an icon could have their text cut off.
- Fix
getFrontmostApplication
failing for some applications. - The βFork Extensionβ will now be more robust dealing with unexpected
package.json
formats. - Fixed an issue where newly created Extensions would not use the correct username after it had been updated.
- Fix an issue where it was possible to set a multiline
searchText
- Metadata: Fixed various rendering issues with
TagList
. - Menu Bar Extra: Fixed a bug that caused section titles to be unreadable on macOS Sonoma.
- Menu Bar Extra: Fixed a bug that could cause a menu bar command to be unloaded while its menu is open.
- Form: Fixed stale suggestions in the DatePicker when changing its type.
- Icon: Fixed the
AppWindowGrid2x2
icon only showing a square.
- Clipboard:
Clipboard.read()
now supports anoffset
option to access the Clipboard History (limited to the last 5) - Grid: Grid items can now have an icon accessory
- Shortcuts: Providing a consistent user experience should now be easier thanks to the new
Keyboard.Shortcut.Common
export.
getSelectedText
is now more reliable- Trash: Improved behaviour of
trash
andAction.Trash
to better handle missing files. - HUD:
showHUD
now supports the same options ascloseMainWindow
- Command Launching: Improved logic for deciding which version of a command gets launched when a user has both a production and a development version of an extension installed.
- Tags: Icon-only tags should now center the icon.
- Form: When working on a draft, updating a
Form.Checkbox
will update the draft. - Error Reports: Improved error messages when an extension crashes during a background launch.
- Shortcuts: Previously, the API permitted the creation of shortcuts using keys reserved by Raycast (β+K, β+W, β+Esc, etc.), resulting in unexpected behavior. Raycast now ignores these and, during development mode, they will trigger a runtime warning.
- Fallback Commands: Local commands will now have an indicator so that itβs possible to differentiate them from the commands installed from the Store
- The NodeJS process used for Raycast extensions will now be named
Raycast Helper (Extensions)
- Active menu bar commands will now be displayed in
Extension Diagnostics
.
- Fix an issue where Metadataβs Tag items would sometimes not be updated
- Fix a bug where renamed commands appear in the root search with both the original and the updated name after an extension update.
- Add an action to clear the local storage when an unexpected error occurs
- When using
showToast
while the Raycast window is closed (for example if a command is launched with a hotkey), aHUD
will be shown instead - Improve the error messages when a command fails to load
- The NodeJS inspector will now use a random free port instead of using the default 9229 port (which you can use for other NodeJS scripts)
- Fix a performance issue on the first render of Lists and Grids
- Fix an issue where required arguments wouldnβt be required when launching a command right after installing it
- Fix a regression where the deprecated
render
method would not work anymore - Fix an edge case where some Form items would not be updated if some items would be added at the same time
- Metadata:
List.Item.Detail.Metadata.TagList.Item
andDetail.Metadata.TagList.Item
now accepts an action handler via theonAction
prop! - Added LaunchContext support to
Create Quicklink
andCreate Snippet:
launchCommand({ ownerOrAuthorName: "raycast", extensionName: "raycast", name: "create-quicklink", type: LaunchType.UserInitiated, context: { name: "context name", application: "Xcode", }});
launchCommand({ ownerOrAuthorName: "raycast", extensionName: "snippets", name: "create-snippet", type: LaunchType.UserInitiated, context: { name: "context name", text: "context text", keyword: "context keyword" }})
- Date Pickers: You can now add a minimum and maximum date to
Form.DatePicker
andAction.PickDate
using themin
andmax
props to limit the suggestions shown when entering a date.
- Updated NodeJS to 18.16.0
- Improve the βFork Extensionβ action to avoid modifying the manifest as much as possible.
- Fixed a bug that sometimes caused
no-view
commands to not display errors. - Fixed a bug that caused OAuth not to work if the
client.authorize(authorizationRequest)
was executed more than once. - Fixed a problem where commands with background execution would not display the OAuth sign-in screen.
- SVG: Properly handle
currentColor
- List/Grid: Fixed
selectedItemId
being sometimes ignored on the first render. - Form: Fixed triggering
onChange
on the TextArea when using a markdown keyboard shortcut.
- SVG: You can now use the Raycast
Color
in an SVG.
- Improve the error message when a required property is missing on a component
- Fixed an edge case where the keyboard events triggered while an extension is loading would not be passed down to the extension once loaded
- Fixed an issue where the fallback of an image would show while it is being loaded
- AI: Introduced a new
AI
Pro API. UseAI.ask
to seamlessly ask any prompt and enhance your extensions with artificial intelligence. - Pro APIs: You can now check whether a user can access a certain API using
environment.canAccess(AI)
.
- Custom Theme: Deprecated
Color.Brown
as it is not part of the Raycast colors anymore. - Custom Theme: Renamed
environment.theme
toenvironment.appearance
. - Improve the error message when an API is called with arguments of the wrong type.
- Forms: Fixed an issue where drafts would not save the value of a File Picker.
- Forms: Fixed an issue where
onChange
would not be triggered in certain cases for a File Picker. - Lists: Fixed an issue that caused a Listβs section to re-render whenever an action panelβs submenu was updated.
- Colors: Fixed a crash that could sometimes occur when using
adjustContrast
on a dynamic color.
- Raycast now provides 2 global TypeScript namespaces called
**Preferences**
and**Arguments**
which respectively contain the types of the preferences and the types of the arguments of all the commands of the extensions. For example, if a command namedshow-todos
has some preferences, itsgetPreferenceValues
's return type can be specified withgetPreferenceValues<Preferences.ShowTodos>()
. This will make sure that the types used in the command stay in sync with the manifest. - It is now possible to add commands that are disabled by default. A user will have to enable it manually before it shows up in Raycast's root search. This can be useful to provide commands for specific workflows without overwhelming everybody's root search.
- Markdown Tables are now properly supported.
- Markdown code blocks now support syntax highlighting. To enable it, make sure you specify the programming language at the start of the block.
- Colors: To improve accessibility, dynamic adjustment for raw colors (
HEX
,rgb
etc) used in extensions has been switched from opt-in to opt-out. If your extension relies on accurate color reproduction, check the documentation for instructions on how to opt-out. - Images: You can now suffix your local assets with
@dark
to automatically provide a dark theme option, eg:icon.png
and[email protected]
.
- CLI: Fix an issue where the CLI wouldn't want to bundle files named
foo.node.js
.
- It is now possible to drag and drop items from Grids. Lists are also supported if their items have as
quickLook
properties.
- Extend
launchCommand
to allow inter-extension launches - Extend
launchCommand
to allow to pass afallbackText
- SVG: Ignore doctype and HTML comments
- Fix a flicker happening when there was a fallback text passed to a command
- Fix a rendering issue with multi-line
tag
text.
- Clipboard: Added
transient
option toClipboard.copy
method. - Actions: Added
type
prop toAction.PickDate
to control the date components to be picked.
- Improve the time to interaction when launching a command that always renders the same view type.
- Changed
Deactivate Command
action shortcut toβ β₯ β§ D
, so it doesn't clash withCopy Deeplink
- Fixed an issue where restarting Raycast would not properly restore menu bar commands that sometimes didn't put anything in the menu bar.
- Locale: Respect the hourCycle, calendar, and numbering system locale.
- Clipboard: Add a new
Clipboard.read()
method that reads the clipboard content as plain text, file path, or HTML.
- List Accessories: Tags can now use any color (we made some improvements to ensure that any color would have enough contrast to be readable)
- Fixed a bug where reloading menu bar commands in development mode would not respect certain manifest property updates (e.g. interval).
- Fixed a bug that caused
Metadata.Link
'stitle
to be cut off unnecessarily when using the large text size. - Fixed a bug where
clearSearchBar
wouldn't clear the search bar when rendering a Grid. - Fixed a bug where
ray lint
would fail if there were a .DS_Store file in thesrc
folder.
- Source maps for production errors: source maps are now also enabled for production builds of an extension. When an exception occurs, you get cleaner stack traces with proper source locations in the TypeScript sources files (vs. the minified and unusable JavaScript locations). Note: An extension must be re-published to enable production source maps.
- Action.PickDate: We are introducing a new Action to allow users to set a Date directly from the action panel.
- Dev Tools: the "Start Development" command under "Manage Extensions" now starts development in iTerm if installed as the default terminal.
- In order to ensure that date formatting & other internationalization functions work as expected, the NodeJS process is now started with the
LC_ALL
environment variable set to the user's current locale.
- Fixed an issue where the first exec/spawn call for running a subprocess could be slower than subsequent calls.
- Fixed menu bar icon padding when there's no text.
- Fixed a problem where menu bar commands updated with a new required preference would not display the required preference screen.
- Fixed a rare bug with menu bar commands that could lead to Raycast hanging.
- Fixed an issue where menu bar commands launching view commands would cause stacking in the navigation hierarchy.
- Fixed an issue where fallback images in lists would flicker.
- Dev Tools: Fixed a bug when zip archiving extensions with special characters in file names.
- Fallback commands: All commands (except menu-bar commands and commands with more than one required argument) can now be used as fallback commands! They should all work out of the box (e.g. a command that renders a List will receive
onSearchTextChange
with the fallback text on its first render, etc.) but you can customize the user experience with a new top-level propfallbackText
. - List Accessories:
date
andtext
accessories can now be colored. - List Accessories: We've added a new accessory type:
tag
. - Metadata: Label text can now also be colored.
- Proxy Support: Extensions using popular networking libraries such as node-fetch/cross-fetch, got, Axios, or our useFetch hook are compatible with proxies if the user has turned on the new proxy preference in Raycast.
- Background refresh: when a command misses a required preference, instead of showing the error screen, the user is directed to the preference onboarding screen again.
- Fixed a bug where entered characters could be "swallowed" in controlled form components or the controlled search bar.
- Fixed the
launchContext
not being propagated to menu-bar and background launches when using thelaunchCommand
API. - Fixed a multi-monitor bug where menu bar extra text would be unreadable on the inactive screen.
- Fixed a bug where menu bar extra icon tinting would change based on Raycast's appearance instead of the system's.
- Fixed some memory leaks when using Form components
- Async Submenus and Dropdown: Dropdowns and ActionPanel Submenus now also support the properties
onSearchTextChange, isLoading, throttle, filtering
- same as for List and Grid where you can perform custom logic when the user changes the search text. - Application: You can now get the current frontmost Application of the system with the top-level
getFrontmostApplication
method. - File and Directory Preferences: We've added two new preference types
"directory"
and"file"
, supported via the manifest. Both types show a file picker component and let the user select directory or file paths. - Environment: You can now get the user's text size via
environment.textSize
.
- Pop To Root Behavior:
closeMainWindow
accepts a new parameterpopToRootType
that lets you control when Raycast pops back to root: the default is as-is and respects the user's "Pop to Root Search" preference in Raycast.PopToRootType.Immediate
closes the window and immediately pops back to root, regardless of the user's setting (so you can get rid of an additionalpopToRoot()
call). The new modePopToRootType.Suspended
temporarily prevents Raycast from automatically popping back to root; this is useful for situations where a command needs to interact with an external system utility and then return the user back to the launching command. - Clipboard: We added new options to copy and paste HTML content, which is useful for sharing formatted text, e.g. a link to a Notion page in Slack.
- Markdown: Markdown in a
Detail
component now supports convenience image references for icons and asset folder files such as:
or
(absolute URLs and user folder paths via~
are also supported) - OAuth: The client's
providerIcon
is now optional (extension icon as default) and accepts anImage.ImageLike
type. - List and Detail Metadata: Now show tooltips when labels get truncated.
- Action.ToggleQuickLook: Now also expands paths starting with
~
.
- Dropdown: Fixed triggering a dropdown component's
onChange
handler when navigating. - Dropdown: Fixed the missing
placeholder
property in the search bar dropdown. - Forms: Fixed submitting a form with marked text.
- Actions: You can now specify an action to focus when opening the ActionPanel (and an ActionPanel.Submenu) by setting the
autoFocus
prop. - Forms: Introducing a new Form Item
Form.FilePicker
to select one or multiple files (or directories)
- DX: A warning will now be shown in the console when using async entry points for view and menu-bar commands.
- List/Grid: Improved the keyword search algorithm to match intersecting keywords (for example, the search term "black cat" matches keywords ["black", "cat"]).
- Grid: The grid supports a new property for configuring how sections are ordered. Setting
filtering={{ keepSectionOrder: true }}
ensures that the sections' order is not changed based on items' ranking values; this can be useful for use cases where a small number of fixed sections should always appear in the same order when the user filters the grid. We are deprecating theenableFiltering
property.
- Fixed the Grid or List's selection sometimes not being preserved when native filtering is disabled.
- The
Image.Mask.RoundedRectangle
mask will be more consistent regardless of the size of the image. - Fixed an issue where the specified
searchText
property would not always be respected.
- The Node runtime has been updated to Node 18, the current Long-term Support (LTS) release.
- Commands can now launch other commands! Using the new
launchCommand
method, you can now trigger a background refresh of another command in the same extension - or even open another command. Some use cases are updating a menu bar command from a view command or, vice versa, launching a companion view command from the menu bar. (Note that for now we only support launches of other commands within the same extension.)
- Grid now supports two new aspect ratios: 4/3 and 3/4.
- Menu Bar icon tinting is now theme-aware.
- Background Refresh: The shortest interval available is now 10s instead of 1m (use cautiously and also see our best practices guide).
- Grid: The grid supports a new property for configuring how sections are ordered. Setting
filtering={{ keepSectionOrder: true }}
ensures that the section order is not changed based on items' ranking values; this can be useful for use cases where a small number of fix sections should always appear in the same order when the user filters the list. We are deprecating theenableFiltering
property.
- List Item Metadata Link and Detail Metadata Link styling should now be consistent with their respective List Item Metadata Label and Detail Metadata Label respectively.
- Fixed a bug where
List.Item
's accessories might not be aligned. - Fixed a bug where the last API call or log in a no-view command would not run before the command gets unloaded.
- Grid: the
Grid
component accepts three new props that should give extension authors more flexibility:columns
,fit
andaspectRatio
.
- Grid Sections don't all have to look the same anymore! The grid
Section
component now also accepts thecolumns
,fit
andaspectRatio
props. When specified, they will override the value of the parentGrid
component's prop. - List: The list supports a new property for configuring how sections are ordered. Setting
filtering={{ keepSectionOrder: true }}
ensures that the section order is not changed based on items' ranking values; this can be useful for use cases where a small number of fix sections should always appear in the same order when the user filters the list. We are deprecating theenableFiltering
property. - Menu Bar Extra: added a new
Section
component, which can be used to better group relatedItem
s and/orSubmenu
s. The component has an optional title for the section. At the same time, we are deprecating theSeparator
component. - Menu Bar Extra: The
Item
component now accepts an optionalsubtitle
prop. - Clipboard:
Clipboard.copy()
andClipboard.paste()
methods now accept file paths as a parameter.
- Improved dark/light mode detection for Menu Bar Extra icons.
- If a Menu Bar Extra's
title
spans multiple lines**,** only the first one will be displayed.
- Fixed certain error stack traces causing CPU spikes of the Node process.
- Fixed an issue with macOS Ventura Beta where Menu Bar Extras would sometimes become unresponsive.
- Fixed the type of the List and Grid's
onSelectionChange
. It always used to returnnull
when no items were selected but the type wasstring | undefined
. It is now properlystring | null
. Note that this might trigger some TypeScript error when you upgrade but it should help you fix some bugs.
- Menu Bar Extras can now be deactivated without disabling the menu bar command! To deactivate a menu bar command, run the
Deactivate Command
action from the command's Action Panel - or drag the menu bar extra out of the menu bar while holding down β. - Commands with Background Refresh also now have a
Deactivate Command
action! - Menu Bar Extras now support both a primary and secondary action type (right click or control click).
- Dropdown's items can now specify
keywords
to match more search terms. - Extension Diagnostics command can now be used to help finding the cause behind any issues with extensions. It displays all
Loaded Commands
, commands withBackground Refresh
enabled and latestEvents
triggered.
- Menu Bar Extra action handlers will now either wait or force a render after finishing execution, to ensure any state updates performed in the action handler have had a chance to render.
- Menu Bar commands now automatically refresh when their or their parent extension's preferences change.
- OAuth: Path-based redirect URLs are now officially supported.
- OAuth:
β οΈ οΈ API methods for OAuth request creation now throw an error when used from a background command - you can check the launch type of a command to see whether authorization can be performed - Types: Node and React types have been added back as optional API peer dependencies and dev dependencies to the templates, so that VS Code autocompletion works.
- Templates: Updated to include the utils package.
- DevX: Added warnings when specifying a
value
withoutonChange
or when changing a Form item from controlled to uncontrolled. - DevX: For starting development, the CLI does not depend on metadata attributes any more
- Forms: The type of the
DatePicker
's value is nowDate | null
(null
happens when selectingNo Date
).β οΈ This might cause some TypeScript errors but it will now reflect what is really happening, preventing bugs at runtime. - Fixed an issue where
List.Item.Detail.Metadata
titles sometimes being cropped despite there being enough room. - Menu Bar Extra
Item
andSubmenu
icons now change based on the system's dark / light mode, not Raycast's. - Forms: Fixed a bug where the initial value for a controlled TextArea could not be deleted.
- Forms: Fixed the info icon and message not coming back after clearing an error on form items.
- Forms: Fixed updating the placeholder of the TagPicker item.
- Empty View: Fix an issue where an Empty View's actions would be rendered even thought the Empty View isn't.
- OAuth: Fixed a bug where multiple overlays could stack upon each other when OAuth was initiated from a menu bar or background launched command
- Bundler: You can now import wasm files and they will bundle in the extension
- SVG: Accept a percentage for rect corner radius attributes
- Actions:
Action.Trash
is now a Destructive Action (meaning it will show up in red)
- Metadata: Fixes an issue where List Metadata would sometimes render Tags in the wrong position
- List.Item.Detail.Metadata: We've added support for new
Link
andTagList
item types. - Environment: You can now check the
mode
of the current command (as defined in the manifest) viaenvironment.commandMode
.
- CLI: The ray CLI is now code-signed
- CLI: We've updated esbuild to v0.14.52
- NPM size: is now 0.5MB instead of 25MB (binary files for ray CLI have been moved out of the NPM package)
- Navigation: Top-level components can now dynamically return a different view type when used inside a navigation stack
- Background Refresh: Fixed an edge case where commands would run into a timeout that prevented further refreshing
- Menu Bar Commands: Fixed a bug where the error screen of menu bar commands would repeatedly be shown in the root search
- Actions: Triggering actions by numeric shortcut / double-clicking could trigger wrong actions or didn't work entirely
- Form:
TextArea
placeholder now won't highlight markdowns if it hasenabledMarkdown
- Added debug actions to all local development commands in root search
- Menu bar commands now show an activation button in preferences
- Menu Bar Commands: Fixed issues around hot reloading, unloading, and inconsistent action handler behavior
- No-view Commands: Fixed returning top-level props for commands that doesn't have arguments or drafts
- π« Menu Bar Commands (Beta): For a long time, Commands could only live in the Raycast window. From today, Commands can put glanceable information in the Menu Bar πͺ. Check out our new docs section on how to develop your first native macOS menu bar command with hot reloading π₯.
- π Background Refresh (Beta): To keep Menu Bar Commands up-to-date, we ported Background Refresh from Script Commands to Extensions. Background Refresh is configured with a new interval option in the Extension's manifest and also works for "no-view" mode commands. Read more about it in a new docs guide.
- πͺ Utils: We've released new React hooks to make it faster to build extensions that follow best practices. To do this, we looked at the Extension's repository for use cases and how we can improve them. Most Extensions connect to APIs: they make network requests, show a toast to handle errors, and add caching and optimistic updates to speed up interactions. Utils are available via a new public npm package.
- π€¬ Arguments: We also ported more functionality from Script Commands. Extensions can now define arguments, which enable simple forms that live in the root search of Raycast. Arguments can be defined via the manifest, and their entered values are passed to the main function of a command.
- βοΈ Subtitle Updates: We've added a new method
updateCommandMetadata
that allows you to update the subtitle of a command in root search. Combined with Background Refresh, this is another way to present information to the user as dashboard-like items in the root search.
- Redesign: Along side the app's redesign, we are introducing a whole set of new icons for you to pick to illustrate the actions in your extensions.
- New Destructive Action: You can now specify the
style
of anAction
to highlight it in the Action Panel as destructive. Use it for actions where an end-user should be cautious with proceeding.
- DevTools: Turning on the "Use Node production environment" in the Advanced Preferences will also hide the debug actions. Previously it was only hiding them when there was no Action Panel specified.
- DevTools: The "Clear Local Storage" debug action has been renamed to "Clear Local Storage & Cache" and will clear the Cache along side the Local Storage.
- Dev Tools: The "Start Development" action now quotes the extension folder path.
- Dev Tools: Added a new development advanced preference to keep the Raycast window always visible during development.
- Dev Tools: Added a new build status tooltip to the accessory icon of a development command in root search.
- Dev Tools: Improved the error handling for failed extension updates after invalid manifest changes; improved the error messages for general rendering errors.
require('os').tmpdir()
will now properly return the path to a temp directory.- Fixed a rarely occurring crash happening when using some SVGs with a path that contains an arc where the ending point is the same as the starting point.
- Forms: Fixed a bug where stored form values could get cleared after extension updates.
- Forms: Fixed inconsistent behaviour of the
onBlur
handler that could get triggered for theForm.TextField
when the form screen is popped in a navigation stack. - List: Fixed the updating of tooltips for list accessory items.
- React 18: React Suspense,
useSyncExternalStore
, etc.. A whole bunch of new features are available with the newest version of React. See the migration guide for more information. - Quick Look: Use the new
<Action.ToggleQuickLook />
action to show additional information with a Quick Look preview. - Forms: Use the new validation feature to check if entered data is correctly formatted and show failure messages with a nice UX
- Forms: Drafts support - use the feature if you want Raycast to preserve non-submitted data, to provide the best experience for users
- DevX: Check out the new screenshot tool that takes a photo of Raycast from the best possible angle
- List Accessories: You can now pass
{date: Date}
as an accessory and it will be rendered nicely by Raycast. - Detail View: Add support for
- [ ] task
and- [x] task
in markdown views. - Action Panel: Add a new
onOpen
callback onActionPanel.Submenu
. It can, for example, be used to lazily fetch the content of the Submenu. - Grid: Add support for
ColorLike
as Grid.Item's content. - Forms: New callbacks
onFocus
andonBlur
for all the items - Forms: Markdown highlighting for the
Form.TextArea
- Misc: Fixed a crash when using
<List>{response?.website && <List.Item title={response.website} />}</List>
andwebsite
is an empty string (Issue 1845).
- Dev Tools: Fixed uninstalling of local development extensions via the Action Panel
- Markdown: Fixed rendering of transparent animated gifs in markdown
- Forms: Fixed an issue when entering characters with IME (
Issue 739) in controlled text inputs
- List Accessories: Fixed the tooltip for grouped accessories; now the tooltip will be shown for the group instead of separately for the items
The <Grid />
component's made its way to our API. It's perfect to layout media-heavy information, such as icons, images or colors. The component allows you to layout differently sized items. We designed its API close to the <List />
component for smooth adoption.
- Fixed the controlled mode for
Form.DatePicker
- Fixed the dynamic appearance of form item's
info
accessory - Fixed the OAuth logout preference not being shown for single-command extensions
- Fixed a bug where components that are pushed with the same properties values would not be updated (
Issue 1843)
- Fixed a bug where updated list metadata items would cause unnecessary list reloading
- Fixed an issue with tinted, resized icons appearing blurred in some cases (e.g. Alerts)
- List Item Metadata: we've added a new
metadata
property to theList.Item.Detail
component, allowing you to add structured metadata. Themetadata
property can be used together withmarkdown
, in which case the detail view will be split horizontally, with the markdown being displayed in the top half and the metadata displayed in the bottom half (similar to theFile Search
,Clipboard History
orSearch Contacts
commands). Alternatively, it can be used by itself, in which case the metadata will take up the entire height of the detail view. - Preferences: We've added two new top-level methods
openExtensionPreferences
andopenCommandPreferences
that allow you to open both extension and command preferences, for example, via an Action (Issue 179)
- Added a new development action to clear the local storage of an extension
- Fixed a bug where the wrong form element onChange handler would be called initially while the form was being updated (
Issue 1633)
- Fixed a bug where form elements would not be re-rendered correctly (
Issue 1663)
- Fixed a bug where a fully controlled form TextField/PasswordField behaves as stateful (
Issue 1093)
- Fixed
EmptyView
not being displayed when it would be reused in a navigation stack
- OAuth: TokenSets are now included in the encrypted Raycast export (Raycast Preferences > Advanced > Export)
- OAuth: The convenience method
TokenSet.isExpired()
now includes some buffer time to reduce the risk of performing requests with expired access tokens
- Fixed an issue where updating the search bar accessory would result in the search bar text being selected
- Forms: We've fixed some inconsistencies around form item properties and added new warnings (e.g. when
defaultValue
andvalue
are set at the same time); this also fixesIssue 1104
- Forms: Fixed an issue where updating form items would lead to unwanted scrolling; fixed the
autoFocus
property not scrolling to the focused item - Fixed an issue with
Action.OpenWith
trying to perform a state update without checking whether it's still mounted (Issue 1495).
- Fixed an issue where
adjustContrast
would not be respected for colored TagPicker items.
- OAuth: we've added a new API that enables you to authorize extensions through OAuth providers such as Google, Twitter, Dropbox or Spotify (
Issue #178). The docs contain a new detailed guide and we've added some integration examples to the extensions repository. (Note that we currently only support OAuth 2.0 with PKCE, more on that in the guide.)
- Form Focus: use the new imperative form API to programmatically focus form items. Want to make sure a particular input is focused on mount? Form items now accept an
autoFocus
prop! (Issue #66)
- Form Reset: use the new imperative form API to reset form items' values to their initial values.
- Form Info: Use the new
info
prop on form items to show additional information about an item, e.g. to explain what this field is used for. - The Raycast window opens automatically when you start a development session for an extension. You can turn the behavior off in the Advanced preferences tab.
- Improved detection of default editor when you open extensions from Raycast
- Improved templates for list, form and detail
- Removed
react-devtools
fromdevDependencies
for newly created extensions (so that you don't have to download a big dependency that you might not use)
- Fixed an issue where animated gifs would be incorrectly scaled when size attributes are specified in markdown.
- Form Checkbox now returns proper boolean values on submit
- List Tooltips: List items now support tooltips for the title, subtitle, icon, and each accessory item. For titles, you can use the new type
{ value: string, tooltip: string }
, for icons{ value: Image.ImageLike, tooltip: string }
, and for accessories you just add the new propertytooltip
. - Animated Gifs: the
Detail
component now renders animated gifs defined in markdown! π
- Improved recovering the Node process after a crash and logging the error to the CLI output
- Added support for running CLI commands through
npx @raycast/api <commandName>
- Improved the
Create Extension
command to addREADME.md
andCHANGELOG.md
files
- Detail Metadata: Fixed toggling (showing/hiding)
- Detail Metadata: Fixed only one separator item getting rendered
- Detail Metadata: Fixed a crash when using primary or secondary colors for tag items
- List Accessories: Fixed rendering when using
undefined
for accessory values - List EmptyView: Fixed an issue where passing a
List.EmptyView
child to aList.Section
would treat it as aList.Item
- SVG: Fixed rendering base64 encoded SVG images
- Fixed loading when a new command is launched by hotkey while another command is open
- Detail Metadata: we've added a new property
metadata
to theDetail
component; this allows you to add structured metadata that is displayed on the right side in a detail view (similar to the Linear, Asana or Jira extensions). We support types such as labels, coloured tags, links, and separators. (Issue #219)
- List Accessories: list components can now show multiple accessory items through the new
accessories
property. (Previously you could only configure oneaccessoryTitle
andaccesoryIcon
, both of which continue to work but have been marked deprecated.) Each item can be configured as text-only, icon-only, or icon + text. (Issue #72)
- List Empty View: list components can define a new
EmptyView
that gives you control over the icon, title, description and optional actions to use when there are no items in a list. (Previously we would default to a "No results" view.) You can use the component to show a custom image and text when the search does not return results or the user is required to first perform some setup. (Issue #447)
- Environment: the current theme (
"dark" | "light"
) configured via Raycast appearance preferences is now globally accessible throughenvironment.theme
- SVG: You can now specify width and height attributes for images in markdown (
<img>
tag). - Dev Tools: the "Create Extension" command lets you add categories to your extension; the categories are displayed alongside the new metadata on our revamped details page in the store.
- Dev Tools: added a new development action to clear the local assets cache, e.g. to render an updated list icon without having to restart Raycast. (
Issue #1095)
- Preferences: the
required
property in manifest preferences is now optional.
- Fixed the extension icon not being updated during development.
- Fixed an extension's cached icon not being cleared when updated from the store. (Note that other dynamically loaded images in the assets folder may still be cached, so if you want to enforce an update for end users you need to rename them.)
- Fixed an edge case where some search bar characters would be wrongly passed to pushed lists in a navigation stack.
- Fixed updating the list
isShowingDetail
property - Fixed unnecessarily reloading the list detail view on search term changes
- We've added the highly requested search bar dropdown π (
Issue #72): you can now add a dropdown component as an accessory to the search bar; the dropdown shows up in the top-right corner and can be used for filtering lists and toggling list states. (So it's a good time to remove any workarounds with actions or navigation for showing a different set of items in the list.)
- The search bar text π can now be programmatically updated (
Issue #281) while you can still opt into built-in filtering at the same time
- List-detail views: list views now support a
detail
property that allows you to display a detail view on the right-hand side of list items (Issue #83) π―ββοΈ; you can use the feature to display additional content side-by-side as users scroll through the list
- Support for rendering SVG files πΌοΈ where images are accepted (
Issue #77), including in the
Detail
view's markdown - New method
Clipboard.readText()
to read the last copied text from the system's clipboard π - Added a new prop
type
toForm.DatePicker
π to control the date components asked from the user
- Toast action handlers π can now still be called if the toast outlives a dismissed extension
- Support for multiple actions of type
Action.SubmitForm
in a form's Action Panel
- Fixed some flickering that could happen when using
React.memo
- Fixed a few edge cases around Action Panels
- Fixed duplicated shortcut shown in the Action Panel's tooltip when setting the default shortcut explicitly on the primary action
- Fixed updating a
Form.Description
component
- Add 2 new Actions:
Action.CreateSnippet
andAction.CreateQuicklink
. Use them in your extensions to provide users an option to integrate deeper with Raycast, for example, by creating a Quicklink from a frequently visited website.
- Various documentation fixes and improvements such as new media for UI components.
- Synchronous React state update calls are now batched, leading to less re-rendering.
- Markdown comments will now be hidden in the
Detail
view
- Fixed a crash that could happen when switching between a development and store version of an extension or restarting the Node connection.
- Fixed an issue with React Developer Tools sometimes not getting opened.
- Limit the width that the
ActionPanel
can take.
- Completely revised (backwards-compatible) API - new namespaces, better organisation, more consistency, updated templates, revamped docs. Check out the full migration guide and get rid of those deprecation warnings. (At the same time, don't worry, your extension is going to work as before, even if you don't take immediate action.)
- We've prettified the CLI output π : all output is now more colourful, cleaner and easier to parse. Update the npm package to v1.28.0 to get the latest CLI for development.
- Fallback images: You can now specify local asset files or built-in icons that are displayed when image loading fails, for example when a remote file is missing (
Issue #108); see the docs
- Toasts are now passed as argument to their action callback, so you can directly act on them in the handler function (for example, hiding them)
- Extensions feedback: We've added better bug report and feature request actions both to the store details page of an extension and to the error screen; the actions prefill some data already in the templates so that reporting issues and feature requests becomes easier for end users.
- Fixed tag picker images and emojis not being properly displayed (
Issue #493)
- Preferences: Added a new app picker preference type - useful if you want to let users customize their apps to use for opening files, folders and URLs
Issue #98
- Forms: Added new
Form.PasswordField
that allows you to show secure text fields (Issue #319 andIssue #44)
- Forms: Added new
Form.Description
component that allows you to show a simple label - Added a new top-level
open
method that gives you more flexibility for opening files, folders, and URLs with default apps or specified apps, often making using an external npm package unnecessary (the built-in open action use our method under the hood) - Node: added security enhancements for the managed Node runtime such as verification of the executable, configuring executable permissions, and removing unnecessary files
- CLI: Added more error info output to build errors
- CLI: Added a new
βfix
flag to thelint
command (applies ESLint and prettier fixes) - Create Extension Command: Updated the templates to include a
fix-lint
script; added prettier to devDependencies
- Forms: Fixed
onChange
callback behaviour to be consistent across all components - Forms: Fixed generic updates of titles for all components (
Issue #687)
- Preferences: Fixed a bug in dropdown preferences returning the defined default value, even if the default is not part of the list values
- Preferences: Fixed the
data
property not being treated as required for the dropdown - Preferences: Fixed defined initial values not being ignored (use default only)
- List: Fixed same-rank items with identical names being non-deterministically ordered
- Fixed a bug with open actions causing double opening via the default and specified app
- CLI: Removed auto-installation of npm dependencies through the downloaded npm
- Developer Tools: Added
Open Support Directory
action to local dev extensions - Developer Tools: Removed auto-injecting of globals for enabling React Developer Tools in dev mode
- Developer Tools: Added
prettier
checks to CLIlint
command - Documentation: Updates and fixes
- Forms: Fixed controlled updates for the
Form.TagPicker
- Navigation: Fixed a bug where a programmatic pop, followed by a manual pop (e.g. ESC) could lead to wrong state (
Issue #571)
- New API for Alert views: Alerts are useful for destructive actions or actions that require user confirmation; new methods let you display our beautiful native Alert component
(Issue #48)
- New API for interactive Toasts: you can now add buttons to Toasts, e.g. to give the user options for created items, to open the browser, or for any other relevant context (
Issue #438)
- New API for retrieving the current Finder selection: unlocks a couple of use cases for extensions that perform actions on selected files and folders (
Issue #153)
- Improved ranking for fuzzy search in lists with sections and keywords
- The icon of the
OpenWithAction
can now be customised - The env var NODE_EXTRA_CA_CERTS is now being propagated so that custom certificates can be configured
- Improved the CLI error message when an entry point file from the manifest is missing (
Issue #495)
- Textfields do not auto-transform certain characters such as dashes any more (
Issue #491 and
Issue #360)
- This CLI of this version contains an update of the build tool with changed (and "more compatible") heuristics around how
default
exports are handled. This means that you should double check whetherimport
statements for certain npm packages need to be adjusted.
Example:import caniuse from "caniuse-api"
has to be changed toimport * as caniuse from "caniuse-api"
because of the missingdefault
export of the builtcaniuse
library that has to run in a Node environment.
- Keywords added to list items are now matched again by prefixes (exact matches were required previously)
- Extensions are now checked for version compatibility before updating and installation
- New and updated templates available in the "Create Extension" scaffolding command
- Modifications to list item keywords could result in wrong list filtering
- Fixed a regression where the CLI would not automatically install dependencies when building the extension
- DatePicker form element now returns the time component when specified
- Animated toasts are now automatically dismissed when the extension is unloaded
- Forms don't accidentally trigger draft creation mode any more
- Extensions which are off by default are now correctly disabled
- Full fuzzy search by default for lists using built-in filtering
- Faster list loading times
- Better default auto-layout of list item title, subtitle and accessories
- Extension support directory does not need to be explicitly created any more
- Raycast is no longer automatically brought to the foreground for failure toasts
- New default action to open a bug report on production error screens in extensions
- Updated extension icons are now displayed without having to re-install the dev extension
- Focus is now kept on the current form element when re-rendering
- Caret does not jump to the end of the string in controlled textfields and textareas any more (one edge left that is going to be tackled in one of the next releases)
- "Disable pop to root search" developer preference is now only applied for commands that are under active development
- Documentation fixes and updates
- Updating of items and submenus while the action panel is open
- Supporting all convenience actions with primary shortcut (cmd + enter) on form views
- Better error handling when the API cannot be loaded after failed app updates
- Loading indicator in detail views when used in a navigation stack
- Improved ActionPanel updating performance
searchBarPlaceholder
updates when using the list in a navigation stack- Wrong action panel actions when popping back in a navigation stack
- Empty state flickering when updating the
isLoading
property in lists - Accessory and subtitle label truncation in lists
- Icon from assets tinting on dynamic theme changes
- Dynamic removal of form elements
- Open actions leading to Node env vars being set for the opened application
- Some extensions not getting loaded for a particular Node setup
- Local storage values being lost when extensions are automatically updated
- Fixed configuring
tintColor
for icons inActionPanel
andForm.Dropdown
- Fixed displaying submenu icons from local assets
- Fixed tinting of icons provided from local assets
- Fixed a crash with the
getSelectedText
function - Fixed the main window sometimes not shown when an error is thrown from a command
- Fixed the
OpenWithAction
not working for some apps - Fixed the list empty state not being shown in certain cases when using custom filtering
- Fixed the the topmost item not automatically being selected for custom list filtering
- Fixed the line number info in error stack traces sometimes not being correct
- Fixed an issue where installing store extension would sometimes fail
- Fixed a crash that could be caused by sending invalid codepoints from an extension
- Fixed a bug where no error would be shown when the runtime download failed
- Fixed reaching the max. call stack size when logging recursive object structures (this could happen when you console logged a React component, for example).
It's happening! We're opening up our API and store for public beta.
This is a big milestone for our community. We couldn't have pulled it off without our alpha testers. A massive shoutout to everybody who helped us shape the API. Now let's start building. We can't wait to see what you will come up with.