Connect File Layout

Connect persists a handful of files on disk so that aliases, host fingerprints, and licensing survive between runs. Use this page to find the defaults and learn how to relocate them when needed.

User-scoped directory (~/.connect)

Connect creates this directory on startup if it does not exist. It is the primary location for secrets that should stay tied to a specific OS account.

• ~/.connect/connect_aliases.enc — encrypted alias store, written with 0600-style permissions. Remove the file to clear stored endpoints.
• ~/.connect/known_hosts — cached SSH host fingerprints used during SFTP handshakes. Delete or edit the file if a server rotates keys.

Binary directory (same folder as connect)

Files that should travel with the executable are stored next to the binary. Path is discovered at runtime.

• connect — the CLI itself. Typical install paths include /usr/local/bin/connect or $HOME/.local/bin/connect.
• license.key — activation record saved after connect license activate. The CLI verifies that the license file and binary share the same owner.
• .connect_secret_key — key to encrypt alias files and other secrets; treat it as sensitive as the license file.

Quick reference

Path	Purpose	Notes
~/.connect/connect_aliases.enc	Alias definitions (encrypted JSON)	Created and updated by connect alias commands.
~/.connect/known_hosts	SSH fingerprint cache	Populated the first time you approve an SFTP host.
<binary_dir>/connect	Main executable	Copy to PATH.
<binary_dir>/license.key	Activated license blob	Must be readable by the same user that owns the binary.
<binary_dir>/.connect_secret_key	Installation-specific encryption key	Treat as sensitive as license.key.

Tip: need to relocate everything into /opt/connect? Move the binary there, copy the existing license.key and .connect_secret_key, then set PATH=/opt/connect:$PATH so the CLI finds its companion files.