Loading...
Loading...
Connect this machine to the person's Catalyst Cloud tenant with their own personal key, cache the tenant contract, and verify. Use when a person is getting started, when their config is missing or broken, when they rotated their key, when a skill script exits 2 saying the machine is not connected, or when they ask which tenant this machine belongs to. The key names the tenant and the person, so nobody types an account id. Installing the skills is not this skill's job; the agent's own install command did that.
npx skill4agent add coalesce-labs/catalyst-cloud-skills connect-meCATALYST_CLOUD_TOKEN=<your-personal-key> catalyst-skills logincatalyst-skills login--key <personal-key>npx @catalyst-cloud/catalyst-skills loginCATALYST_CLOUD_BASE_URL--base-url~/.config/catalyst-cloud/customer.jsonuser~/.config/catalyst-cloud/contract.jsoncatalyst-skills replica start --detachlogin --start-replicacatalyst-skills replica statusctc_acct_Connected to <name> (<slug>)Connected as <label> (<role>)node scripts/verify-connection.mjscatalyst-skills readycatalyst-skills replica start --detachcatalyst-skills replica statusreferences/keeping-the-replica-running.md401--base-url403catalyst-skills statuscatalyst-skills contract--refresh--path teams.0.stagescatalyst-skills replica statuscatalyst-skills ready| when | read |
|---|---|
| the person wants the replica writer to survive a reboot, or asks what it stores and whether anything needs cleaning | |
| the full readiness vector and what each check means | the |
CATALYST_CLOUD_TOKEN--account