The Console-Opener
Devtoolus curiosus
Appearance
Indistinguishable from a normal user at first glance, until the moment the keyboard shortcut is pressed. From that point on the skin mottles and darkens, and the eyes acquire focus.
Habitat
Landing pages of B2B SaaS products. Comparison pages. Documentation that mentions architecture. The Console-Opener has also been observed, less commonly, on the marketing site of their own employer.
Field notes
The Console-Opener is rarely a casual visitor. The naturalist treats every one as a person of interest as it might be a potential buyer evaluating the product stack. However, it could also be a spy marketer from a competing company. Only the most committed minority go on to file thoughtful bug reports about console errors they noticed.
Resolution
Highly variable. Enthusiastic visitors could become power users, but spy marketers only screenshot your bundle and leave. A few file a polite issue noting that an API key is being leaked in a client-side request.
Hazards observed
Console errors visible to the public. API keys logged in client-side network requests. A 401 returning from an endpoint you forgot was live.
If you spot one
Someone opening devtools on a marketing page is either evaluating you seriously or has found something you would rather they had not. Open your own landing page console and read it the way a stranger would, watching for leaked keys and 401s from endpoints you forgot were live. Devtools sit outside the page, so the recording never shows them opening. The session's raw events still reach the model, exceptions included. Run a Monitor scanner for sessions that threw a visible error and kept probing instead of leaving.