You can enable multiple modes at the same time by comma separating their identifiers as value to

xdebug.mode: xdebug.mode=develop,debug,profile

The triggers for debug are
XDEBUG_SESSION_START
in GET / POST / ENV for debug

and
XDEBUG_TRIGGER
in GET/POST/ENV for profiling

Hi!

This is certainly possible.

Set xdebug.mode=develop,debug,profile

And then you can either use a browser extension as described in the documentation (https://xdebug.org/docs/step_debug#browser-extensions), or specifically trigger
step debugging with a GET/POST/ENV/COOKIE named "XDEBUG_SESSION", or
profiling with a GET/POST/ENV/COOKIE named "XDEBUG_PROFILE"
This is all described in the documentation at https://xdebug.org/docs/all_settings#start_with_request

I am creating a (short) video/animation of this at the moment as well, which will show up at my YouTube channel at https://www.youtube.com/playlist?list=PLg9Kjjye-m1g_eXpdaifUqLqALLqZqKd4

Please do note, that this is a bug tracker, and not a support forum. For support options, including (free) community support, please refer to https://xdebug.org/support

cheers,
Derick

I understand that if I start with xdebug.mode=develop,debug,profile, I will always be paying the performance penalty of debug, and see spurious "Debugging session finished without stopping on a breakpoint, check your path mappings yadda yadda yadda" notifications in my IDE. Is that correct? If so, is that avoidable?

I should have been more pedantic when asking the question. When I asked "develop by default", I should have emphasized: "develop (but not debug or profile) by default".

Allright, I had some difficulties figuring the right combination of settings to avoid always paying the debug performance penalty, but I will follow your video tutorial and report back.