A chat window drafts fine. It also forgets what you corrected the moment the tab closes, so month six costs you what week one did.
Garry keeps a company brain: a private repository holding the strategy, the customers, the decisions and the lessons. Every employee reads it before working, and a change to it is a draft you approve like any other. The Sunday retro writes back what the week taught. The correction you make once is the one you make.
A chat window hands you text. You paste it into the email, open the pull request, post it, and follow up — the work around the work is still yours.
Garry opens the pull request, sends the approved email, publishes the approved post, and takes tasks from the channel you already use. The result comes back as evidence: the commit, the message id, the permalink.
To make a chat window do anything real you paste it a credential and hope.
Garry's employees never hold one. Keys for GitHub, email, ads and social accounts are sealed in the control plane and used only by the trusted worker, only for a draft you approved, once. A model call goes through a spend gateway with the company's budget on it, and you never handle a model key at all.
A chat window does what you type. Garry does what you approve: every email, post, pull request and brain change waits in one queue with the exact text and the evidence beside it. Reject it and nothing happened.
A one-off question. A paragraph you will rewrite yourself anyway. Thinking out loud. Keep it open — Garry is for the work you want done rather than discussed.