Local-first execution keeps prompts and repo work on the machine running KCC unless sync or hosted control-plane features are explicitly used.
Security
Local-first architecture reduces unnecessary exposure.
KCC is strongest when it is explicit about what stays local, what can sync, and what the hosted control plane is allowed to do.
Account sessions use native secure storage where available: Windows DPAPI, macOS Keychain, and Linux Secret Service.
Approvals, audit, and machine revocation help teams control high-risk actions without slowing down the local CLI.
Enterprise security reviews, questionnaires, and procurement requests should go through the KCC contact path.