Something Not Attaching?

A session will not connect

If the agent has neither an SSH key nor a password saved, the app tells you that directly and prompts for a password on the spot rather than failing with a generic network error. If it still will not connect, check the primary host is reachable first — an alternate host is only tried when the primary fails outright, and both hosts share the same stored credentials, so a bad password fails the same way on either one.

It attached to the wrong screen session

GNU screen matches session names by prefix, so a session named opus_home can be mistaken for a live opus_home-myproject. The Architect matches the exact name and attaches by pid-qualified id, or creates a fresh session if none matches — it never attaches to the nearest guess. If you are still seeing the wrong session, confirm the agent's session name field matches what screen -ls reports on the host.

Colors look wrong under screen

GNU screen versions before 5.0 mangle truecolor escape codes. Turn on Legacy screen color fix in that agent's settings — it switches to a 256-color terminal type instead of truecolor. Screen 5.0 and newer render truecolor correctly and do not need it; tmux and direct sessions are unaffected either way.

I lost my license key

There is no account to recover it from, only the email it was sent to. Write to info@rmrsolutions.us from the address you paid with (or requested a Linux key with) and we will resend it. If two devices need the same license, export your configuration over SFTP from the licensed device — the key travels with it and the next device's first-run wizard picks it up.

My key will not activate

Keys are locked to the platform they were issued for. A Windows key will not activate macOS, and neither activates Linux. The app states which platform a key failed to match rather than failing silently. If you bought the wrong platform, the terms of sale cover the 30-day refund.

Where do session logs go?

Only if you turned on Log Traffic in Settings → Advanced — it is off by default because it records everything typed, unredacted, including anything entered at a remote prompt. The resolved path is shown right on that toggle. Delete a single session's log from the trash icon in its viewer, or clear everything from Delete All Logs in the same section.

A port forward is not coming up

A forward failing never blocks the SSH connection itself — the terminal still opens, and the failure shows in the port-forward status on that screen. The most common cause is two agents claiming the same local port; the app warns about that in the agent form before you save, and at connect time the session that already holds the port keeps it rather than both fighting over it.

Something else

Write to info@rmrsolutions.us. Include the platform you're on (Windows, macOS, Linux, or a beta build) and, if it's a connection problem, whether the host runs screen, tmux, or neither — that alone rules out most causes.