Skip to content

docs: document definition of workspace activity #16941

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Mar 21, 2025
Merged

docs: document definition of workspace activity #16941

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5e72d54
draft improvements to workspace activity
EdwardAngert Mar 14, 2025
4e2a304
rephrase pty to reconnection
EdwardAngert Mar 14, 2025
48f5d01
replace quotes with bold
EdwardAngert Mar 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
rephrase pty to reconnection
  • Loading branch information
@EdwardAngert
EdwardAngert committed Mar 14, 2025
commit 4e2a304a064d92af9a33da3f2b8e65875f4972d6
4 changes: 2 additions & 2 deletions docs/user-guides/workspace-scheduling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ A workspace is considered "active" when Coder detects one or more active session

- **VSCode sessions**: Using code-server or VS Code with a remote extension
- **JetBrains IDE sessions**: Using JetBrains Gateway or remote IDE plugins
- **Terminal sessions**: Using the web terminal (reconnecting PTY)
- **Terminal sessions**: Using the web terminal (including reconnecting to the web terminal)
- **SSH sessions**: Connecting via `coder ssh` or SSH config integration

Activity is only detected when there is at least one active session. An open session will keep your workspace marked as active and prevent automatic shutdown.
Expand All @@ -66,7 +66,7 @@ The following actions do **not** count as workspace activity:
- Accessing ports through direct URLs without an active session
- Background agent statistics reporting

To avoid unexpected cloud costs, close your connections (IDE windows, SSH sessions, etc.) when you finish using your workspace.
To avoid unexpected cloud costs, close your connections, this includes IDE windows, SSH sessions, and others, when you finish using your workspace.

## Autostop requirement

Expand Down
Loading