Net worth
Pick a day on the chart to open its balance sheet.
Once the app has your balances and transactions, your net worth and spending show here.
J K move · Enter open · X select · 1–9 category · Esc close
Pick a day on the chart to open its balance sheet.
Shown everywhere in place of the bank's name. Leave blank to use the bank's name.
Decides where it appears on the balance sheet.
Turn on more than one for a joint account, or none.
For money you track but don't own. The account stays listed with its balance, but no total includes it, on any date. Syncing is not affected.
Each value counts from its date until the next one.
Last synced: —
Same account showing up twice? Merge this copy into the other one.
Remove this account with all its balance history and transactions.
Added on —
Everyone here signs in with their own Google account and sees the same accounts. Mark whose each account is on its page.
Alerts when a bank needs you to sign in again or an account is heading short, and a daily summary of your balances.
| Tell me about | This device | Discord |
|---|---|---|
| A bank that needs me to sign in again | ||
| A daily summary of my balances | ||
| An account heading short of cash |
Sent to a channel in your Discord server.
Which checking and savings accounts the Overview’s Next 30 days looks at, and the least you want to keep in each.
Each run of the scheduled sync, for every user: what it synced, the Discord alerts it sent, and what the cleanup after it removed.
A run still marked running half an hour after it started stopped without finishing.
Each address that may sign in or has, once, with where it stands. An invitation the allowlist doesn't have yet comes first.
Of the transactions the app filed on its own, how many users then changed rather than kept, by the step that filed them and by category, across every user.
Counts only: nothing about what the transactions were.
Each month's requests to Claude for filing transactions, across every user: how many merchants and notes they asked about, their tokens, and an estimated cost at the prices in the app.
The build this server is running and the environment it was started in, and the build of the app on this device, with whether it is the one the server serves.
What this server is connected to right now. The password is removed from the connection string.
Your last 50 page loads and returns to the app on each of your devices with timing reports on, as their critical path.
Timing reports send this device's load times, animations and pull-to-refresh attempts to the server log, to diagnose slow loads and gestures. They hold timings and the app's own element names, never anything the pages show.
Each trace runs from navigationStart (or visibilitychange) to the first screen's render (js/criticalpath.js). All times in ms from the trace's start. CP start and CP end are when a step was on the critical path; Prior and Post are how long it ran before and after. Server rows come from Server-Timing; the handler's parts are listed, not placed, since some run side by side, and ×n marks a total over n calls. Network rows take half a round trip each way: the trace's quickest request that did not wait for a server to start, else a connection handshake, else this device's recent round trips, as each row says. The server keeps your newest 500; each browser also keeps its own last 20, shown here when the server's cannot be read.
Every message sent to your Discord channel or your devices, and what came back.
Every category a transaction can be filed under. A group is a category too, for when only the group is clear, such as Shopping for most Amazon orders.
A rule files every transaction it matches, except ones you filed yourself. When two match, the more specific one wins.
For a merchant your rules and history don't know, the app can ask Claude.
It sends the merchant's name and the bank's text with long numbers masked, roughly how much and which way the money went, and the account's type: never exact amounts, account numbers or your name, and your notes only if you turn that on below.
After each sync, Claude reads the note on a transaction your own choices and rules haven't filed, with the bank's text masked as above, and files it when the note says clearly what it was for. Off, a note is sent only when you press Save and suggest a category.
For everyone, as an admin
Lets Claude read transaction notes, for everyone.
Anyone can press Save and suggest a category under a note, which files nothing until they tap the answer, and each person can turn on Also read my notes in Settings, so notes their own choices and rules leave open are read after each sync. Each note sends that one transaction's note and bank text, never its exact amount: about half a cent asked alone, less read with others.
How the app files each merchant from what you chose before, or from the history you imported where you haven't chosen yet.
Your paychecks, bills and card payments that come around regularly, and what they’ll leave in each account. Everyday spending isn’t included.
Use this when one real account shows up twice. Balance history and transactions are combined under the account you keep, and the other one disappears. This cannot be undone.
Decides where it appears on the balance sheet.
What it was worth on that date.
Three-letter code, such as USD or EUR.
When a transaction
file it as
You chose these categories yourself, so a rule leaves them as they are.
Choose what counts toward your monthly spending. Switching off something that doesn’t come around every month, like a trip or a yearly tax bill, makes one month easier to compare with the next. It stays out of every month’s total, here and on the Overview, and is still listed separately.