GTT interrupts you as little as possible. The agent settles on its own everything that governed context or a simple, reversible choice can settle. It asks you only what is yours, and when you have to run something it gives you one command.
Available since GTT 1.11.0 (hand-over) and 1.12.0 (questions), refined in 1.15.0 and 1.16.0. Details: https://github.com/GTT-Community/gtt-bootstrap/blob/main/.gtt/docs/agents/operations.md
Questions: rare, and always in the same form
A question exists only when something cannot continue without your answer and the decision is yours: an account, a key, money, a legal matter, a product matter or a governed file. A product or governed question names the Story or Epic it blocks; no question repeats an open one; at most four are open at once.
Questions reach you in the chat, as one batch of up to four. Each has a short topic, the question with what your answer closes, two or three numbered options with what the agent will do if you choose each (the recommended one first), then "something else" and "talk about it in the chat". With no answer, the agent uses the recommended option and keeps working on everything that does not depend on it.
Behind each question is one small file in `gtt-domain/pending/`. It is the silent record; the agent does not announce files. Normally the folder is empty.
Decisions you only need to hear
When the agent decides something that changes scope, time, cost, security or the design, it tells you in one line. If you do not object in 7 days it is closed; an unanswered question is never deleted.
Your answer is only yours
You answer in the chat (`14: 1`, "ok to all"), in the file, or with `gtt answer 14 1`. The agent can record your chat answer only with a real quote of your last messages, and it cannot write or overwrite an answer. An answer that looks like a key is refused: keys go in `.env.local`. An answer never ratifies the governed design: that stays `gtt promote`.
Hand-over: one line, one command
A governed act keeps its own command (`gtt promote <set>`). Anything else that changes state or takes two or more commands becomes a run plan: the agent writes what it does, why and what it changes, and GTT generates the script from a fixed template, seals it and reviews it (no writes to governed paths, no Git history, no `rm -rf` outside temporary folders, no download piped into a shell). You get one line and `gtt run <n>`. The agent never writes the script, edits it or runs it; a hand-edited script is refused. Your run is logged and archived.