horizon-cloud

Horizon cloud MCP

Use this skill for cloud offers, the cloud list of your workspace, Upkeep, companion workers, a worker's Local Network Bridge, and GitHub access on a cloud worker. Read the cloud reference for the server and operation you need. Use tools from the connected server and their current schemas. Do not substitute private Horizon state for MCP results. Cloud-list worker_image and image_publication are retained metadata from the matching cloud runtime, or null when unavailable or the image is unresolved. Registry publication includes an opaque nonsecret grant ID, never a credential value or path. These fields do not prove current registry access.

Hetzner offers include all current x86 types in permitted locations. The configured server types are fallback preferences; they do not restrict explicit worker choices.

Cloud cards show the last-read tailnet device name under Connections > Tailnet. Copy includes the MagicDNS domain when the worker reports it. A stable-name fallback accepts horizon-tailnet-contract=2 or horizon-tailnet-contract=4; it does not supply an unknown domain. Marker 2 qualifies this display fallback only; selected-tailnet operations require marker 4. Connect again to refresh names after an administrator rename.

A selected tailnet requires horizon-tailnet-contract=4 and an auth key with only tag:horizon-worker. The tailnet policy must define this tag in tagOwners. The worker checks Self.Tags after enrollment and once at each resume. An untagged node or a node with extra tags is refused and logged out. There is no continuous tag monitoring or separate tag for each workspace. The tailnet policy controls reachability. The quick-start pin contains marker 4; selected-tailnet startup still requires storage that enforces private root modes. The tested RunPod persistent storage does not and is unsupported. Never weaken these checks; None does not bypass isolation. CPU evidence is not GPU qualification.

Personal API token and OAuth client bindings stay in the desktop OS store, independently of enrollment auth keys. Stored presence reports kind only; it does not prove API validity, scope or network access. Saving does not remove nodes. Never pass an API secret to MCP or a worker. Settings > Tailnets displays nonsecret API credential status and supplies masked owner entry, replacement and removal. Saved values never fill a draft. Read cloud_companions.tailnet_api_credentials for cached ready, pending or unavailable status without Settings. The CLI is cloud_deploy tailnets STATE_ROOT [TAILNET_ID]. API status does not qualify an older worker image. Cached status is not an OS-store watcher; use Tailnets Refresh for an explicit fresh read. Never pass an API secret to MCP. Use tailnet_api_credential to request set_personal_token, set_oauth or remove for an exact saved tailnet ID and caller-chosen UUID request ID. Set requests carry kind metadata only; the person enters values and selects Save in Settings. The person fulfills it in Settings > Tailnets; requests never open Settings or authorize a write. Read status with the same IDs after a lost answer. cancel cancels only a pending request; a running transaction remains uncertain until its result arrives. Credentials are desktop-global, so a workspace agent cannot approve its own request. Status qualification uses the production UI, actual CLI and normal AGENT public MCP responses; baseline id/name evidence alone does not qualify API status.

Machine-local destination preference helpers retain a checkout/profile scope and nonsecret account or exact registry grant metadata. The launch engine retains that choice before image work. A saved preference is not proof of authentication or registry permission. Keep these settings outside repository files and use the shared transactional save helper to preserve other windows' choices.

Image publication credentials belong on the host. An operation preparation helper retains the authenticated provider account ID and owns a separate temporary Docker login. The engine retains its account and renews the operation login before push. Prebuilt profiles still require an explicit image; build profiles may omit it. Never copy publication credentials to a worker or repository.