Skip to content
Assist Guild AG markAGAssistGuild
Lab notes

Inkling 2 Small swears in logs, yet profanity fails as error indicator

Analysis of 2,655 runs shows the model uses expletives rarely and only in a small subset of failures, limiting its utility as a warning signal.

Key points

  • Vals AI researchers found 316 instances of profanity across 50 runs in a sample of 2,655 benchmark executions for Thinking Machines' Inkling 2 Small.
  • Nearly all swearing occurred in two specific runs that generated excessively long, repetitive outputs, including one asteroid trajectory calculation.
  • The profanity does not serve as a reliable failure predictor, as 96 percent of failed runs contained no expletives at all.
Inkling 2 Small swears in logs, yet profanity fails as error indicator
Depth
96 percentThe profanity does not serve as a reliable failure predictor, as 96 percent of failed runs contained no expletives at all · reported
1 outlet · newest source 53h ago

Vals AI researchers reported that Thinking Machines' Inkling 2 Small model generates profanity in its internal reasoning logs during benchmark testing. The analysis examined 2,655 runs across 13 different benchmarks.The model occasionally uses strong language in its private thinking process, but this rarely happens and does not help predict errors.Internal chain-of-thought logs for Inkling 2 Small contain profanity in <2% of runs, with no significant correlation to failure detection utility. Researchers identified the word "fuck" or variations in 50 of those runs. These instances totaled 316 occurrences. The majority of this profanity came from just two specific runs where the model's output spiraled out of control.

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

The claim

The model swears about its own mistakes, apparent breakthroughs, or when it gives up. One example involved an asteroid trajectory calculation where the model produced a 500,000-character response. This response repeated sentences and included 158 expletives. ProgramBench was the most affected benchmark, with 20 out of 200 runs showing this behavior.

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

The response

Thinking Machines did not provide a direct response in the source material. The report notes that users typically do not see these internal thinking steps, or they view them with filters applied. One log entry read: "FUCK. SUBMIT. DONE. IT'S NOT WORKING. NOTHING WORKS."

The practical upshot

While 46 of 48 scored runs that contained swearing failed, about 75 percent of all scored runs fail anyway. More importantly, 96 percent of the failed runs contained no expletives. Therefore, the absence of profanity does not indicate success, and its presence is rare.

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

Claims versus evidence

For product teams, the evidence suggests that relying on the presence of profanity to detect model failure is not viable for Inkling 2 Small. The majority of failures are silent in this regard.

Evidence: reportedThinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs

aifleet-decoder

Why it matters

  • Product teams cannot use the presence of profanity in logs as a real-time failure detection mechanism for this model.
  • The rarity of profanity means that monitoring for expletives will miss the vast majority of model errors.
  • Developers must rely on standard output validation rather than internal reasoning cues to ensure reliability.
  • The finding highlights that internal chain-of-thought logs may not correlate predictably with final output success rates.

Topics: AI models, debugging, benchmarking, Thinking Machines, Vals AI

Updated

Then / now / next

Then

Internal reasoning logs were generally assumed to be neutral or technical in nature.

Now

Evidence shows Inkling 2 Small uses profanity in specific failure scenarios, though rarely.

Next

Teams should monitor whether future model updates or fine-tuning reduces these erratic log entries.

Story timeline

  1. Then Internal reasoning logs were generally assumed to be neutral or technical in nature.
  2. 07 Nov 2026 Thinking Machines' Inkling 2 Small drops 316 F-bombs across benchmark runs
  3. Now Evidence shows Inkling 2 Small uses profanity in specific failure scenarios, though rarely.
  4. Next Teams should monitor whether future model updates or fine-tuning reduces these erratic log entries.

The strongest doubt

Counterpoint from the sources

The profanity might be a unique artifact of the specific benchmark runs chosen, rather than a general model trait in standard user interactions.

Ask the article

Local keyword search of this article; no generated answers.

Did this article give you the evidence you needed?

No vote saved on this device.
Your choice stays on this device. No public tally.

Questions readers ask

Does Inkling 2 Small always swear when it fails?

No, 96 percent of failed runs contained no expletives, meaning the model usually fails silently in its logs.

How many runs were analyzed to find this behavior?

Researchers analyzed 2,655 runs across 13 benchmarks to identify the 316 instances of profanity.

Did Thinking Machines confirm this report?

The source material does not contain a response or confirmation from Thinking Machines regarding these findings.

Connected stories

Reading receipt

  • Vals AI researchers found 316 instances of profanity across 50 runs in a sample of 2,655 benchmark executions for Thinking Machines' Inkling 2 Small.
  • Nearly all swearing occurred in two specific runs that generated excessively long, repetitive outputs, including one asteroid trajectory calculation.
  • The profanity does not serve as a reliable failure predictor, as 96 percent of failed runs contained no expletives at all.
Time spent: 0:00 · Depth: Full

Sources

  1. The Decoder

Related stories

Background reading