Document messaging agents and the usage page
1 file+18−00/1 viewed
| 116 | 116 | repository wants approvals from people, it waits for them, and shows | |
| 117 | 117 | **Needs you** until they arrive. | |
| 118 | 118 | ||
| 119 | + | ### Talking to an agent while it works | |
| 120 | + | ||
| 121 | + | While a g1t agent is making or revising a change, its pull request shows | |
| 122 | + | **Message the agent**. Write a correction, a hint or a change of plan; the | |
| 123 | + | agent reads it at its next step, without starting over, and it is | |
| 124 | + | recorded in the session. A message sent as the agent is finishing still | |
| 125 | + | reaches it: the agent keeps going to act on it. Your own agent can send | |
| 126 | + | one through the `message_agent` tool or `POST | |
| 127 | + | /repos/{owner}/{name}/pulls/{number}/messages`. | |
| 128 | + | ||
| 119 | 129 | ### Asking the agent for changes | |
| 120 | 130 | ||
| 121 | 131 | Review a g1t agent's pull request the way you would anyone's: comment on | |
| 218 | 228 | There is no subscription and no seat price. A small change costs a few | |
| 219 | 229 | cents. | |
| 220 | 230 | ||
| 231 | + | ## Seeing what agents cost | |
| 232 | + | ||
| 233 | + | A workspace's **Usage** page shows what its agents have cost over a period: | |
| 234 | + | spend per day by kind of work (making changes, reviews, revisions, | |
| 235 | + | catching up, planning), and by repository, model and pull request, with | |
| 236 | + | the credit left and how long it lasts at the current rate. The sidebar | |
| 237 | + | shows this month's usage. | |
| 238 | + | ||
| 221 | 239 | ## What a sandbox has | |
| 222 | 240 | ||
| 223 | 241 | Git, common shell tools, and toolchains for Node.js, Python, Go and Rust, so |