0.3.6

• Chinese and Japanese stretches grow a character at a time around their short form, and Thai a
  word at a time, instead of going blank and then appearing whole. The words you already read stay
  where they are.

0.3.5

• Tool calls are drawn by Claude Code itself again: a click on a finished group's one-line summary
  opens it, and a terminal that draws no links no longer prints ▸ show (https://cc-stretch.invalid/)
  (#1). The plugin's own ▸ show fold is gone.
  Contributed by @ppikkuaho in #10.
• Chinese and Japanese replies wrap between characters, so a row no longer ends half empty, and
  punctuation such as ， or 。 or a Japanese small kana never starts a row. Korean wraps at spaces and
  Thai between words; Thai vowel and tone marks no longer take a cell of their own.
• While a reply streams, a stretch after a code span that runs over a line break shows as its short
  form instead of its raw markup (#6).
• A line such as "```python …" inside a code block no longer ends the block
  (#7).
• Emoji such as 🚀 count as two cells, so a click after one lands on the phrase under it
  (#8).
• npm run bench:report runs on a fresh clone without writing over the published numbers
  (#9).

#6 to #9 were reported by @rahul05ranjan.

0.3.4

• In fullscreen on Claude Code 2.1.300, a new reply's stretches are underlined and open on a click
  again. That version hands the plugin a finished reply with its long forms already hidden, so the
  short forms showed as plain text; a session resumed with --continue was not affected
  (#3). Contributed by @danielhernik in
  #5.

0.3.3

• The guide sent to Claude is back to its 0.3.1 text. The line 0.3.2 added, asking that a short form
  never be a label such as "What changed.", did not reduce such labels when 11 real replies were
  rewritten under both guides, and it made the shortest reading slightly longer.

0.3.2

• Claude is told that each short form must say something itself, the gist of its long form. A label
  for the long form, such as "Details." or "What changed.", is not a short form.
• The README gathers where clicks don't work, and why, under Limits.

0.3.1

• On Claude Code's main screen, where a printed reply cannot change and so every stretch shows open,
  the first such reply now says why in a dim line, and how to get clickable stretches: /tui fullscreen, or starting Claude Code with CLAUDE_CODE_NO_FLICKER=1 in setups that start on the
  main screen anyway (#3).
• The README names those setups.

0.3.0

• In the terminal, the words a stretch adds are drawn in a colour of their own, a different one for
  each stretch you open. The one you opened last is brightest; the others fade a little, and all of
  them fade once you write your next prompt. Each « keeps its stretch's bright colour.
• Closed stretches are underlined in the text's own colour, no longer blue, so colour marks only what
  you opened.
• A « after a rule or a code block goes on a line of its own, in the terminal and in the desktop
  app. Before, it turned the rule into plain dashes or left the code block unclosed.

0.2.0

• Clickable stretches in the Claude desktop app: each stretch is a link that opens in place, and «
  closes it. Contributed by @LGuillermoAngaritaG in
  #2.
• Desktop links also work when a short form holds brackets, code, a link or hundreds of characters.
• The markup stays hidden while a reply streams even with a phone or VS Code attached. Only a session
  with the desktop app attached shows it.
• In the terminal, a short form written over several lines is drawn open. Before, drawing its
  paragraph ran past Claude Code's time limit.
• The note that tells Claude what you opened no longer lists a short form written over several lines
  as unopened. When nothing was clicked, it no longer implies the desktop app drew every stretch open.
• A bug report template asks for the Claude Code version, where you run it, and what you see.