Code Editor
Code Editor opens a Visual Studio Code environment in your browser. It's code-server, working directly on your home directory: real files, your own permissions, and VS Code's search, extensions, Git support, and integrated terminal.
Your account becomes a development environment. Edit an application, test it, and it's already deployed; the files never left the server.
Opening the editor starts your account's editor instance in a new tab, or connects you to it if it's already running. Its theme and language match your panel settings, and its state (extensions, settings, and the open workspace) stays in your home directory between sessions.
The editor needs persistent services, like app servers and containers. Your provider must turn them on for your account.
Which tool to use
It uses far more memory and CPU than the file manager, all of it counted against your account's resource limits. A long editing session takes the same memory as your websites.
| Task | Tool |
|---|---|
| Browse, upload, set permissions, edit one file | File Manager |
| Real development | Code Editor |
The file manager also has the panel's own actions, which the editor doesn't: web permissions, the trash, shares, and archives.