Option to include console output (stdout/stderr) in app mode when "show code" is enabled

[liquidcarbon]

Text written to stdout/stderr, including print statements and logs, shows up in a console output area below a cell.

By default, these console outputs don't appear when running a marimo notebook as an app. If you do want them to appear in apps, marimo provides utility functions for capturing console outputs and redirecting them to cell outputs.

Though this is available, it requires additional coding and figuring out where to place it.

When the app errors out, you do get to see some messages, though they tend to be not helpful:

An internal error occurred
An internal error occurred: 0f6c9bc0-e287-42a0-acac-f06803d43035

If you run the app through gunicorn and capture logs, you can find what happened, but this takes a fair amount of digging and filtering out normal Marimo messages:

AttributeError: 'DataFrame' object has no attribute 'iid'
[E 250423 16:20:24 ops:299] (error_id=4c76882f-858a-457e-86c0-a7188cbd211e) 'DataFrame' object has no attribute 'iid'
[E 250423 16:20:24 ops:299] (error_id=7c672cbc-0fe2-42c8-a8aa-6badd74a4646) An ancestor raised an exception (AttributeError):
[E 250423 16:20:24 ops:299] (error_id=0f6c9bc0-e287-42a0-acac-f06803d43035) An ancestor raised an exception (AttributeError):

Having this in the app would be really helpful for troubleshooting - unfold the code and see the logs and complete error messages appear and change in response to interacting with UI elements.

[mscolnick]

We already support this with --redirect-console-to-browser: marimo run nb.py --redirect-console-to-browser

[liquidcarbon]

Nice! How do you do it in mounted apps?

[mscolnick]

create_asgi_app doesn't take in a param for it, but should be fairly easy to wire down if you are up for the PR?