golem-logging-ts

You can view console output from a TypeScript Golem agent by using standard console methods like log, info, warn, and error in your code, then running `golem agent stream` or `golem agent invoke` to see the captured stdout and stderr logs.

To debug a TypeScript agent on Golem, use standard console API methods such as console.debug for execution details or console.error for failures, and Golem will automatically capture the stdout and stderr to stream the logs for troubleshooting.

Yes, Golem automatically captures both stderr and stdout generated by the standard console API in TypeScript agents, routing the output directly into the golem agent stream and golem agent invoke pipelines without requiring extra setup.

The best way to structure logs for a Golem TypeScript agent is to emit JSON strings or context-rich messages via console methods, which makes the captured stdout and stderr output significantly easier to search and interpret during monitoring.

Yes, you can use console.trace to emit optional stack traces within your TypeScript agent code, and Golem will capture this stderr output to help you diagnose execution failures and monitor behavior.

If your TypeScript agent logs are not showing up in golem agent stream, ensure you are using the global console API for output, as Golem specifically captures standard console stdout and stderr to emit logs to the stream.