Probably an obvious one, but when the setup fails for whatever, reason, we get the “Connect interactive terminal” button appearing in front of the interactive terminal and this means:
Without changing the interface at all, if you could add a button to “view logs” in a new tab or something like this, it would be extremely helpful when debugging deploy issues.
I fully support this.
To begin with, simply allowing us to copy and paste logs from the test terminal would already be very helpful—especially after a failure occurs. Right now, when tests fail, the text becomes inaccessible due to the error message overlay.
Additionally, enabling file access for logs captured during program execution within the sandbox would greatly improve debugging. I’ve frequently encountered truncated error messages displayed as partial log chunks in the agent’s log view. Direct file access would significantly simplify troubleshooting in these scenarios.
FYI one workaround for me is to run these iterative “tests” for setting up the environment locally… I’ve even written a simple script to quickly spin up a new local Codex VM so I can run the tests locally without the timeout and with easy selection of log output.