Navigation
ELOWEN · Documentation

Last updated: October 27, 2026

Browse documentation · Your account's development environment
Computers, terminal and Git

Your account's development environment

Every account has a private home directory, HOME, that holds its Git, npm and tool configuration across Projects.

What HOME holds

HOME belongs to the account, not to a Project. It keeps your Git identity, npm configuration and tool settings, so the same tools behave the same way in every Project you work in.

Check the size and Git author

  1. Open Account → Development environment.
  2. Read Account HOME, HOME size and Generation.
  3. Check Author name and Author email under Git author. Change them and save if commits should carry a different identity.

An administrator can see the same values for another account.

Reset HOME

  1. Open Account → Development environment.
  2. Choose Reset HOME. A warning explains that Git, npm and tool configuration are removed.
  3. Confirm the reset.

Note: The reset is refused while the account has Active processes. Wait for them to finish, then try again.

Where commands run

  • A command in a managed Project runs inside that Project's environment, never in the server's own folder.
  • Commands that run directly on the host are Confined by default: they may only reach your Projects and your private HOME.
  • If the check that prepares confinement fails, the command is Refused rather than started without it.
  • An operator of the instance can allow directly run commands for an account, which shows as Not confined.

Read Autonomy & Safety for the instance-wide setting and its effect on all accounts.

Read Projects overview for the Project kinds, and Manage a managed environment for the environment a managed Project runs in. Administrators set the environment up in Set up an account development environment.