You start a team working and step away from your desk. One teammate reaches an action that needs a permission decision before it can go ahead. What happens to that prompt, and what does it take to clear it?

The principle — consent is yours to give, and it is asked for in the session you are sitting in rather than the one doing the work.

Why the key is correct — two sentences settle it between them. Teammate permission prompts appear in the lead session, so approve them there yourself. And a teammate can't approve a permission prompt or supply consent on your behalf, and a teammate that was denied an action can't relay it to another teammate to bypass the check. So the prompt is not hidden somewhere you would have to go looking: it is in front of your lead session, and it stays there until you come back to it. There is a practical move upstream of the stall, and it is the reason this is worth knowing before you walk away rather than after. Teammates start with the lead's permission settings, so whatever your own session may already do without stopping to ask is what a teammate may do too. Settling that first is what keeps a long unattended run from spending most of it waiting on you.

Why the others are wrong — the prompt does not wait in the teammate's session; it is raised in yours. A peer cannot approve it, and a refusal cannot be routed around by handing the action to another teammate. And a teammate does not inherit the lead's discussion, so there is no earlier approval in its context to reuse.

Remember this — a teammate can be blocked on your decision, and only you can unblock it. Decide what the team may do before you leave it running.

Sources — Anthropic's Claude Code documentation on orchestrating teams of sessions.