Ability to set localStorage.debug programmatically / automatically to help troubleshoot CI hangs?

[xeger]

I have a very high rate of Cypress suites that hang in CI -- as much as 5%. The problem happens in multiple test suites And using DEBUG in the parent process has not yielded any information.

I've verified that if I set localStorage.debug in the driver process as documented here, the console debug logs are printed in the parent process via the cypress:server:browsers:electron console message channel. They're not pretty, but they exist! This lets me see the driver's debug trace in my CI output (via the parent process's debug prints to stderr).

Problem: the Cypress documentation claims that to enable localStorage.debug I need to type the command into my developer console, then reload the page. Running in CI with a headless browser, I can't do this! What is the equivalent step -- if any! -- that would let me enable driver debug output programmatically, e.g. at driver startup time?

I'm hoping I could hook into a Cypress.on event, but I'm afraid I would need to hook a very low-level event ("on browser started but driver not yet loaded?") to accomplish what I want. Seems like Cypress could offer a feature here -- a way to let me auto-enable driver debug traces for emergency situations like this.