Settings

Settings opens a list of rows rather than a wall of controls, and the answer beside each name lets you read the whole state before you open anything.

• Account — who you're signed in as, the timezone, your password, what the phone app needs, the calendar link, a download of everything you have, and the way out.
• AI — one switch for the whole thing, then one per job, each with its model and its prompt.
• Sleep — one switch for the morning sleep reading, off if you don't want the entry at all, and the life area each morning's entry is filed under. Filing it under no area is a real answer, and the entry is still written.
• Tasks — the Goals & task detail switch, and your statuses once it's on.
• Notifications — in the phone app only: whether this phone can be reached, which kinds of news reach it, and a test that says what became of one.
• Reminders — the nudges you have set, and where you set another.
• Areas — making, renaming and colouring the areas of your life.
• Features — the parts that run on an outside service you pay for, each with its own switch.
• Keys — the API keys your account runs on, one row per service.
• Backend — which backend this app is reading and writing through, and how to point it at another one. The admin guide covers it.
• Guides — this manual, one page per screen. It was a ? in the corner of every screen until Sep 2 2026.
• Development — the work on the app itself: what's being built right now, what's queued, what's waiting on you, and the standing checks with their last runs.

Settings is off the menu on both surfaces, since the menu is for the places you work all day. It is the gear in the top corner, beside the magnifier and the chat bubble, and that corner is the same three icons at every width and in the installed phone app. The corner is on all six screens with a bottom bar, so Settings is one tap from wherever you are standing rather than a trip to Day first.

The phone app puts its settings on one scrolling screen instead of a list of rows, under a Server row naming the server it is signed in to. Nearly everything above is on that screen in the same words, and the differences run both ways. Notifications is on the phone and has no row in a browser, since it answers a question about this phone alone. Changing your password, Backend and Development are in a browser and not on the phone. Anything you change on one shows up on the other, since both are asking the same LifeOps.

Account names who this LifeOps belongs to and which zone your days are measured in. Every date the app works out resolves through that zone, so the zone decides which day an entry belongs to and when a day rolls over.

Both apps follow the device you're holding. Land somewhere and your days move with you, with nothing to set — the phone has always done this, and the web does now too. On the web, tapping the zone also opens a search over every zone there is, each showing the current time in it, for when you want a zone that isn't where you're standing.

Changing the password is here too, on the web: the password you use now, the new one, and the new one again. A new password needs at least twelve characters, and every refusal ends by saying your password has not changed. Browsers already signed in stay signed in, this one included, so sign out on any you want out. A forgotten password is still a request to whoever runs your LifeOps, covered in the owner's guide under Your login.

Your Google Calendar connects here too, under Calendar: one button, Google's own permission page, and you're back. Once connected, the section lists every calendar on your Google account. A tick beside each chooses which appear on your Day — work, home, and your own, not just one — and a life area beside a ticked calendar files its meetings under that area, so a work calendar's meetings read as work and the time log a Done meeting becomes does too. Your meetings arrive as tasks and appear within fifteen minutes, and Disconnect in the same place forgets the link. If the section says the instance isn't registered with Google yet, that one-time step belongs to whoever runs your LifeOps.

Your phone on the same screen shows the server address and mints an access token. The phone app does not need either of them any more: it signs in with the username and password you use here. Keep this for a phone pointed at a server its build does not know about, and for handing somebody a way in without handing over a password. Getting in covers both routes.

Your data takes everything in your account out as one zip: every entry, task, document and setting, plus your photos and attachments. A large account takes a few minutes to prepare, and a download that stops early will not unzip, so start it again rather than trusting a short file. Under the button is one line saying whether anything holds an off-site copy of this LifeOps and when it was last made. Bringing data back in is not built, so this is a way out and a way to hold your own copy rather than a way to move between one LifeOps and another.

Sign out asks twice on both apps, and Sign out for good is the press that does it. Stay signed in is the way back out of the question. In a browser it ends the session and returns you to the sign-in page. On the phone it also clears the stored token off the device, so getting back in means signing in again.

The list of life areas is yours to write. Adding one takes a name and nothing else. Tapping a name lets you rename it, and the new name shows everywhere the old one already was. The whole app files by that list. Tasks group by area, journal entries take one, and the Day shows their colours.

Each area also has a colour, picked from a palette of thirteen. An area you never pick for reads Automatic and takes a colour worked out from its name, so a fresh LifeOps is already colourful rather than grey. Automatic is also the way back if you change your mind.

Each area can also say what it is, in a line under its name that you tap to write. That line is what the AI reads when it files an entry, a task or a document, so an area described in your own words gets filed the way you meant it. Under the list is a field for adding one, and under that a line counting how many of your areas have a colour you picked rather than Automatic. There is no delete. Removing an area would unfile every task and every entry filed under it with nothing to undo it, so renaming covers a typo and an area you've finished with simply gets nothing new.

Some of what this app does runs on outside services, and those services bill whoever owns the key. Settings → Keys is where the keys live. Each row is one service: what it is used for, whether your account holds a key for it, and a field to store one. A key is stored once and never shown again. Saving an empty field removes it.

Three services take a key. Anthropic is what every AI job and Chat run on. ElevenLabs turns a recording you post into a transcript. Resend emails you when a background job breaks or recovers. Google Calendar is connected instead of keyed, under Account.

