القائمة
Deploying a Golem application. Use when asked to deploy agents to a Golem server, update running agents, or troubleshoot deployment issues.
التثبيت باستخدام 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.
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.
| name | golem-deploy |
| description | Deploying a Golem application. Use when asked to deploy agents to a Golem server, update running agents, or troubleshoot deployment issues. |
golem deployBoth golem and golem-cli can be used — all commands below work with either binary.
golem deploy --yes
Run this from the application root directory (where the root golem.yaml is located). It automatically builds all components (with up-to-date checks), uploads them to the configured Golem server, and creates or updates the deployment. Always pass --yes to avoid interactive prompts.
golem deploy Doesgolem build).Existing running agents are not affected by default — they continue running with their previous component version. Use --update-agents or --redeploy-agents to change this behavior.
| Option | Description |
|---|---|
--plan | Only plan deployment, apply no changes |
--force-build | Skip modification-time based up-to-date checks |
-u, --update-agents <MODE> | Update existing agents: automatic or manual |
--redeploy-agents | Delete and recreate existing agents |
-r, --reset | Delete agents and the environment, then deploy from scratch |
-P, --preset <PRESET> | Select custom component presets |
-Y, --yes | Non-interactive mode — always use this flag |
| Option | Description |
|---|---|
-E, --environment <NAME> | Select a Golem environment by name |
-L, --local | Use local environment or profile |
-C, --cloud | Use cloud environment or profile |
--profile <PROFILE> | Select a Golem profile by name |
golem deploy --yes
Builds, uploads, and activates all components. Agents are created on first invocation.
golem deploy --yes --reset
Deletes all previously created agents and redeploys everything. Use this when iterating on code changes — without it, existing agent instances keep running with the old component version.
golem deploy --yes --update-agents automatic
Updates existing agents to the new component version automatically. Agents pick up the new code on their next invocation.
golem deploy --yes --plan
Shows what would be deployed without making any changes.
golem deploy runs the build automatically.