# ChatGPT and Current AIs Are Dumb
**URL:** https://discuss.criticalfallibilism.com/t/chatgpt-and-current-ais-are-dumb/1753
**Category:** Unbounded
**Tags:** ai
**Created:** [March 31, 2023, 5:40pm UTC](https://discuss.criticalfallibilism.com/t/chatgpt-and-current-ais-are-dumb/1753 "2023-03-31T17:40:09Z")
**Posts on this page:** 1
**Showing post:** 60
### Author:  [@Elliot](https://discuss.criticalfallibilism.com/u/Elliot)
#### Post date: [April 5, 2026, 2:54am UTC](https://discuss.criticalfallibilism.com/t/chatgpt-and-current-ais-are-dumb/1753/60 "2026-04-05T02:54:41Z")
AI agents are really useful for software development now. I just had Codex fix a bug in Ghost (the open source project that the CF blog uses). It did it largely by itself just based on me saying what the bug is and giving a screenshot. It took a while, downloaded code, installed some tools, did some workarounds to get stuff running on my computer, did some testing that its changes worked, etc., in addition to figuring out the actual code changes to make. It also wrote the explanation of the changes and pushed it to github from my account for me.
>
>
> Summary
>
> This fixes a Markdown card display issue where multi-paragraph and nest…ed blockquotes lose their visual separation in read-only mode.
>
> The underlying markdown HTML is correct, but the shared prose styles currently reset blockquote paragraph margins too aggressively. That causes sibling paragraphs inside a blockquote to collapse together, and nested blockquotes can appear visually cramped.
>
> What changed
>
> The fix updates the shared blockquote spacing rules in \`packages/koenig-lexical/src/styles/components/kg-prose.css\` to style direct blockquote children instead of only \`blockquote p\`:
>
> \- \`blockquote \> \*\` now resets top and bottom margins
> \- \`blockquote \> \* + \*\` restores spacing between adjacent children
>
> This preserves separate paragraphs and nested blockquotes without changing markdown parsing or card serialization.
>
> Why the change is in shared prose styles
>
> Markdown card read-only rendering goes through the shared \`.kg-prose\` layer, so the problem is in the prose blockquote styles rather than in the Markdown renderer or card component itself.
>
> Testing
>
> I added a focused e2e regression in \`packages/koenig-lexical/test/e2e/cards/markdown-card.test.js\` that:
>
> \- loads a Markdown card containing multi-paragraph blockquotes
> \- includes nested blockquotes
> \- verifies the rendered HTML structure
> \- verifies that sibling blockquote children have non-zero spacing
> \- verifies that nested blockquotes still render with a left border
>
> I also ran the targeted e2e case locally.
>
> Risk / side effects
>
> This is a small CSS-only change plus a regression test.
>
> It does not change:
>
> \- Markdown parsing
> \- card editing behavior
> \- serialized editor state
> \- frontend theme rendering
>
> The only behavioral impact should be that blockquotes rendered through the shared prose layer preserve spacing between direct children more reliably, which is the expected result for multi-paragraph and nested quotes.
>
> Co-authored-by: Codex \
>
>
> \---
>
> \> \[!NOTE\]
> \> \*\*Low Risk\*\*
> \> Low risk CSS tweak in shared prose styles plus an e2e regression test; potential impact is limited to blockquote spacing across \`.kg-prose\` content.
> \>
> \> \*\*Overview\*\*
> \> Fixes Markdown card read-only rendering so multi-paragraph and nested blockquotes keep visible separation.
> \>
> \> Updates \`.kg-prose\` blockquote rules in \`kg-prose.css\` to reset margins for all direct blockquote children (\`blockquote \> \*\`) and reintroduce spacing between adjacent children (\`blockquote \> \* + \*\`). Adds a Playwright e2e regression asserting the expected HTML structure and non-zero spacing/border for nested quotes in \`markdown-card.test.js\`.
> \>
> \> \Reviewed by \[Cursor Bugbot\](https://cursor.com/bugbot) for commit b7d91a1f145117bb03dc10a8520412acf9f31653. Bugbot is set up for automated code reviews on this repo. Configure \[here\](https://www.cursor.com/dashboard/bugbot).\
I paid a bit of attention, reviewed its changes, and approved some commands. I’m not running it fully autonomously. There are security options like using a separate user account, separate computer, cloud server, git worktrees, etc. I think you can run it more autonomously than I did and still have reasonable security but I don’t know the full details.
Meanwhile on a different project I’m having Codex ssh into a staging server (not used by customers) and debug a high memory use issue. The server can be rebuilt if it breaks something, but it’s unlikely to break anything.
re Gemma 4, I didn’t try it yet but I heard it’s about as good as Claude Sonnet 4.6 which is decent and pretty usable though not the best.
For other types of productivity besides software development, I think AI is often more questionable but can be useful; it varies. And it can certainly be misused and get bad results for software.
---
_[View the full topic](https://discuss.criticalfallibilism.com/t/chatgpt-and-current-ais-are-dumb/1753)._