Repository navigation
Aperture 0.4.0
Aperture Bot now works without being asked: it reviews pull requests, replies to new issues, explains a red default branch, and posts a daily brief of what needs you, ending every reply with suggestions you tick to have it do them. Get it with Hankaws/aperture-bot@v1 (v1.5), or switch the jobs on from the Bot page.
Subscribers can also switch plans from the pricing table, paying twice no longer leaves two subscriptions, and long agent turns wrap up before the server's time limit instead of being cut off.
Added
Aperture Bot's daily brief. The look-over job ("Daily brief" on the Bot page, now daily by default) posts each morning what needs you, read from GitHub (CI on the default branch, pull requests waiting longest, issues quiet for two weeks), and up to five ideas from reading the code (likely bugs, untested paths, TODOs, open issues), each a box to tick. "Fix it without asking" (always-allow: red) has the bot fix a red default branch at once instead of waiting for a tick. (#157)
Aperture Bot reviews pull requests. /aperture review, or every push with "Review every pull request" on, posts a GitHub review with a comment on the line of each likely bug (only what it is at least 80% sure of) and a reply with each fix as a box to tick. It changes nothing, reads a fork's changes without running them, and does not repeat a comment already on its line. (#156)
Aperture Bot can work unasked. With "Reply to new issues" on, it reads each new issue and the code and replies with what it would do (or asks for what is missing), its first box being the issue itself to tick. With "Explain red CI" on, a workflow that fails on the default branch is explained on the bot's own issue, once per red commit, with the fix to tick. Both change nothing on their own and stop at 20 replies a day (daily-limit). (#155)
Aperture Bot answers questions and takes suggestions with one tick. Comment /aperture why does the login test fail? and it answers on the thread from the code, the diff and the failing checks, changing nothing. Every reply ends with what it would do next as boxes: tick one and it does it, as if you had asked with /aperture. Ticking needs the workflow to listen for edited comments, as the Bot page's and the README's now do. (#154)
Subscribers can switch between Pro and Team, or between monthly and yearly, from the pricing table: Paddle prices the change first ("You pay $18.50 now for the rest of this period"), and Settings → Plan shows the switch once Paddle confirms it. (#153)
Fixed
Aperture Bot can no longer be made to @mention people: text it did not write itself (the model's words, issue titles, review notes) has its mentions made inert, and an HTML comment in it can no longer hide the bot's boxes. Replies nobody asked for queue one at a time, so a burst of new issues cannot slip past daily-limit, spend at most 150,000 tokens each, and say to read a suggestion before ticking it. (#158)
Paying twice no longer leaves a second subscription charging every month: a second live subscription for the same account is cancelled the moment Paddle reports it, and buying again while a checkout is open reopens that checkout, or says the payment already went through. (#153)
A long agent turn wraps up before the server's time limit and keeps what it staged, instead of being cut off mid-reply; a test run is shortened, or left for the next turn, when there is not enough time left. A reply that still ends early says it was cut off and offers Retry, and an external agent that cannot start now shows why. (#152)
Signed in, the editor no longer rebuilds its whole layout as it opens, and on a phone it no longer flashes "Sign in": the phone account button waits for the session, as the desktop bar does. (#151)
Every change, newest first: CHANGELOG.md