Allow All & goal runs

With Allow All off (the default), every change Literess proposes waits on a confirmation chip until you approve it.

With it on, her proposals apply the moment she makes them: new block translations, glossary and style guide edits, document moves, workflow runs, workspace settings. She keeps working through the task in the same breath instead of stopping after each proposal.

The chip still appears in the chat, already marked “Applied automatically”, so you keep a record of everything she did.

When she changes several blocks of one document this way, the card offers Review in one screen: her applied edits beside the earlier text, each with Keep or Revert to previous. See the review screen.

Two exceptions hold no matter what:

• inviting a teammate always asks first, because an email leaves your workspace
• deleting a saved workflow always asks first, because there is no undo.

Two places flip the same setting: the switch under Settings → Notifications, and the sparkle button in the header of the Literess panel, lit while the mode is on. You can also just tell her to turn it on. That request arrives on a chip you approve, so the mode can never switch itself on without one deliberate click from you. Turning it off works from anywhere, mid-task included.

No. When she writes to you without being asked (a failed run, a faster way to do something), whatever she proposes waits for your click, even with Allow All on.

To let those apply too, turn on Allow All on her own, just below Allow All in Settings → Notifications. Taking the chat to another document always asks for confirmation, whichever switches are on.

Warning. Beware that turning this setting on may lead to Literess spending all your balance doing whatever she finds suitable.

While she works, the send button in the composer becomes a square Stop button. Press it and she halts where she is: whatever she already applied stays applied, the words she already wrote stay in the chat, and anything she hadn’t started is dropped rather than left half-done. This works in every conversation, and if a goal run is underway it pauses the run too.

A goal run is how Literess handles work that spans many blocks or pages: translate the whole document, chase one recurring mistranslation through all six chapters, check every block against the style guide.

Instead of doing one step and waiting for your next message, she sets herself the goal and keeps working turn after turn until it’s reached.

There’s no command to learn: describe the job and she takes it on.

While a run is open, a thin strip sits above the composer with the objective, the turns she’s used, the words she’s written, and a small bar for the run’s allowance. Pause on that strip stops the run once the current turn ends. Resume picks it back up.

With Allow All off, a goal run doesn’t wait for you between batches. She keeps working while her proposals wait, and each one appears on the review screen as she makes it, so you can accept or reject them while she writes the rest. Once 30 are waiting she pauses, and she carries on as you decide them. Each proposal is billed when she writes it, whether you accept it or not.

For bulk translation she normally reaches for the pipeline first: start a translate workflow, watch it run, then put her own effort into reviewing and fixing the result.

Her hand-written work is the expensive, careful layer, so she saves it for the places it beats the pipeline. If you want her to write everything herself, say so once and she will.

• She reaches the objective, declares the goal complete, and closes with a summary of what she did.
• She hits something she can’t work around, says so plainly, and tells you what would unblock her.
• The run uses up its built-in allowance of turns and compute. She finishes the turn cleanly and reports how far she got. A fresh goal continues from there.
• You press Stop or Pause. The run waits until you resume it.

Allow All and goal runs change who presses the button, never the price: the same work bills the same credits from the same balance. On a team document her work bills the team pool, like any run there.