---
title: delegate-task session_break field
type: concept
tags: [delegate-task, using-tasks, autonomous-runner, session-boundary]
updated: 2026-06-09
---

# delegate-task `session_break` field

`delegate-task` v0.2.2 adds an optional `session_break` field to the task-body template, plus
a sixth pre-flight question. This is the **authoring** side of the marker whose **consumer**
side lives in `using-tasks` — see [[using-tasks-session-break]].

## Problem

`using-tasks` v1.2.0 can stop an autonomous runner after a task closes (instead of chaining
`tasks_claim_next`) **iff** the closed task carries a `session_break` marker. But nothing in the
delegation flow prompted the author to set it — so the capability sat unused unless someone
hand-edited the task body. The marker has to be *placed at delegation time* to be useful.

## Design

- **Pre-flight Q6** (after Q5 `notify`): *"Session-break после этой задачи? — нужен ли разрыв
  сессии после её закрытия (domain-switch, milestone, heavy infra)?"* If yes → set
  `session_break` in the task body; if no → omit it (default unchanged).
- **Template field** (optional, in the trailer next to `weight` / `notify` / `allow_upgrade`):
  `session_break: true | "<следующий трек / hint>"` with an inline comment pointing at the
  `using-tasks` stop behaviour. `session_break` (lowercase, underscore) is the same frontmatter
  key `using-tasks` reads.
- **Value:** `true` (next track = "см. STATUS.md") or a hint string naming the next track.

## When to set it (three cases)

1. **Смена домена / репо** — the task ends one track before an unrelated one begins.
2. **Milestone-задача** — the last sub-task in a feature's group.
3. **Тяжёлая инфра-задача** — shared checkout, migrations, deploy — where it's sane to stop and
   inspect state before continuing.

Not a default: setting it routinely would make `using-tasks` tear the session after every
close. It is a marker of a *real* boundary, an authoring choice — same rationale as the
consumer-side "marker not heuristic" argument in [[using-tasks-session-break]].

## Versioning

PATCH bump (0.2.1 → 0.2.2): additive optional field + one extra pre-flight question, no existing
behaviour changed. (The version target was fixed by the delegating task.)