5 sessions on marked with a coding agent: the agent failed at least once in 0, and 1 finished without a human stepping in.
Takeaway: Next time I'd start the first prompt by asking for a full audit of what each bundling layer (parser, languages, themes) actually pulls in, instead of chasing library swaps first.
Takeaway: Next time I'd ask upfront for the revert plus a rebuild/lint check in one go, since resolving the three-way conflicts in package.json, the lockfile and the component took most of the turns.
Takeaway: I'd start by asking for the investigation and the two features (row dividers, longest-word minimum width) together, since that's basically what I ended up doing anyway.
Takeaway: I'd start by asking directly whether this is standard Markdown behavior before diving into a code investigation, since it turned out to be expected CommonMark semantics all along.
Takeaway: Next time I'd start the prompt by pointing straight at markdown-block's KaTeX inline math extension instead of letting the agent rediscover it through a long grep trail — that diagnosis phase took way longer than the actual fix.