Takes effect on the next question — no restart. Effort changes how much the model thinks rather than the price per token, so its cost effect varies; the model changes the rate directly. Switching model resets the prompt cache, so the first answer after a change costs a little more.

Every figure the assistant gives is computed by the same functions that draw these pages, so the two can never disagree. It will recommend actions your own data supports, but not specific investments — and anything consequential on tax is worth confirming with your accountant.

Plaid finds a recurring charge once it has seen enough of them, which is no help the day you set one up. Enter what you expect and the feed checks it: a charge that arrives for a different amount is flagged rather than quietly becoming the new normal.

Everything that moved through each account, and how much of it was actually spending. The two differ because moving money between your own accounts, and paying your own cards, is real money leaving an account without being money spent.

Plaid reports the money leaving your current account and the money arriving on the card as two unrelated transactions — nothing links them. Where the card is linked here, an exact amount within a few days identifies it and the row says matched. Where it is not, the issuer is read out of the payment description, which names who was paid but not which card: those say named. Worth knowing which is which.

Debts no bank feed reports — a servicer Plaid cannot reach is invisible, and invisible debt is counted as zero, which makes net worth wrong in the flattering direction. The balance is yours to keep current; payments are found in your transactions when you name the merchant that bills you.

An account decides where its charges go by default. These override that for one merchant, across every charge it has made and every one it makes next — which is the difference between marking a supplier once and marking it forever. Set them from the Books column on any transaction.

Kept as a way in if Google is unreachable or misconfigured. Setting one here stores a scrypt hash and stops APP_PASSWORD being read, which takes the plaintext out of .env.

A six-digit code from an authenticator app, on top of the password. A leaked or guessed password is then not enough on its own.

This session signed in with the app password during first-time setup, so there is no account to attach a second factor to yet. Add an address below, give it a password, then sign in with it.

Sign in with a fingerprint, face or device PIN instead of a password and a code. A passkey is tied to this exact site, so a copy of the sign-in page pretending to be it gets nothing — which is the one attack a password and a code cannot survive.

Every attempt to get in, successful or not. The most recent are kept; older ones fall off. A refusal you do not recognise, from an address you do not recognise, is the thing to look for.