Slack: native streaming renders "•" as "-"

Open
#1,184 0 comments 0 reactions 0 assignees View on GitHub

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
  1. @chat-adapter/slack 4.44.0 with agentView: true, in a DM with the bot.
  2. Stream Checking •• 1234\n (or x • 6, or `••`) with adapter.stream / thread.post.
  3. 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/chat

All issues in vercel/chat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.