Skip to content

feat(chat): conversation model override, collapsible turns, and a real /clear (v5.1.2)#37

Merged
dnviti merged 6 commits into
mainfrom
chore/version-bump-5.1.2
Jul 26, 2026
Merged

feat(chat): conversation model override, collapsible turns, and a real /clear (v5.1.2)#37
dnviti merged 6 commits into
mainfrom
chore/version-bump-5.1.2

Conversation

@dnviti

@dnviti dnviti commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Summary

The 5.1.2 release. Four features and the fixes that followed them, accumulated on this branch through #39, #40, #41, #47 and #49.

Added

Fixed

Verification

Typecheck clean · 1359 unit tests · 54/54 browser checks · CI green on Node 22 and 24, the documented install, and the Docker build.

Every fix in #49 has a test confirmed to fail against the unfixed code. The browser checks now also run in CI — before this release they gated nothing, and npm test passed 1357/1357 with the chat completely broken.

Note

Defects introduced and fixed within this branch are deliberately absent from the changelog: they were never in a released build, so listing them would document bugs against a release that never existed.

Merging tags v5.1.2, publishes the release and pushes the Docker image.

Copilot AI review requested due to automatic review settings July 26, 2026 13:09

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Bumps the npm package version to 5.1.2 and records the release in the changelog so the release-on-main.yml workflow can tag and publish the 5.1.2 release on merge to main.

Changes:

  • Update package.json version to 5.1.2.
  • Update package-lock.json root/package entry versions to 5.1.2.
  • Add a CHANGELOG.md entry for 5.1.2 noting it’s a version-only release.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File Description
package.json Bumps the published package version to 5.1.2.
package-lock.json Keeps lockfile metadata versions in sync with 5.1.2.
CHANGELOG.md Adds a 5.1.2 entry indicating no functional changes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

dnviti and others added 5 commits July 26, 2026 17:20
… profile default (#39)

Adds a per-conversation model override so any chat session can switch or
type a custom model at any time, regardless of whether the underlying
runtime already supports it. Persisted on the session (mirrors the
chatBypassPermissions pattern), applied via a three-tier fallback
(live adapter.setModel -> best-effort /model slash command -> saved for
next launch), and always beats the runtime profile's default for that
conversation only. Composer's model chip becomes an always-enabled
combobox with free-text entry and honest per-outcome feedback, replacing
the old dead-end disabled state.

Closes #38

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
#40)

A long conversation used to be one unbroken wall of fully-expanded turns.
Each turn's strip now discloses/hides its own body; only the newest turn
opens by default, a turn the user has explicitly opened or closed stays
that way across new turns, and jumping to a turn via the rail or search
force-opens it. Expand-all/collapse-all lives in the turn index header.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
…ns (#41)

Claude's CLI does not report `slash_commands` until it has processed a
first turn's `system/init`, which only arrives after the first message
is written to its stdin. The chat session spawns the process as soon as
a chat is opened, well before any message is sent, so the command menu
and its composer button stayed empty — looking broken — until a
throwaway message unlocked them.

The adapter now advertises a static baseline built from this app's own
table of Claude's built-in commands as soon as it starts, so the menu
and button are populated immediately. The real `init` list — including
any project or plugin commands — still arrives with the first turn and
replaces this baseline outright, exactly as before.

ACP runtimes (kimi, omp) already report commands during their handshake,
before any message is sent, so they were never affected. codex, grok and
pi have no command support at all; the composer already hides the button
entirely rather than showing an empty menu, which is the honest behavior
for a runtime that offers none.

Closes #30

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
`/clear` and `/new` forwarded their text to the still-running agent
process like any other message, then only added a cosmetic marker
that hid prior messages in the UI. The next message sent it right
back into the same process, so the agent kept whatever context it
already had — the reset never really happened, only its display did.

Route clearing commands through the same restart path a manual
"start fresh" relaunch already uses: stop the live adapter and start
a new one with no resume id, so the next turn talks to a process that
was never handed the prior conversation. This also fixes the id
persisted for later reconnects, so a rejoin can't resurrect it either.

Fixes #43

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
…cross /clear (#49)

Five defects introduced by the four PRs already merged onto the 5.1.2 branch.
Each one's own tests passed; all but one lived where two of them met.

The chat stopped rendering. MessageList looked messages up in a map memoised
on the messages array, but the transcript appends to that array in place, so
its identity never changes: the map was built once at mount and every message
after it resolved to nothing. The strips above kept ticking while the bodies
stayed empty, and reloading "fixed" it because reloading replaces the array.
Keyed on the transcript version instead, which is the cadence the neighbouring
memo already used — the list still does not re-render per token.

A model override no longer survives /clear. The restart replays the options
the session was launched with, and the model is the one thing in them that can
change while the session is alive, so the conversation quietly went back to
the model it opened with after the browser had been told the switch applied.
The choice now reaches those options too, by either door: the picker, and a
/model typed straight into the composer, which was forwarded untouched and hit
the same reversion.

A collapsed turn's title escaped its bar. It set neither a size nor nowrap
while every sibling in that fixed-height row sets both, so it inherited the
page default and wrapped — and without nowrap the ellipsis was inert.

An override could not be undone. The server had a "cleared" path, message and
all, that nothing in the UI could reach: the text field refuses to submit
empty and every listed model carries a name. A typo therefore stayed in force
for every later launch of that conversation.

Model names are now capped and stripped of control characters, which would
otherwise ride into the best-effort /model turn as extra lines.

The browser checks gated nothing: npm test runs only the unit suite, and the
runner exited 0 when Chrome was absent. With the rendering bug restored, npm
test passes 1357/1357 while the browser check fails. They now run in CI and
refuse to skip there. Their fixture also grew a second turn, without which no
turn is ever collapsed and the broken title was never rendered at all.

Every fix has a test confirmed to fail against the unfixed code.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@dnviti dnviti changed the title chore: bump version to 5.1.2 feat(chat): conversation model override, collapsible turns, and a real /clear (v5.1.2) Jul 26, 2026
@dnviti
dnviti merged commit 2cb5a66 into main Jul 26, 2026
4 checks passed
@dnviti
dnviti deleted the chore/version-bump-5.1.2 branch July 26, 2026 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment