Your Mac.
All in Term.

Work on your Mac

Select the local terminal action on the start screen. Try a familiar command to see where you are:

pwd
ls -la

Use the command palette to discover actions, and save frequently used commands as snippets.

Connect over SSH

1. Add a server and give it a recognizable name.
2. Enter its hostname or IP address, SSH port (usually 22) and username.
3. Select password or SSH key authentication and supply your credentials.
4. Save the connection and open it. Review the host identity before trusting a new server.

Example: production-web · 203.0.113.10 · port 22 · user deploy. Replace these sample values with your own.

Explore the connected tools

With an SSH session connected, open SFTP to browse and transfer files. Use the available tools to inspect processes, system health, databases or Nginx.

Tool availability depends on the software installed on your server and your account permissions. Review commands and configuration changes before applying them.

Need a hand?

Password authentication

1. Create a connection with a descriptive name such as Staging web server.
2. Enter the server address, port and username supplied by your hosting provider or administrator.
3. Choose password authentication and enter that server user's password.
4. Save and connect. A hosting dashboard password may be different from your SSH password.

Private key authentication

1. Choose private key authentication in the connection form.
2. Select your private key file, for example ~/.ssh/id_ed25519.
3. If the key is encrypted, enter its passphrase in the passphrase field.
4. Make sure the matching public key is authorized for the same user on the server.

Check the connection

After connecting, these read-only commands help you confirm the current user, machine and directory:

whoami
hostname
pwd

For example, deploy, staging-web-01 and /home/deploy indicate the session belongs to that remote account. Your actual output will differ.

Keep connections organized

Give production and staging hosts distinct names, groups and colors in the connection form. Keep separate tabs for local work and remote operations.

Saved credentials use macOS Keychain-backed encryption through the app's secure storage. If secure storage is unavailable, resolve the reported save error before assuming a connection was saved.

Upload and review a configuration

1. Open SFTP from a connected remote session and navigate to the destination directory.
2. Drag a local file or folder from Finder into the SFTP workspace.
3. Watch transfer progress and confirm completion before using the file.
4. Open a text file in the remote editor, review the contents and save deliberately.

For a deployment folder, compare local and remote versions first, then review individual differences before pushing or pulling files. Keep a backup before overwriting configuration.

Inspect data without losing context

1. Open the database workspace and choose PostgreSQL or MySQL / MariaDB.
2. Enter the database host, port, database name and credentials for your environment.
3. Explore schemas, tables, columns, keys and indexes, then page through rows.
4. Inspect large cell values separately and export the results you need.

Start with a small read-only query. Replace the example table with one in your database:

SELECT * FROM your_table LIMIT 25;

Database credentials can differ from SSH credentials. The database host must be reachable from the connection environment.

Understand a traffic spike

1. Open Nginx on the server handling your traffic.
2. Review the selected day's request totals and response status distribution.
3. Compare top routes, bot traffic and upstream error patterns to locate the change.
4. Inspect the relevant virtual host and logs before changing configuration.

Daily aggregates and individual log samples serve different purposes: detail rows may be bounded even when totals cover the day. Results depend on readable logs, their format and retention.

After editing configuration, validate with nginx -t before reloading. A reload affects the running service.

Inspect services in place

Docker: inspect container state and logs, then review discovered Compose definitions. Confirm the container and environment before using start, stop or restart controls.

Redis: search for a key pattern such as session:*, inspect its value and review TTL. Confirm the selected database and key before editing values or expiration.

These tools require the relevant service and access permissions on the connected host.

Find the cause of a slow server

1. Check CPU, memory and swap to understand the overall pressure.
2. Sort processes by resource usage and inspect their commands and owners.
3. Use the listening port view to identify which process owns a service port.
4. Review mounted disk capacity and scan directories to locate storage growth.

A resource spike is a clue. Review the process and service context before terminating anything.

Turn findings into a maintenance plan

Run a health scan and read the evidence behind each finding. Inspect storage cleanup candidates, failed services, SSH settings and exposed listeners before choosing an action.

Review cleanup selections and estimated recoverable space. If you configure scheduled care, check the schedule and execution logs afterward.

Security indicators guide investigation; an unusual process alone does not establish that the host is compromised.

Keyboard essentials

⌘ K

Open the command palette to find connections and saved commands.

⌘ T

Open a terminal tab.

⌘ W

Close the active tab. Finish running work before closing a session.

Save repeatable commands

Use Snippets for commands you revisit, with a descriptive title and category. For example, save a read-only disk check:

df -h

Find it through the command palette or Snippets sidebar. Review the active host and command before execution. History helps you revisit recent work; avoid putting passwords or tokens directly into shell commands.