Skip to content

docs: Fix typos in "I Have No Mouth, and I Must Scream" blog post #226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
promptless merged 1 commit into from
Jan 27, 2026
Merged

docs: Fix typos in "I Have No Mouth, and I Must Scream" blog post #226

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions fern/docs/technical/i-must-scream.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Our customers often configure Promptless themselves, and sometimes they'll make
<img src="https://promptless-customer-doc-assets.s3.amazonaws.com/docs-images/org_2lvkgU9erOFxYhtEVVC0ymPrPdF/i-must-scream-customer-config-daa58a33.png" alt="Agent escalation about missing Slack notification channel" />
</Frame>

This often helps us deliver a delightful customer experience—allowing us to provide a white-glove support process with Promptless's proactive help. Promptless In this case we were able to intervene with them to fix their set up before they realized anything was wrong.
This often helps us deliver a delightful customer experience—allowing us to provide a white-glove support process with Promptless's proactive help. In this case we were able to intervene with them to fix their set up before they realized anything was wrong.

### It found bugs with its tools

Expand All @@ -72,7 +72,7 @@ This one was particularly insidious—git was returning success exit codes while

### It helped us get ahead of customer frustration

Sometimes the will escalate to us something when it's clear that it screwed up earlier. In this case, a customer asked in Slack why their PR had unexpected files. Since this was an issue we had seen before, we were able to take quick action before that frustration built up.
Sometimes the agent will escalate to us something when it's clear that it screwed up earlier. In this case, a customer asked in Slack why their PR had unexpected files. Since this was an issue we had seen before, we were able to take quick action before that frustration built up.

<Frame caption="Agent escalating about duplicate files in a customer PR">
<img src="https://promptless-customer-doc-assets.s3.amazonaws.com/docs-images/org_2lvkgU9erOFxYhtEVVC0ymPrPdF/i-must-scream-customer-frustration-f1ae26f6.png" alt="Agent escalation about duplicate files in customer PR" />
Expand All @@ -90,7 +90,7 @@ This was the result of a software bug that we were able to easily fix, but our t

### Bonus: It caught a critical bugs in our code

This one we didn't expect. Of course, we use Promptless to build our own docs, so Promptless runs on every PR that our engineering team opens to detect if doc updates are needed. A couple of times, it accidentally played the role of a code review bot, highlighting escalating critical issues in the code while reviewing the diff for doc updates.
This one we didn't expect. Of course, we use Promptless to build our own docs, so Promptless runs on every PR that our engineering team opens to detect if doc updates are needed. A couple of times, it accidentally played the role of a code review bot, escalating critical issues in the code while reviewing the diff for doc updates.

<Frame caption="Agent escalating a critical bug it found while reviewing code">
<img src="https://promptless-customer-doc-assets.s3.amazonaws.com/docs-images/org_2lvkgU9erOFxYhtEVVC0ymPrPdF/i-must-scream-critical-bug-53ad5da5.png" alt="Agent escalation about critical bug with inverted logic" />
Expand Down