Skip to content

Conversation

@NewtonDer
Copy link
Contributor

Issue

Description of Changes

Problem:
If user starts a process in the Terminal and closes the browser tab, the SageMaker Code Editor space will still automatically shut down after the idle timeout.

Explanation:
The sagemaker-idle-extension's checkTerminalActivity method halts when the browser tab is closed. Thus, it is unable to detect any running processes and avoid the idle timeout.

Solution:
Moves sagemaker-idle-extension's checkTerminalActivity method to server side in webClientServer. This method is called in the /api/idle handler, which currently happens on a 1 minute interval.

Testing

Tested with a custom image deployed in a SageMaker AI Studio domain.

Screenshots/Videos

Additional Notes

This same fix is already launched and working in sagemaker-code-editor versions 1.5, 1.6, and 1.7.

Backporting


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@NewtonDer NewtonDer requested review from a team as code owners December 9, 2025 21:51
Copy link

@aakashmandavilli96 aakashmandavilli96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@NewtonDer NewtonDer merged commit 2262020 into aws:1.0 Dec 9, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants