golem-local-dev-server

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.

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.

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.

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.

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.

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.