ContextMove 4.6.1

ContextMove 4.6.1

Signing in on a new computer now brings your vault with it, the app backs
itself up daily without being asked, and the star button on chat pages is
legible again on both light and dark sites.

Moving to a new computer

Everything needed to carry a vault across already existed in Settings —
export, backups, restore — but nothing offered it. Reinstalling on a new
laptop opened an empty app, and finding the panel required knowing a backup
was the thing to look for.

Now an empty vault plus a signed-in account gets the offer directly: bring
the newest backup across, or start fresh. Both are real choices and both look
like it.

Google asks for Drive access once at that point. Sign-in and Drive go through
two separate Google clients, so the consent is genuinely a second grant rather
than a repeated one — but the account you just signed in with is pre-selected,
so a browser holding several accounts cannot quietly point you at an empty
Drive folder.

Restores stay additive. Nothing local is deleted, entries are matched by id
rather than appended blindly, and a vault whose contents are only in the
Recycle Bin still counts as used — so a restore never lands on top of work in
progress.

Backups take themselves

Once a day, pruned to the last ten. Whether one is due is read from Drive
rather than from a local timestamp, which matters in exactly the case this
release is about: a freshly restored machine has no local history, would
believe it had never backed up, and would immediately re-upload what it had
just finished downloading.

The first-run tour stops covering the question

Signing in could start the tour and raise the "moving from another computer?"
card at the same moment. The tour drew on top — over the one question someone
arriving on a new laptop actually has to answer. It now waits for that
decision the same way it already waits for sign-in.

Onboarding no longer asks for your name

Google hands the display name over with the identity, so the first question in
the tour was a form field whose answer the app already had. It greets you
instead, and still offers the box if you would rather be called something
else. A name set in Settings always wins.

The star button is readable on both themes

The star that saves a chat from the page sits directly on the site's own
background, and it was too faint to see on a light one and a white plate stuck
to a message on a dark one. Measured rather than eyeballed, the resting glyph
came out at 2.58:1 on a white page — below the contrast a control needs — and
the dark treatment was simply the wrong shape of control.

The extension now reads the theme of the page it is on and treats each case on
its own terms: an opaque chip on light, glass on dark, with the coral lifting
toward salmon so it survives a black background. Starred against unstarred was
already unambiguous and is unchanged.

This ships in extension 2.4.

Images ChatGPT stopped labelling

When a ChatGPT reply is a generated image, the site puts the picture in a turn
it does not tag as a message. Capture searched only inside tagged messages, so
those images were silently absent — no file saved and nothing reported
missing, which looked exactly like a chat that never had pictures. The
transcript was never affected; it comes from the network rather than the page.

Attachment search now covers the site's own turn containers as well, so a turn
the message markup cannot resolve is still searched.

Everything else

Capture, storage, search and the vault format are unchanged from 4.6.0.
Updating keeps everything where it is.