ContextMove 4.6.0

ContextMove 4.6.0

The browser extension is on the Chrome Web Store, and it now shows how much of
your plan is left without you leaving the chat. ContextMove also has a dark
theme, and captures on Claude, ChatGPT and Grok save the whole thread rather
than what happened to be on screen.

How much you have left, under the composer

Knowing you are near a limit is only useful before you start the long piece of
work, not after the site cuts you off in the middle of it. Until now the only
way to find out was to leave the conversation, open the provider's usage screen
and come back.

There is now a line under the chat composer with your weekly and session
figures, each with the time until it resets:

usage    WK  44%  resets in 3d 13h    SESSION  5%  resets in 4h 46m

The numbers are the site's own. ContextMove reads the figure out of the usage
response the provider already sends its own meter — it does not query any
account API, count tokens, or estimate. Where a provider reports nothing, the
line stays away rather than guessing.

Claude only fetches that figure when you open its usage page, so a reading
taken once would be correct the moment you looked and quietly wrong for the
rest of the day. ContextMove notices which address produced a real reading,
remembers it, and asks that same address again every few minutes. Nothing is
hardcoded, so the day the provider renames the endpoint the next reading
teaches it the new one.

The reading is shared across your tabs and survives moving between chats, which
is what makes it useful in the place you actually look at it — the empty
composer of a conversation you are about to start. A figure that is too old to
trust is dropped rather than shown.

The readout has its own switch on the Buzzer page in the app, separate from the
alarm: "tell me when I am nearly out" and "show me where I am" are different
questions, and the second one draws on someone else's page, which ought to be
refusable. Turning the readout off leaves the alarm working.

The buzzer settings moved into the app

Everything about the usage alarm — whether it fires, the threshold, the volume,
the notification, and now the readout — is set on the Buzzer page in
ContextMove, next to the sound it plays. It used to be split: the sound was
chosen in one product and everything governing it in the extension's own
options dialog, which is somewhere most people never opened.

A change made in the app reaches every open tab without a reload, and a browser
running while the app is closed still buzzes the way you set it up.

The alarm also sounds three times instead of once. One buzz is easy to miss
with music playing or the tab in the background.

Stars you can see

The per-message star marks which parts of a thread carry over when you hand the
conversation to another model. It was drawn as a text character and kept at
zero opacity until hover, so on most threads there was no sign it existed —
and on Claude the star injector and the capture code disagreed about where a
message began, which put stars on the wrong things.

The star is now drawn as a real shape, sits visible at rest, and both halves
resolve a turn the same way, so a star appears once per message and marks the
text that is actually carried.

The extension installs in one click

Until now, adding the extension meant opening chrome://extensions, turning on
developer mode, clicking Load unpacked, and pointing Chrome at a folder
inside the install directory. Four steps, one of them a setting most people are
right to be wary of — and the result broke if that folder ever moved, because
Chrome keeps loading it from the path you picked.

ContextMove Exporter is now published:

https://chromewebstore.google.com/detail/goenplhbbljlodllpclonganogjajppe

Setup opens that page for you at the end of the install. Click Add to
Chrome and you are done. Chrome updates the extension on its own from then
on, so the fixes in this release — and every one after it — arrive without you
reinstalling anything.

If you added the extension the old way, remove the unpacked copy from
chrome://extensions and add it from the store instead. Running both at once
puts two panels on every page.

A dark theme

Settings carries a Light / Dark control, and with neither chosen ContextMove
follows your operating system and keeps following it — change the OS at dusk
and the app changes with it, without a restart.

The theme is stamped before the first paint, so opening the app in dark mode no
longer flashes a white window first.

Captures keep the whole conversation

On Claude and ChatGPT, ContextMove now reads the conversation the site itself
holds rather than scraping what is rendered. A long thread is saved in full,
even the part scrolled out of view, and a message you edited and re-sent is
saved once — as the version that is actually in the thread, not interleaved
with every abandoned attempt.

Grok threads are captured properly for the first time.

Where a site gives up two versions of a transcript, ContextMove compares them
and keeps the more complete one. On Gemini, icon glyphs and per-message button
labels no longer end up mixed into the prose.

This part lives in the extension, so it is already in place if you have it
installed — Chrome updated it for you.

The bin selects the way the Library does

Selection in the bin used to be always on: an ordinary click silently ticked a
checkbox you had not asked for, and Restore and Delete forever sat greyed in
the toolbar waiting for a selection you had no reason to be making.

Multi-select is now an explicit mode, the same one the Library already had. Off
by default, each card carries its own Restore and Delete forever — which covers
the common case of coming to the bin for one item. Turn Select on and the whole
card becomes the checkbox, and the actions move to a floating pill with a live
count and Select all.

Emptying the bin with select mode on no longer strands that pill over an empty
view reading "0 selected".

Fixes

• The Library no longer leaves skeleton placeholder cards on screen when a
  filter returns nothing.
• The licence screen, and the publisher, support and update links Windows shows
  under Apps & features, point at contextmove.com — where downloads and release
  notes actually live — instead of a code repository.
• Double-clicking a .cvpack file someone shared with you opens it. Stray
  bytes had corrupted the Windows registry paths for that file type, so the
  association pointed at a directory that does not exist — in every build
  shipped so far.
• The app calls itself Context Move everywhere the operating system shows
  it: Windows shortcuts, the Start Menu group, the setup wizard, Add/Remove
  Programs, and on macOS the bundle name, the .dmg volume and the Finder
  description of a .cvpack. Upgrading removes the old desktop shortcut and
  Start Menu folder rather than leaving you with two of each.
• The macOS build no longer fails to start on a missing python-multipart,
  and the bundle keeps the right name.
• The Library lists what you touched most recently, rather than ordering by
  when a context was first created, and the dashboard's last-saved time is
  correct.

Upgrading

Your vault, settings and sign-in carry across untouched. The one manual step is
the extension: add it from the store, and remove the unpacked copy if you have
one. The usage readout arrives with extension 2.3, which Chrome installs on its
own.