Engineering
What changed since Monday, with the commits linked.
#paymentspublic channel3 tool calls
Three days of commits across connected repositories, answered in the thread with each commit linked and the messages turned into what actually changed. The follow-up — which PR touched the retry budget — is a code search, not a guess.
Sam9:31 AM
@attest_tag what changed in the payments client since Monday?
attest_tagApp9:31 AM
- github_recent_commits · acme/payments · since Mon · 3 commits
- github_find_code · “retry budget” · 2 files
- github_get_pr · #418
3 commits on main since Monday, all by Sam:
- Thu — payments: jittered backoff between attempts (1c9ef3b)
- Wed — payments: replace the retry count with a total time budget, 2.5 s per request (a41d02e)
- Tue — payments: make the timeout error retryable (7b3c9d0)
The budget lives in retry.go and is read in client.go; the PR that introduced it is #418, merged Wednesday, reviewed by Priya.
google/gemini-flash4.9k in380 out$0.0027Configure
How the turn went
A connected repository, named tools, and a link on everything.
- 01
The repository is a connection like any other
An owner/name and a token, checked against that repository first, sealed, and attached to the channel. The channel gets the GitHub tools and nothing else the bundle might grow later.
- 02
Named tools, not an API reference
github_recent_commitsandgithub_find_codeare thin tools from the GitHub pack, which is what makes an open-weight model reliable here. A generic HTTP tool and the GitHub docs would have it improvising. - 03
Links on everything
Each commit, the PR, the file. A summary without the link is a claim; with it, it is a starting point.
What it needs
The setup, in the console.
What it will not do
Enforced outside the model.
It reads. Creating a branch, a PR or a comment is a write and waits for a Confirm — or goes through a fix job, which has rules of its own.
A repository connected to another channel is not reachable from this one; scope is per channel.
Try it
Say it in a channel it is in.
The sentence as it was typed. It works in any channel the bot has been invited to that carries the connection above — no command syntax, no form, and follow-ups in the thread need no mention.
@attest_tag what changed in the payments client since Monday?
github_recent_commitsgithub_find_codegithub_get_pr
More in Engineering
Ask the repository a question. Then hand it the fix.
- “Fix it and raise a PR” — and a draft PR arrives.#payments · fix the flaky retry-budget test so it stops depending on wall-clock time, and raise a PR
- The decision, who made it, and a link to where.#payments · what did we decide about retries this week, in three bullets? and who first suggested capping total retry time instead of the count?
- Your own internal API becomes a tool.#ml-internal · what did the extraction of this document cost, end to end?
Bring the channel this would live in.
Sign up, connect the service above in one channel, and type this sentence yourself — or run the same binary on your own infrastructure.