Skip to content

Admin and user docs for accessing Cursor/WindSurf #16919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
matifali opened this issue Mar 14, 2025 — with Slack · 2 comments · Fixed by #17092
Closed

Admin and user docs for accessing Cursor/WindSurf #16919

matifali opened this issue Mar 14, 2025 — with Slack · 2 comments · Fixed by #17092
Assignees
Labels
docs Area: coder.com/docs

Comments

Copy link
Member

matifali commented Mar 14, 2025

we recently added support for WindSurf/Cursor in our VSCode extension.
So we should probably include them in the docs.

IMO, they don't have to be as detailed as the VSCode page is. As these IDEs share the same settings and extensions.

Slack Message

@matifali matifali added the docs Area: coder.com/docs label Mar 14, 2025 — with Slack
@matifali
Copy link
Member Author

A seamless WindSurf support depends on extension being available in the OpenVSX registry.

@EdwardAngert EdwardAngert removed their assignment Mar 17, 2025
@EdwardAngert
Copy link
Contributor

EdwardAngert added a commit that referenced this issue Apr 1, 2025
closes #16919 

- [x] cursor doc
- [x] windsurf doc

from
#16919 (comment):
- add to access-workspace
- link to module(s)
- how to windsurf with ssh
- temp: install vsix manually (Windsurf)
   - from <https://github.com/coder/vscode-coder>
- log in first
- search extensions for Coder
- ask your admin to add a module:
https://registry.coder.com/modules/cursor

---------

Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>
Co-authored-by: M Atif Ali <atif@coder.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Area: coder.com/docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants