Servers

Terminal tab

A real command line in the browser, with an AI helper beside it and a record of everything typed.

A genuine terminal, connected to your server, running in the browser. Anything you could do over SSH from your own machine you can do here — no client to install, no key to carry around.

If you have never used a command line, you do not need this tab. Everything common has a button somewhere else in the workspace, and the AI assistant can do the rest.

Using it

Click into the black area and type. It is a full interactive terminal, so editors (vim, nano), pagers (less) and interactive programs all work.

On a phone there is a key bar above the keyboard with the keys a phone keyboard does not have: Ctrl, Esc, Tab, ^C, ^D, ^L, arrows and | / - ~.

Ask AI — the sidebar

Beside the terminal is an AI helper that can see what you are doing.

  • Ask "what does this error mean?" and it reads the output.
  • Ask it to do something and it types the command into your session.
  • It obeys the same Read / Execute safety switch as the main chat: in Read mode it cannot change anything; in Execute it asks before each change. See The safety switch.

On a phone the helper stacks underneath the terminal instead of beside it.

Everything you type is recorded

Every command run in this terminal — by you or by the AI helper — is written to the Activity log with a timestamp and the exit code.

This is done with a hook inside that one shell session. Nothing is installed on your server and nothing is written to it. When the session ends, the recording ends.

There are things it cannot see, and the log marks each one as a gap rather than pretending otherwise:

  • Commands inside a nested shell (sudo -i, su -).
  • Commands inside a full-screen program (vim, mysql, top).
  • Shells other than bash and zsh.
  • Anything after someone deliberately switches the hook off.

The full list is in Activity log.

Sessions and timeouts

  • A session closes after 30 idle minutes. Reopen the tab to get a new one.
  • Sessions do not survive an update of DevOps Agent itself.
  • A live session answers only the person who opened it.

Safety

The terminal does exactly what you type, immediately, with no confirmation. There is no undo. Two habits worth keeping:

  • Back up a config file before editing it: cp file file.bak.
  • Read a rm -rf twice before pressing Enter. Especially the path.

If you want the safety rails, use the AI assistant instead — it asks before every change and refuses destructive commands unless you explicitly approve them.

Permissions

Operator and above. Viewers cannot open the Terminal. See Roles.