AI

The switchA switch in Settings turns it off

In Settings › AI, a switch labelled AI Master Switch shows whether it is on, with a sentence under it saying what that means right now. Below it, under Each job, every job this instance runs has a switch of its own. Flipping one takes effect on the next background sweep, within a few minutes, with no restart and no redeploy.

Turning it back on fills in the recent gap: the sweep classifies entries from the last two days that never got a verdict. Anything older keeps the shape it was saved with.

What stopsFiling stops, and nothing you wrote changes

With AI off, no job the AI has happens.

Area naming

An entry you write stays with the life area blank instead of being filed under one. An area you set yourself is never touched either way.

Task filing

A task you add stays with the life area blank instead of being filed under one, so it groups under Other on the Tasks page. A task under a stream still takes its stream’s area: that half is a rule rather than a model call, and it does not stop. An area you set yourself is never touched either way.

Document filing

A document you start stays with the life area blank instead of being filed under one. An area you set yourself, from under the document’s title, is never touched either way.

Transcribe a recording

A video or a voice memo you post is stored and playable, with no transcript, no title and no summary written for it.

What changed in a version

A sealed version of a document or a stream keeps its text and its timestamp, with no line saying what moved since the version before it.

Document summaries, task status lines and travel time are planned, tracked as issues #261 to #263, and each arrives here with its own switch when it is built.

What you type is stored exactly as typed, search still searches it, the timeline still lays it out, and no control anywhere in the app breaks or greys out.

The owner's guide on AI covers what the AI reads when it is on, and which text never leaves the instance.

Model and promptEvery job names the model it runs on and shows the prompt it runs with

Each job row holds two controls beside its switch. Model marks the one in use and offers the other, and Opus is the model every job ships on. Prompt opens the text that job will run with, so an edit starts from what is running rather than from a copy of it. Both controls are on the phone as well as the web, on the same rows.

The three filing jobs hold markers in curly brackets where the app drops their inputs in, and an edit that drops one of those markers is refused instead of saved: the app names the markers it needs back, your text stays in the box, and the job goes on running the wording it already had. The other two jobs take their material as a separate message, so their wording has no marker it must keep. Models & prompts covers both controls in full.

For the whole instanceWithout the backend's API key there is no AI, whatever Settings says

The switch in Settings is yours. The second switch belongs to whoever runs your LifeOps: the instance has AI only while its Anthropic API key is set on the backend. Remove the key and AI is off for the entire deployment, and your in-app switch cannot override it.

When the key is absent, the AI section in Settings replaces the switches with one sentence: AI is switched off for this whole instance, so there is nothing to choose here. Removing the key is a backend act, and it is the switch to ask for when the answer must stay "no" even if Settings gets flipped.