Extension
https://github.com/raycast/extensions/tree/main/extensions/super-productivity
Raycast Version
v0.71.0.0
OS Version
Windows 24H2 (SuperProductivity 18.19.0W)
Description
The Super Productivity Raycast extension does not include the Local REST API access token in its HTTP requests. The extension currently only reads apiBaseUrl from preferences and never sets Authorization: Bearer . The Local REST API requires the token for every endpoint except /health, so authenticated endpoints return 401 and the extension cannot list or control tasks.
Steps To Reproduce
- In Super Productivity (desktop), enable Settings → Misc → Enable local REST API and copy the Access Token.
- In Raycast, open the Super Productivity extension (no access token configured in preferences).
- Run the View Tasks command (or any command that calls /tasks).
- Observe failure: requests to /tasks return 401 / the extension shows a connection/API error and cannot list tasks. /health may still succeed.
Current Behaviour
Requests made by the extension (except /health) lack Authorization: Bearer header and thus the extension receives 401 UNAUTHORIZED responses or fails to operate against authenticated endpoints.
Expected Behaviour
Add an "Access Token" (password) preference to the extension and include Authorization: Bearer in request headers when present. Optionally show a clearer toast on 401 to help users set/refresh their token. Document where to find the token and the dev env overrides (SP_FORCE_LOCAL_REST_API and SP_FORCE_LOCAL_REST_API_TOKEN).
References
Extension
https://github.com/raycast/extensions/tree/main/extensions/super-productivity
Raycast Version
v0.71.0.0
OS Version
Windows 24H2 (SuperProductivity 18.19.0W)
Description
The Super Productivity Raycast extension does not include the Local REST API access token in its HTTP requests. The extension currently only reads apiBaseUrl from preferences and never sets Authorization: Bearer . The Local REST API requires the token for every endpoint except /health, so authenticated endpoints return 401 and the extension cannot list or control tasks.
Steps To Reproduce
Current Behaviour
Requests made by the extension (except /health) lack Authorization: Bearer header and thus the extension receives 401 UNAUTHORIZED responses or fails to operate against authenticated endpoints.
Expected Behaviour
Add an "Access Token" (password) preference to the extension and include Authorization: Bearer in request headers when present. Optionally show a clearer toast on 401 to help users set/refresh their token. Document where to find the token and the dev env overrides (SP_FORCE_LOCAL_REST_API and SP_FORCE_LOCAL_REST_API_TOKEN).
References