# Dev Workspaces A workspace is a browser editor attached to one of your projects. It runs your project files, a terminal, and preinstalled Python, Rust, Nim and Swift toolchains. `sudo` and `apt install` work with no extra setup; ports below 1024 cannot bind, so use a high port and publish it through a tunnel. The editor opens with a **DevPlace Code** terminal already running the `dpc` coding agent and a plain shell beside it, and it trusts every folder, so nothing opens in Restricted Mode. Its appearance and boot behaviour are your own preferences, readable and writable through the two `/workspace/editor` endpoints below and explained on [the workspace editor page](/docs/workspace-editor.html). Editor preferences apply on the next workspace start. A **tunnel** publishes one port from inside your container on a public HTTPS hostname of the form `<port>-<name>.tunnel.pravda.education`. **Tunnel URLs are public and unauthenticated** - anyone with the link can reach whatever you are serving. Forwarding a port in the editor's **Ports** view creates the tunnel for you through the same endpoint; un-forwarding it does not remove the tunnel. Workspaces are bounded: a count limit per user, a disk quota, an egress quota, and a tunnel limit. An idle workspace is warned about, then stopped, then warned again, then removed. Every warning arrives as a `workspace` notification and states exactly what happens next and when.