Server Access · Setup guide

How to connect an SSH server to your AI worker with Outloop

Q: Does the worker receive my private SSH key?

Outloop protects the private key through macOS Keychain. The worker requests execution through Outloop. Copy the public key to the authorized server account.

Q: Does a Workspace restrict every file on the server?

Workspace authorization controls which connection the worker may use. The remote account controls what that connection can read or change. Configure both boundaries.

Q: Should I leave an SSH terminal open?

The connection is used when work requires it. Your Mac must be available to execute through Outloop. After a restart, check connection readiness before resuming work.

Q: Can I retry a task after an interruption?

First inspect the job status and server state. A disconnected request may already have made changes. Retry only after establishing what completed.

Connect your server once. Give your AI worker approved access to run commands, manage files and maintain WordPress websites without exposing your private SSH key.

Outloop creates and protects the private key on your Mac. You install its public key on the server, authorize the correct Workspace and give the worker a task. Connections open when needed.

Step 1 of 8

Open Server Access

In the Outloop sidebar, choose Server Access under Access. Select Connect a server.

Have a company-controlled Mac, an SSH-enabled hosting account and an authorized staging target ready. Ask your provider for the server address, SSH port, account name and trusted host fingerprint.

Outloop sidebar with Server Access selected and the Connect a server button. — Actual product screen. Customer connection details are redacted.

Step 2 of 8

Enter server details

Select the intended Workspace. Give the connection a recognizable Name, then enter Server address, Port and Account.

The address identifies the server. The port identifies its SSH service. The account determines the authority the worker receives. Obtain the values from your hosting administrator rather than assuming a default port or using the website administrator login.

ScalaHosting/SPanel and cPanel installations may expose SSH settings differently. Confirm shell access is enabled for the intended account.

Actual connection form with Workspace, Name, Server address, Port, Account and Check server identity. — Blank connection form. No connection was created for this capture.

Step 3 of 8

Verify server identity

Choose Check server identity. Compare the returned fingerprint with one supplied through your trusted hosting console or administrator. Confirm the exact server and fingerprint before trusting it.

If the fingerprint differs unexpectedly, stop and investigate. A server rebuild or key rotation can explain a change, but an unexpected change must not be accepted automatically.

Step 4 of 8

Create the SSH key in Outloop

Use Outloop’s key-creation flow after verifying the server identity. Outloop keeps the private key in its protected host infrastructure. The public key is the part to give the authorized server administrator.

On an existing connection, Show public key reveals the public key with a Copy button. The screenshot shows that real existing-key screen.

Existing Outloop connection with Show public key open and a Copy button. Key and connection details are redacted. — Existing public-key display. Private keys never belong in agent prompts or project files.

Step 5 of 8

Authorize the public key on the server

Ask the hosting administrator to install the copied public key for the intended SSH account. In a hosting panel, use its public-key import and authorization workflow. Some panels require an additional authorization action after import.

For a directly managed account, the administrator can add the complete public-key line to that account’s ~/.ssh/authorized_keys, with ownership and file permissions appropriate for its SSH configuration. Keep the key on one line. Follow your provider’s account-specific instructions. cPanel documents importing and authorizing public keys; ScalaHosting documents enabling SSH in SPanel.

Installing this public key permits authentication as the remote account. Outloop retains the private key on your Mac.

Step 6 of 8

Test and authorize the Workspace

Select Test connection and inspect the result. The reviewed connection displayed Ready, an OK last test and long-job tracking.

Under Workspaces that may use it, select the intended Workspace and choose Add when needed. Confirm it is On.

Workspace authorization controls use of the connection. Server account permissions separately control files, databases and commands.

Ready server connection and an enabled DEMO Workspace in Outloop. — Ready connection and Workspace authorization. Identifying fields and test-account details are redacted.

Step 7 of 8

Give Ollie a verifiable first task

In the intended client Workspace, open AI Worker. Supply the approved staging target through its context, then use this inspection-only brief.

Use only this Workspace’s approved SSH connection and the authorized WordPress staging installation. Discover the available connection and confirm the intended staging target. If either is ambiguous, ask before proceeding. Perform a read-only inspection: identify the remote account and working directory, check whether WP-CLI is available, and report the WordPress version and plugin inventory from the confirmed installation. Do not read credential files, dump environment variables or databases, change files, update plugins, submit forms or touch production. Report each check and its result, available execution references, and anything you could not verify. If execution is interrupted, inspect status before retrying.

Check that the report names the correct environment, distinguishes successful checks from unknowns, and provides the available execution record. Verify the reported result before authorizing changes.

Step 8 of 8

Manage access and troubleshoot

After restarting the Mac: Open Outloop, check connection readiness and test before continuing. Confirm any interrupted job’s outcome separately.
Server unavailable: Check the address, port, network reachability and whether the host is running SSH. A timeout does not establish whether an earlier task finished.
Host identity mismatch: Verify the new fingerprint with your administrator before using Re-check identity to establish trust again.
Permission denied or public-key failure: Confirm the account, installed public key, panel authorization and SSH filesystem permissions. An SSH account can differ from a WordPress login.
Interactive password prompt: Use the supported key-based path. Resolve password-only or interactive authentication with the provider before running an unattended task.
Long job interrupted: Inspect job status and server state before retrying. Record uncertainty if you cannot prove completion.
Disable access or rotate: Turn off or Remove a Workspace’s access to the connection. Coordinate New key with installing the replacement public key and retiring the old server authorization. Verify revocation and active-job behavior for your installed release.

What can your AI worker do next?

Diagnose WordPress errors and inspect selected logs.
Create, duplicate and update pages, copy and SEO metadata.
Edit templates, CSS, JavaScript and animations.
Transfer files and verify their integrity.
Use installed WP-CLI, Git, scripts and deployment tools.
Perform authorized database inspection and maintenance.
Operate separately authorized client servers.
Combine server work with approved browser and API access.

Each task depends on the remote account’s permissions, installed tools, WordPress architecture and authorization.

Frequently Asked Questions

Server Access questions

Does the worker receive my private SSH key? +

Does a Workspace restrict every file on the server? +

Should I leave an SSH terminal open? +

Can I retry a task after an interruption? +