aws / aws/amazon-sagemaker-feedback
Support connecting to alternative VSCode-based editors (forks) for SageMaker remote access
- Dominant language
- No language data
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### Product Version
- [ ] Amazon SageMaker Studio Classic
- [x] Amazon SageMaker Studio
- [ ] It is not related to SageMaker Studio
### Product Category
Other
### Description
Currently, SageMaker Studio only supports Visual Studio Code Remote, which prevents users from connecting with forks like Cursor. These editors are API-compatible but cannot connect under the current integration. Supporting any VSCode-based editor would give teams more flexibility.
### Other Details
_No response_
Contributor guide
Research direction
The issue names no implementation files, tests, or entry points. Start by locating the SageMaker Studio remote-access integration and determine how it identifies Visual Studio Code; done means compatible forks such as Cursor can connect through the same integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, vscode
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100