Handle it by not doing it. Schedule time to check each of these, according to priority. Start the day with whatever you want, knowing that these will be caught later.
True. But how do I know if it will be caught later anyways? I'd just end up getting distracted in the middle of my work, which is arguably even more distracting, right?
bash? :) iframes, a little dashboard, or nowadays you use something like mcp-browser-use, chrome-devtools-mcp with your llm of choice and write skills for that.
If it has APIs, you dont even need that browser-engine at all.
Handle it by not doing it. Schedule time to check each of these, according to priority. Start the day with whatever you want, knowing that these will be caught later.
True. But how do I know if it will be caught later anyways? I'd just end up getting distracted in the middle of my work, which is arguably even more distracting, right?
bash? :) iframes, a little dashboard, or nowadays you use something like mcp-browser-use, chrome-devtools-mcp with your llm of choice and write skills for that.
If it has APIs, you dont even need that browser-engine at all.
then you start the complete report with:
/morning
Yeah I haven't looked into dashboarding, as i always thought it took too long and was too limited. But i will try now thanks :)