golem-add-config-ts

To add typed configuration to a TypeScript Golem agent, define a plain TypeScript type literal describing your config shape and bind it using a Config<T> constructor parameter in the @agent() decorator so the framework detects and loads it automatically.

Config precedence follows a cascade where narrower scopes override broader ones: componentTemplates override components, which override agents, which override presets, ensuring per-call RPC overrides and CLI --config flags take priority over golem.yaml defaults.

Yes, you can pass configuration overrides during agent-to-agent RPC by using methods like getWithConfig, allowing per-call settings to take precedence over values defined in golem.yaml or supplied via CLI --config flags.

You access typed configuration values inside a Golem agent by using the config.value syntax on your injected Config<T> parameter, ensuring settings supplied via golem.yaml or CLI flags are safely read as strongly typed data.

No, Golem typed config requires using plain TypeScript type literals to define the config shape rather than interfaces or classes, ensuring the framework can properly detect and bind the configuration through Config<T>.

Supplying settings via golem.yaml and CLI flags provides strongly typed, structured configuration management for Golem agents, replacing unstructured parameters with a safe config precedence cascade and validation through TypeScript type literals.