Standing instructions

A nudge is a short reminder Vera repeats every few turns, so the model keeps following it.

• Why: models have limited attention. An instruction from early in a long conversation gets buried, and the model starts to forget it.
• What to use it for: things you want kept up all the time, such as concise answers or test results in every summary.
• Where it applies: everywhere, in one workspace, or for one agent.

Nudges add guidance. They do not change tools or permissions.

What a nudge does

On a turn where a nudge applies, Vera adds its text as a hidden message right after yours. The model reads it with your request. The transcript and exports leave it out, and the conversation keeps it where it was added.

What the model sees

1systeminstructions, tools, rules

1youcount the doubloons in treasure/chest.yaml

>count the doubloons in treasure/chest.yaml

>

1

You ask the crow to count the loot.

Vera's instructions and tools go first, then your message.

2

Your nudge matches, so Vera adds it right after your message. The transcript does not show it.

3

The model asks to read the chest.

4

The chest goes in.

5

The answer ends with arr, as the nudge asked.

6

Turn 2.

The nudge runs every 2 turns, so this turn gets none.

7

Everything above the line is sent exactly as last time, so the provider reads it from its cache.

8

Only the new message is read fresh.

9

Turn 3.

You send the next order.

10

The nudge is due again. Vera adds it after this message, and the first one stays where it was.

11

Nothing above moved, so the cache still covers all of it.

12

The answer ends with arr again.

Wide view1 of 12

Adding nudges does not break the provider’s prompt cache (the KV cache). Every earlier message, including earlier nudges, is sent again exactly as before, so the provider reuses its cached work and only reads the new turn fresh.

Create a nudge

1. Run /nudges, or choose Standing nudges from Ctrl+P.
2. Press N to create a rule.
3. Enter a name and an instruction of up to four lines.
4. Choose when it applies and how often.
5. Select Save changes and press Enter.

Changes apply on the next user turn. A workspace rule uses the full workspace path and initially selects the current workspace. Agent matching uses the exact definition name.

Choose a frequency

Every turn applies the preference on each matching turn. A number from 2 to 10 repeats it at that interval, beginning with the first matching turn. For example, 3 applies on turns 1, 4, 7, and 10.

Each conversation, including a delegated conversation, counts independently.

Edit, disable, or delete

In the form, Tab or Up/Down moves between fields. Type in Name, Instruction, Agent, and Workspace. Space changes Status, Apply when, and Frequency. Left/Right moves the caret in text fields.

Enter adds a line inside Instruction and advances from the other text fields. Up/Down leaves a multiline Instruction at its first or last line. Use Page Up/Page Down or the wheel to inspect a long match value.

Know when a nudge applies

A Nudge on notice above the composer names enabled rules that match the conversation. It remains visible between scheduled applications because the rules are still enabled.

Rules are saved in ~/.vera/standing-nudges.json, created on the first save. An invalid file produces an error with its path. Form errors stay in the form so you can correct them before saving. Deletion cannot be undone.