Follow Discord
Sweep 03 Oct 2026 · 20:28Z Build v2.1.289 510 read Stable v2.1.285 Latest v2.1.289 Next v2.1.289 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.289 ·

Invalid Box borderStyle values are now checked and drawn with no border

Plugin UI boxes with an unknown borderStyle now get a diagnostic and no border, and diff highlighting stops retrying after an error

Group of 3 You'll notice Improvements
JSON All of v2.1.289
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Terminal UIArea: what it touches
ImprovementsKind: in v2.1.289,
ImprovementsSection of the release

What

Plugins can draw boxes on screen and give them a borderStyle. Claude Code now checks that style.

  • Validation: plugin UI trees are checked for an invalid Box borderStyle. A bad style is removed and a diagnostic message is shown, and the box is drawn with no border.
  • Known styles only: the border renderer now accepts only known style names, and a style must supply all eight corner and edge pieces. Before, any style that was set counted as a one-cell border, and an unknown name fell back to a default.
  • Validator order: some props now skip the standard per-prop check, while the borderStyle accounting still applies.
  • Syntax highlighting: when highlighting code in a diff (a view of what changed in a file) throws an error, the language is cleared so it does not keep retrying.

Why

A mistyped border style or a highlighting error should no longer break how things are drawn. Plugin authors get a clear message instead of a broken border.

See this entry in the whole of v2.1.289 →

Feedback