Slack: native streaming renders "•" as "-"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
Start by locating StreamingMarkdownRenderer and tracing how chat.startStream, appendStream, and stopStream pass markdown_text to Slack. Reproduce with Checking •• 1234, x • 6, and inline code to see which bullets Slack rewrites. Done when the streamed text preserves non-list bullets, or the Slack adapter documentation clearly describes the limitation.
Written by the indexing model from the issue text.
Description
Bug Description
When a reply streams through Slack's native streaming (chat.startStream / appendStream / stopStream with markdown_text), Slack renders every U+2022 BULLET as a hyphen, anywhere in the text: mid-line, and inside inline code. StreamingMarkdownRenderer passes the character through unchanged, so the rewrite happens in Slack.
That breaks text that uses the bullet as a character rather than a list marker, such as account masks that banking apps write as Checking •• 1234, which show as Checking -- 1234.
Steps to reproduce
- @chat-adapter/slack 4.44.0 with agentView: true, in a DM with the bot.
- Stream
Checking •• 1234\n(orx • 6, or`••`) with adapter.stream / thread.post. - Slack shows
Checking -- 1234.
Other dots render as written: · (U+00B7), ∙ (U+2219), ⋅ (U+22C5), ● (U+25CF), ⦁ (U+2981).
Expected
The text renders as written, or the Slack adapter docs note the limitation.
Possible fix
Slack's renderer owns this, so the adapter could swap a • that isn't a list marker for ⦁, which looks almost the same, before appending. We do that ourselves for now.
chat 4.44.0, @chat-adapter/slack 4.44.0, Slack web client.
– 🤖 Claude Opus 5.5
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 355
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 42
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vercel/chat
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
X and Twitch: paragraphs inside a block quote are joined with no spacePossibly taken @abhiramshaji-cyber claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
🛠️ dette technique
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
betagouv/mon-entreprise#4752 · 1 comment ·
Maintainers usually reply within 5 days
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
franciscoBSalgueiro/en-croissant#1111 ·
Maintainers usually reply within 2 days
-
area/providers type/feature version/v2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/opencode#64845 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day