Skip to Content
Enderdash

Use the shell and manage host resources

Open a host terminal and inspect processes, services, and local users with the agent's permissions.

The Shell, Processes, Services, and Host users panels act on the machine that runs the agent, not on the game runtime. For game commands, use the console.

Before you begin

Each panel appears only when the agent reports its capability. A standalone agent on a host reports the most. A plugin inside a hosting provider's container often reports fewer, and the host may restrict what works.

Every action runs as the operating-system user that runs the agent. That user's permissions are the real limit. Members also need a scoped grant for each kind of operation. Shell also needs the host terminal plan feature.

A shell is full access as the agent user

Anyone who can open Shell can do everything that the agent's user can do on that host. Run the agent as a dedicated user with limited permissions, and grant shell access to few people.

Open a shell

  1. Open the server, then Shell.
  2. Wait for the prompt, then run a harmless command such as whoami.
  3. Make sure that the user and host are the ones you intend to change.

The session runs on the agent's host and ends when you close it or lose the connection. A command that must survive a disconnect needs a service manager, tmux, or a similar tool on the host.

Open Terminal preferences to change the font size, cursor, scrollback, and bell. Keep Paste guard on. It asks before sending a multi-line or large paste, which prevents an accidental run of copied text. In fullscreen, you can keep the screen awake and capture browser shortcuts where the browser supports it.

To run a command on a schedule, use an automation instead of an open terminal.

Inspect and signal processes

Open Processes and filter by name, path, command, or PID. The list shows the processes that the agent's user can see, with their memory use.

To stop a process, open Process options in its row and choose Terminate or Kill. Check the process name and PID in the dialog, then confirm with Terminate process or Kill process. Prefer Terminate, which asks the process to shut down. Use Kill only when the process does not exit, because it stops the process immediately and unsaved data is lost. A PID can belong to a different process after a restart.

Viewing and signaling are separate permissions. A member can be allowed to inspect processes without being allowed to signal them.

Stop a game server through its own console or service where possible. Killing its process can lose unsaved world data.

Start, stop, and restart services

Services lists the host's services with their status and whether they start automatically. It uses the host's service manager, such as systemd on Linux or launchd on macOS.

  1. Filter by name, display name, status, or PID.
  2. Open Service options in its row and choose Start, Stop, or Restart.
  3. For Stop, check the service name in the dialog and choose Stop service. The service stays stopped until someone starts it again.
  4. Reload the list and make sure that the status changed.

Service actions need an agent that runs as root on Linux and macOS, or as Administrator on Windows. Without that, the panel shows Service actions need an elevated agent and you can only view the status. If an action fails with a permission error, fix it on the host. Do not restart the service that runs the agent itself unless you have another way to reach the host.

Manage local users

Host users lists local accounts with their home directory and shell. Choose Create User to add a local account. Open User options in a row to enable, disable, or delete an account. Deleting asks you to confirm with Delete user, and you cannot undo it.

User management also needs an agent that runs as root or Administrator. Otherwise, the panel shows User management needs an elevated agent and the list is read-only.

Treat this as host administration. Check your organization's policy before you add an account, and never disable the account that runs the agent or your own access path.

If a panel or action is unavailable

  • The panel is missing: the agent does not report the capability, the plan lacks the feature, or your access does not include it.
  • You can view but not act: your grant covers inspection only. Ask an owner or admin for the specific action.
  • The host returns a permission error: change the agent user's permissions on the host. An Enderdash grant cannot exceed them.
  • The shell does not open: check the live connection.

Next: edit and transfer files or container platforms.

Was this page helpful?

Send a quick note if anything is missing or unclear.

Last updated on