A key belongs to your account and pays for your calls alone. Yours runs on that key and on nothing else, and no other account can spend it. There is no instance-wide key and no deployment variable behind the scenes. An account with no key for a service cannot use what that service powers, and the Features page says so on the row rather than leaving a switch that promises something and does nothing.

Some things this app can do are not free to run. Transcribed recordings is the only one so far. Posting a video or a voice memo sends it to ElevenLabs to be turned into a transcript, and ElevenLabs bills whoever owns the key, by the minute of recording.

So it is off until you switch it on. Settings → Features has the switch, and under it a field for your own ElevenLabs key. Paste the key and turn the switch on, and a video you record from then on comes back with a title, a summary and a transcript. Leave it off and a recording is still saved and still plays. It is not sent anywhere.

The two halves are separate on purpose. A switch that is on with no key says which one is missing. Your key is stored for your account and never shown again, and saving an empty field removes it.

The AI page starts with one master switch, the AI on or off for you, and under it one switch per job. The list of jobs comes from the server itself, so a job cannot run without a switch appearing here. Each row says what its job does and exactly what it sends when it runs. Under that, Model chooses which model the job runs on, and Prompt opens the words it is given, for you to edit and save. A row whose prompt you have edited says so, and Reset to default puts the shipped wording back.

Area naming files a new journal entry under one of your life areas, and it sends the entry's text and your areas with the descriptions you wrote for them to Anthropic's API. It runs as a background sweep, about two minutes behind your writing rather than in the moment you save, and an entry it cannot place stays unfiled and is never asked about again. Document filing does the same for a document with no life area, on a five-minute sweep, reading the document's name, kind, description and text alongside those same area descriptions. Task filing does the same for an open task with no life area, reading the task's words, its kind and its note alongside them too. A task under a goal takes its goal's area without asking the model at all. Area descriptions drafts what a life area you have only named means, sending your area names and the descriptions you have already written. The draft arrives marked as a draft, and it is yours to edit or clear. Transcribe a recording turns a video or a voice memo you post into a cleaned-up read-through of what you said. What changed in a version writes the line saying what moved between two versions of a document or a goal. Summarizing a note, writing the status line on a task, and reading travel time out of a meeting's title each have a switch here now.

Off, entries save with no area filled in. Everything you type is still stored, still searched, and every control still works. The owner's AI page covers where the text goes once it leaves. Your LifeOps may have AI switched off as a whole, in which case this page says so and there is nothing to choose.

Goals & task detail turns the simple checklist into the full task system, adding statuses, task types, three ways of grouping the list, and a filled-in Goals tab. The same tasks are underneath either way, so turning it off hides the detail and destroys none of it. The row on the Settings index says which one you are on.

Goals & task detail covers what that switch gives you and how to work it.

Notifications in the phone app starts with This phone. Turning it on is where the app asks your phone for permission, unless setting a reminder has already asked for it. Under it is a switch for each kind of news the app can send. Every kind starts off, and switching one on is what lets that kind through. Reminders covers the nudges you set, and Background jobs tells you when something that runs on its own stops working, and again when it starts working. A LifeOps run with notifications off altogether says so above the switches, rather than storing answers nothing will honour.

Send a test sends one notification to this phone now and says underneath what became of it. There are four answers and it rounds none of them into another. Sent, not confirmed yet means the message left and Apple has not answered for it yet. The screen keeps asking for about a minute, then says Not confirmed rather than guessing. Arrived appears only once Apple has confirmed the delivery. Didn't arrive comes with Apple's own reason. And when nothing left at all, the line names which nothing it was, since no phone registered, notifications off on this server, and a notification service out of reach are three different problems with three different fixes. The test ignores the kind switches, so it answers whether this phone can be reached even with every kind off.

Recent keeps the answer after you have stopped looking. The last ten notifications the app sent are listed with what became of each, so a nudge that never turned up is something you can go back and read the reason for.

Turning This phone off stops the app reaching this device and leaves your phone's own permission alone, since only you can give that back. The kind switches keep their answers while it is off, so turning the phone back on does not ask you everything again.

Reminders opens on what you have set, under Coming up, soonest first, or on Nothing set. when you have none. New reminder is the group under that, and History under that again lists the ones that have already gone off. A reminder takes words of its own, a day, a time, and a repeat: Once, Every day, Weekdays or Every week. A repeating one works its next time out from the wall clock as it fires, so it survives travel and the clocks changing.

Most reminders are about nothing in particular, which is why they are their own thing rather than a field on a task. When one IS about a task, start it from that task instead: Remind me… on the task's own menu opens the same composer already saying what the task says. Either way the task keeps its own date, which may be a different day or no day at all.

A reminder interrupts you once and is then over, so there is nothing to mark done and nothing to snooze. Arriving is what finishes it, and it moves from Coming up to History. Before it goes off, the row's menu offers Edit and Delete, which is the way to call one off. On the phone, a reminder the app has already seen arrives from an alarm the phone set for itself, which is why setting one asks for notification permission. Turning This phone and Reminders on under Notifications is what lets the server send one the phone has not seen, such as a reminder you set in a browser since you last opened the app. In a browser, Try one now under the composer asks that browser to show one, so you can see whether it reaches you there.