Profiles represent SSH targets and now carry both connection data and lightweight operational context.
Phase 3 supports:
- default profile
- active profile
- favorites
- recently used profiles
- validation
- connection testing
- environment labels
- free-form tags
komu profiles listkomu profiles addkomu profiles show <name>komu profiles edit <name>komu profiles use <name>komu profiles test <name>komu profiles favoriteskomu profiles recentkomu profiles remove <name>
The current resolution order is:
- an explicitly provided
--profile - the active profile selected with
komu profiles use - the default profile
This keeps profile switching explicit while still making repeated shell use efficient.
Phase 3 validates profiles for:
- non-empty label
- non-empty host
- valid SSH port range
- non-empty username
- SSH key path presence when key-based auth is selected
Validation runs during add, edit, and status rendering.
komu profiles test <name> opens an SSH session and runs a minimal remote shell check. On success, KOMU records that profile as recently used and updates connection timestamps.
Favorites are manual. Recents are updated automatically when a profile is used for planning, inspection, execution, or connection testing.
This supports a smoother operator workflow without silently changing the active profile.
Profiles now include:
environmenttags
These fields are intended to support later work such as:
- staging or production grouping
- role-based target selection
- controlled fan-out execution
- reusable target sets
Phase 3 does not execute across profile groups yet, but the profile model is ready for that direction.