Add a key for Skyflo's agent
Open Settings › Providers and find the Skyflo card. The built-in key controls support Moonshot and Z.ai. Add the key through the provider's form and use Test key or Retry to check it. Keys stay in the macOS Keychain; they are not managed-model allowance.
Moonshot provides Kimi models. For Z.ai, choose the platform that matches your key: pay as you go or GLM Coding Plan. GLM-5.3 requires the Coding Plan platform. An old mainland Zhipu endpoint is retired; use a supported Z.ai key when the product reports Endpoint retired.
Other providers
OpenAI, Anthropic, Google and other provider keys are not added through these built-in Skyflo key forms. Use a compatible external coding agent's own configuration. For example, Pi can expose providers and local models configured in Pi. Their availability depends on that agent, its configuration and your access.
Disable or remove a key
Turning off a provider keeps its key but removes it from new work. Removing the key makes its models unavailable until you add one again. Existing missions remain on the Mac.
A rejected key and an unreachable provider are different failures. Check the key and selected platform for the first; check connectivity and provider availability for the second. Avoid repeatedly replacing a key during a network outage.
What leaves the Mac
Your own-key requests go to the chosen provider. Keeping a key in Keychain does not mean prompts and code stay local when a remote model processes them. Review the provider's data terms and the information included in the mission.
Skyflo Cloud uses Skyflo-managed models. Your Mac's model key is not moved to its machine.