golem-local-dev-server

Name: golem-local-dev-server
Availability: InStock
Author: Soham

Start and troubleshoot the local Golem development server with subcommands and tracing flags.

Updated May 17, 2026

Search Tags:#debugging #agent runtime #durability #retry policy #golem #local dev server #tracing logs

Ready to run

npx skills add https://github.com/Rust-soham/golem-claw --skill golem-local-dev-server-rust-soham

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: golem-local-dev-server
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-local-dev-server
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-local-dev-server-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably start, configure, and debug a local Golem development server so you can reproduce and diagnose runtime behavior before deploying agents.

Core Features & Use Cases

Local server startup and networking: Runs golem server as a single local process bundling worker executor, component compilation, shard manager, registry, and router, with configurable router/custom request/MCP ports.
State management and repeatable testing: Supports cleaning all local server state and (for advanced debugging) using deterministic agent filesystem roots.
Deep observability for failures: Guides you to use -v verbosity levels and grep specific tracing targets and log patterns for durability, HTTP retry decisions, semantic trap retry policy resolution, and replay behavior.

Quick Start

Start the local server and capture detailed durability and retry logs by running golem -vvv server run in a terminal.

Frequently Asked Questions about golem-local-dev-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I start a local Golem server for debugging agent runtime issues?▼

To start a local Golem server for debugging, run `golem -vvv server run` in your terminal. This launches a single local process bundling the worker executor, component compilation, shard manager, registry, and router while capturing detailed durability and retry logs.

How can I diagnose durability and HTTP retry decisions during Golem development?▼

You can diagnose durability and HTTP retry decisions by running the local Golem server with `-v` verbosity levels. Use grep to filter specific tracing targets and log patterns that reveal semantic trap retry policy resolution and replay behavior during testing.

Can I clean persisted state from a local Golem development server for repeatable testing?▼

Yes, you can clean all persisted state from a local Golem development server to ensure repeatable testing. For advanced debugging scenarios, you can also configure deterministic agent filesystem roots to isolate runtime behavior across test runs.

Does the Golem local dev server support custom port configurations for routing and MCP requests?▼

Yes, the Golem local dev server supports custom port configurations. You can use optional configuration flags to specify router ports, custom request ports, and MCP ports, ensuring the local execution environment matches your networking requirements.

What is the best way to reproduce semantic trap retry policy behavior in a local Golem environment?▼

The best way to reproduce semantic trap retry policy behavior is to run the local Golem server with maximum verbosity. This enables detailed tracing logs that capture retry policy resolution, allowing you to analyze how the agent runtime handles failures.

Why are my Golem agent components failing to deploy during local server testing?▼

If Golem agent components are failing to deploy during local server testing, inspect the tracing logs generated by the `golem server` command. Ensure you are using the correct subcommands and verbosity-driven tracing targets to diagnose component compilation and deployment errors.