The thinking line does not show that it is still thinking #373

New issue

Closed

opened 2026-08-13 11:19:16 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-13 11:19:16 +00:00

Member

Slice of #370, which gave the exact target:

```

🤔 thinking...
```

What is in the way

Two things, and only one of them is cosmetic.

The ellipsis is free. The notice alphabet already admits ., though the sanitizer trims a trailing one, so it has to be appended after sanitizing rather than passed through it.

The icon is not free. noticeShape is ^> \[a-z0-9][a-z0-9 ,./-]*`$` and an emoji fails it. That shape is the thing that lets a member tell a harness line from model output, so widening it is a real change and not a formatting tweak.

The widening is deliberately narrow: only a non-ASCII run may lead the line. Model prose is ASCII, so > Sure! \thinking...`` still fails the shape. A test holds that.

In scope

An icon may lead a stage notice, and an ellipsis follows the phrase.
The thinking stage gets the icon from the issue.
The body is still sanitized. An icon decorates the line and licenses nothing inside the phrase.
An unlisted stage renders plain, so nothing needs an icon to work.

Out of scope, and it is a question rather than an omission

Icons for the other three stages: reading recent messages, calling a tool, checking the reply. Kai specified one icon and I am not choosing member-facing content. They render plain until someone picks them, which is a one-line change each.

Acceptance

The thinking line renders exactly the string in the issue.
Every stage still matches the notice shape.
ASCII cannot lead a notice.
A phrase containing mentions or punctuation is still sanitized inside the backticks.

**Slice of** https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/370, which gave the exact target: \`\`\` > 🤔 `thinking...` \`\`\` ## What is in the way Two things, and only one of them is cosmetic. The ellipsis is free. The notice alphabet already admits `.`, though the sanitizer trims a trailing one, so it has to be appended after sanitizing rather than passed through it. **The icon is not free.** `noticeShape` is `^> \`[a-z0-9][a-z0-9 ,./-]*\`$` and an emoji fails it. That shape is the thing that lets a member tell a harness line from model output, so widening it is a real change and not a formatting tweak. The widening is deliberately narrow: **only a non-ASCII run may lead the line.** Model prose is ASCII, so `> Sure! \`thinking...\`` still fails the shape. A test holds that. ## In scope - An icon may lead a stage notice, and an ellipsis follows the phrase. - The thinking stage gets the icon from the issue. - The body is still sanitized. An icon decorates the line and licenses nothing inside the phrase. - An unlisted stage renders plain, so nothing needs an icon to work. ## Out of scope, and it is a question rather than an omission Icons for the other three stages: reading recent messages, calling a tool, checking the reply. Kai specified one icon and I am not choosing member-facing content. They render plain until someone picks them, which is a one-line change each. ## Acceptance - The thinking line renders exactly the string in the issue. - Every stage still matches the notice shape. - ASCII cannot lead a notice. - A phrase containing mentions or punctuation is still sanitized inside the backticks.

coilyco-ops referenced this issue from a commit

2026-08-13 11:19:47 +00:00

feat(progress): the thinking line now shows that it is still thinking

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-13 11:19:47 +00:00

feat(progress): the thinking line now shows that it is still thinking #374

coilyco-ops referenced this issue

2026-08-13 11:20:11 +00:00

thinking message could be more interesting #370

coilyco-ops closed this issue

2026-08-13 11:25:52 +00:00

coilyco-ops referenced this issue