メニュー
Setting up a Golem Cloud account from scratch. Use when creating a Golem Cloud account, authenticating with Golem Cloud via the CLI, setting up a cloud profile, or deploying to Golem Cloud for the first time.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Invoking a Rust Golem agent method from the CLI. Use when asked to call, invoke, or run a method on a deployed agent using golem agent invoke.
Defining environment variables for Golem agents. Use when configuring env vars in golem.yaml at the component template, component, agent type, or preset level, passing env vars to individual agent instances via CLI, or using template substitution and merge modes.
Exposing a Rust Golem agent over HTTP. Use when the user asks to add HTTP endpoints, mount an agent to a URL path, or expose agent methods as a REST API.
Adding secrets to Rust Golem agents. Use when the user needs to store sensitive configuration such as API keys, passwords, or tokens that should not be checked into source control.
Calling Golem agents from external Rust applications using generated bridge SDKs. Use when the user wants to invoke agents from outside the Golem platform, from a Rust CLI, server, or any native Rust application.
Enabling snapshot-based recovery and implementing custom snapshot save/load functions for Rust agents. Use when adding manual update support, custom state serialization, or — equally importantly — when a long-running agent's oplog is growing large and recovery/replay is becoming slow (heartbeats, polling loops, recurring tasks, frequent state changes). Snapshotting compacts the oplog and lets recovery start from the latest snapshot instead of replaying full history.
| name | golem-cloud-account-setup |
| description | Setting up a Golem Cloud account from scratch. Use when creating a Golem Cloud account, authenticating with Golem Cloud via the CLI, setting up a cloud profile, or deploying to Golem Cloud for the first time. |
Both golem and golem-cli can be used — all commands below work with either binary. The golem binary is a superset that includes a built-in local server.
Golem Cloud is the hosted version of Golem. To deploy agents to Golem Cloud you need:
The CLI ships with a built-in cloud profile that points to https://release.api.golem.cloud with OAuth2 authentication. You can use it directly:
golem -C profile get # Show the built-in cloud profile
If you need a custom cloud profile (e.g., for a different cloud endpoint):
golem profile new my-cloud --url https://release.api.golem.cloud --set-active
When no --static-token is provided, the profile uses OAuth2 (GitHub) authentication — a browser window will open on first use.
Authentication happens automatically the first time you run a command against the cloud profile. The CLI will:
~/.golem/config.json)To trigger authentication explicitly:
golem -C account get # Triggers OAuth2 flow if not yet authenticated
The CLI displays:
┌────────────────────────────────────────┐
│ Authenticate with GitHub │
│ │
│ Visit the following URL in a browser │
│ │
└────────────────────────────────────────┘
https://github.com/login/device
──────────────────────────────────────────
Waiting for authentication...
Follow the URL, authorize the application, and the CLI will complete automatically.
After authentication, you can manage your Golem Cloud account:
golem -C account get # View account info
golem -C account update "My Name" "me@example.com" # Update name/email
golem -C account new "Team Account" "team@example.com" # Create additional account
For programmatic access (CI/CD, scripts), create static API tokens:
golem -C api-token list # List existing tokens
golem -C api-token new # Create a new token (default: expires 2100-01-01)
golem -C api-token new --expires-at 2025-12-31T00:00:00Z # Create with custom expiry
golem -C api-token delete <TOKEN_ID> # Delete a token
Use a static token in a profile for non-interactive environments:
golem profile new ci-cloud --url https://release.api.golem.cloud --static-token "<TOKEN_SECRET>" --set-active
In your golem.yaml, add a cloud environment:
environments:
local:
default: true
server: local
componentPresets: local
cloud:
server: cloud
componentPresets: cloud
Then deploy with:
golem -C deploy # Deploy to cloud using the cloud environment
Or explicitly:
golem -e cloud deploy # Deploy using the named "cloud" environment
-C and -L Shortcuts| Flag | Effect |
|---|---|
-C / --cloud | Use the cloud environment (or cloud profile if no manifest) |
-L / --local | Use the local environment (or local profile if no manifest) |
These shortcuts work with any command:
golem -C component list # List components on Golem Cloud
golem -C agent list # List agents on Golem Cloud
golem -L deploy # Deploy to local server
Golem Cloud also provides a web management console at console.golem.cloud for visual management of components, agents, and deployments.
# 1. Authenticate with Golem Cloud (opens browser for GitHub OAuth2)
golem -C account get
# 2. Deploy your application to the cloud
golem -C deploy
# 3. Interact with your cloud agents
golem -C agent list
golem-profiles-and-environments for detailed profile, environment, and preset configurationgolem-deploy for deployment commands and flags