SSH & REMOTE

SSH Config Import

Bring SSH host entries into Chau7 when you choose.

Availability

Partially implemented in stable. Read the limits below before relying on this workflow.

Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.

The pain this solves

  • Copying SSH host details into a separate connection list can create duplicate work.

What ships with it

  • Parses supported SSH Host fields into a reviewable list.
  • Imports a selected or eligible non-wildcard entry only after a user action.
  • Watches for config changes to refresh parsed entries, but does not sync imported records or process Include and Match semantics.

Questions this answers

  • Can I import hosts from ~/.ssh/config?
  • Does Chau7 automatically sync imported SSH profiles?
  • Which SSH config directives are imported?

How it works

The SSH profile settings view reads and parses the configured SSH file, showing entries for review. Supported fields include Host, HostName, User, Port, IdentityFile, ProxyJump, and ForwardAgent.

You can import one displayed entry or choose Import All. Wildcard Host entries are skipped by the import-all path; import is an explicit user action rather than automatic profile creation on first launch.

The manager watches file changes to refresh its parsed entry list, but it does not automatically reconcile those changes into saved Chau7 connections. Include and Match processing is not implemented by the parser.

Why it matters

Reviewing SSH config entries can reduce duplicate data entry when building Chau7 connection records. Import remains explicit, so you can choose which parsed hosts become saved connections.

Frequently asked questions

Does Chau7 import every host on launch?

No. It loads the config entries for review; importing an entry or importing all eligible entries requires an explicit action.

Does a config edit update saved Chau7 connections automatically?

The parsed list is refreshed when the file changes, but imported saved connections are not automatically synchronized.

Are Include and Match directives fully evaluated?

The v0.5.1 parser does not follow Include files or evaluate Match blocks.