Connect to editor

Access the code editor directly from your browser to edit files on remote servers.

Open the editor

The editor opens through a work session. You request a session with the Code editor feature, and once it’s approved you launch the editor from the session.

  1. On a server card or detail page, click Connect (or open Sessions and create a new session).
  2. In the request, include the Code editor feature, then submit. See Request a session.
  3. Once the session is Active, open it and click Launch on the Code editor feature. If more than one server in the session has the editor enabled, pick the server.
  4. The editor opens in a new browser tab.

You can also launch the editor from your active sessions on the Dashboard.

Requirements

  • Server is commissioned and Online
  • Server setting: Editor enabled (set by the server owner—see Manage servers)
  • You have an Active work session that includes the Code editor feature for the server
  • You belong to a group assigned to the server (or are a workspace administrator)

Account selection

The account you connect as depends on the server’s operating system:

Linux servers: You always connect as your own account—your Alpacon username is used as the remote user. There is no system-account selection. For privileged actions, use sudo with MFA.

macOS servers: Users with sudo privilege can also select from available system accounts on the server. Connecting with a system account may require MFA authentication depending on workspace security settings.

The editor is not available on Windows servers.

For full details, see Account selection.

MFA authentication for system account access

When workspace security settings require MFA for privileged access:

  1. Select system account and click Connect
  2. A notification appears indicating MFA is required
  3. You are redirected to the MFA authentication page
  4. Complete authentication (TOTP, email, phone, or WebAuthn)
  5. After successful verification, you are automatically redirected back to the editor
  6. The connection is established and the editor opens

MFA verification remains valid for the duration configured in workspace settings. Subsequent system account connections within this period will not require re-authentication.

First-time connection

The first time you connect to a server via the editor, the editor environment is automatically installed. This process may take a few minutes.

Connection steps:

  1. “Installing editor environment…”: the editor is being installed on the server
  2. “Starting editor…”: the editor is starting up

Once it’s ready, the editor opens.

Subsequent connections to the same server will be faster as the environment is already installed.

Troubleshooting

Editor shows “Connection Error”:

  • Verify the server is connected and online
  • Click Retry to attempt reconnection
  • Click Back to Servers to return to the server list

Editor stuck on “Installing”:

  • First-time installation may take a few minutes
  • If installation fails, click Retry

MFA authentication fails:

  • Ensure you have enrolled an MFA method accepted by the workspace
  • Check that your MFA device is available
  • Contact workspace administrator if issues persist
Last updated: