Skip to content

Commit b9ff438

Browse files
committed
docs(acp): clarify managed copilot policy hooks
1 parent 256f41a commit b9ff438

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

‎docs/user/providers-acp.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -136,9 +136,10 @@ conversation from before the checkpoint.
136136
GitHub Copilot can write T3's thread titles, commit messages, branch names, and pull request
137137
descriptions. Choose a Copilot model in **Settings → Threads → Text generation**. T3 Code never
138138
switches to Copilot on its own, because each request counts against your Copilot plan, so a low-cost
139-
model is a good choice. These requests run without tools and without your Copilot hooks, MCP
140-
servers, plugins, or custom instructions, and they stay out of your Copilot session history. Copilot
141-
cannot write review guides, which need to read the checkout.
139+
model is a good choice. These requests run without tools, user-configured Copilot hooks, MCP
140+
servers, plugins, or custom instructions. Administrator-managed Copilot policy hooks still run.
141+
A `userPromptSubmitted` policy hook receives the text-generation prompt. These requests stay out
142+
of your Copilot session history. Copilot cannot write review guides, which need to read the checkout.
142143

143144
Other Registry agents are not used for text generation. Configure another provider for those
144145
actions.

0 commit comments

Comments
 (0)