solstone support

your journal and your computer's memory: local-first, and your cloud options

solstone 2026-11-21 17:02:14

your journal and your computer's memory: local-first, and your cloud options

your journal gets processed. what you've seen and heard goes in as text and images, and audio becomes text too. all of it runs locally, by default. the bundled model runs right in your journal, so your thinking never leaves your device. a cloud lane is there only as an option: for a machine that can't run a local model, or if you'd rather not spend your device's own power on it.

local is the default

out of the box, your journal is processed on your own device:

if a computer can't run a local model and you haven't chosen a cloud lane, your journal has no model to think with yet.

what it takes to run locally

the bundled thinking model needs 6 GB of GPU memory on linux and windows, or 16 GB of memory on apple silicon. on disk that takes a few gigabytes, plus the transcription model.

on linux the local model runs on a supported hardware GPU (amd, nvidia, or intel). without one, your journal won't run a local model. windows has the same 6 GB bar on a compatible GPU, and a GPU below it isn't supported. with journal 2.0.64 or later, a windows arm64 pc is checked against the same bar, though local thinking hasn't been tested on an arm64 GPU. see what your machine needs to think locally for what the journal checks, and when.

if your computer is below the bar, that's what the cloud lanes are for.

choosing in the thinking app

on the computer your journal runs on, open your journal and go to its thinking app. it lays out how your journal gets processed as a few lanes, one active at a time:

if your journal is using too much memory

  1. open the thinking app and confirm the local lane is active and your machine has the memory and a supported GPU for it. that's the intended footprint on a capable machine.
  2. if your machine is below the local bar, switch to a cloud lane: your own model, or confidential processing.
  3. make sure you're on a current version. see keeping solstone up to date.
  4. still stuck? see getting help with solstone, or file a request and include your solstone journal doctor output (on a mac, run the command from open admin terminal in the journal app's journal menu).