SSH Documentation

1. 1 Open SSH and create a connection.
2. 2 Enter a display name, host, port, and username.
3. 3 Choose password, private key, or no authentication. For a private key, enter the local key path and an optional passphrase.
4. 4 Use Test connection, then Save. Stored passwords and passphrases are represented by local credential references; reopening the form does not reveal the secret.

Use the SSH sidebar search to match connection names, hosts, usernames, or ports in the active workspace. It does not filter SSH Tasks or terminal sessions and does not change saved connections. Clear the search to restore the normal list.

1. 1 Select a saved connection and connect to open a PTY-backed terminal session.
2. 2 Use the terminal normally. The session forwards keyboard input and resizes the remote PTY with the pane.
3. 3 Use split panes, output search, log copy/export, and the context menu for Copy, Paste, Paste Selected Text, and Select All.
4. 4 Close the session when finished. Active sessions use a confirmation flow before closing.

On first connection, review the host-key fingerprint before trusting it. A later mismatch is rejected instead of silently replacing the trusted key.

• ✓ Only trust a fingerprint that you verified through an independent channel.
• ✓ If a server key intentionally changed, reset the stored fingerprint from the connection UI and reconnect to review the new value.
• ✓ Unfour tracks failed and reconnecting states and preserves failed session tabs so the error remains visible.
• ✓ Reconnect restores the terminal transport; verify remote state before resuming an interrupted command.

Unfour records structured command history after a command is echoed by the remote shell. History is scoped to the workspace and connection, bounded locally, and conservatively redacted.

• ✓ Type at least two characters at a detected shell prompt to see up to six matching suggestions.
• ✓ Use Up and Down to choose, Tab or click to insert, and Escape to dismiss. Enter always submits the current line.
• ✓ Password-prompt input is not stored, and commands that cannot be classified safely may be excluded or shown as redacted.
• ✓ MCP history queries can filter the current workspace by connection, text, time range, and result limit; they never return terminal buffers or raw session logs.

Open Remote Files from a connected terminal session. The SFTP panel uses that session and connection to browse the remote filesystem.

• ✓ Open directories, enter a remote path, go to the parent directory, and refresh the listing.
• ✓ Upload a local file or use drag and drop, and download a selected remote file.
• ✓ Create folders, rename entries, delete selected disposable paths, and copy a remote path.
• ✓ View transfer progress and cancel an active transfer. Unfour allows one streamed upload or download per SSH connection at a time.

1. 1 Connect to a trusted SSH server and open Remote Files. Find a regular UTF-8 text file no larger than 1 MiB, such as a small configuration file or log excerpt.
2. 2 Open the file context menu and choose Preview. Read the content in the read-only dialog; choose Copy content only if you want it on your clipboard.
3. 3 Close the dialog when finished. Preview does not edit the remote file or persist its content in history or shared application caches.

UTF-8 with or without BOM is supported. Binary data, unsupported encodings, non-regular files, and files over 1 MiB are rejected. Permission and connection errors are shown; reads time out after 30 seconds.

An SSH Task is a saved, serial sequence of enabled command, upload, and download steps. Tasks belong to a workspace and may have a default connection.

Use previous parameters explicitly recalls the last run; ordinary Run uses current defaults. From a completed history entry or result panel, prepare a rerun of a successful, failed, or cancelled task. Review the current saved task, target, environment, and inputs before starting. Safe manual values can be restored, variable sources resolve again, and sensitive manual values require re-entry. Missing or changed resources must be resolved first. Legacy runs without recall context use current defaults.

1. 1 Open Tasks, create a task, and add steps in the required order.
2. 2 Use {{name}} placeholders in supported command and path fields. Run inputs can be prefilled from workspace globals and the selected environment; mark sensitive inputs as secret.
3. 3 Review the target connection, resolved inputs, and enabled steps in the Run dialog, then start the task.
4. 4 Watch the live transcript and step status, then inspect persisted run summaries and logs. Cancel a running task when necessary.
5. 5 Scroll up to pause automatic following while reading earlier output. Returning from another module keeps your reading position; use the follow control to resume live output.