# Upgrade Guide — v0.12.6

<!-- bump: patch -->

## What Changed

Jobs now default to **quiet mode** (`on-alert`). Instead of sending a Telegram notification on every job completion, jobs are silent unless:

1. **The job failed** — failures always notify (via consecutive failure alerts)
2. **The session signaled attention** — if the LLM running the job includes `[ATTENTION] reason` in its output, that triggers a notification

The `telegramNotify` field on job definitions now accepts three values:
- `true` — always notify on completion (legacy behavior, opt-in)
- `false` — never notify
- `"on-alert"` — only notify on failure or explicit attention signal (**new default**)

When `telegramNotify` is undefined (the common case), it defaults to `"on-alert"`.

**Topic creation is now lazy for on-alert jobs.** Topics are only created when the job actually has something to report, instead of being created eagerly at scheduler startup. This prevents a flood of empty job topics on fresh installs.

**Attention protocol injection:** Job sessions in on-alert mode receive a preamble instructing the LLM to use `[ATTENTION] reason` when it finds something noteworthy. This gives the agent a way to break through quiet mode when it matters.

## What to Tell Your User

- **Quieter notifications**: "Jobs are now quiet by default. You'll only get notified when a job actually finds something that needs your attention or when something goes wrong. No more firehose of routine job completions."

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Quiet job mode (default) | Automatic — all jobs default to on-alert mode |
| Explicit always-notify | Set `"telegramNotify": true` in jobs.json for jobs you want to always hear from |
| Attention signaling | Include `[ATTENTION] reason` in job output to break through quiet mode |
| Lazy topic creation | Automatic — topics created only when needed |
