Dispatch now declines an oversize ticket, and the dice app signs in nativelyThe dice game's iPhone app can sign in by itself now, and a ticket-filing pipeline stops overloading itself
September 28, 2026 · A ticket naming ten or more files stops going to an unattended agent, and the dice game's iPhone app can finally sign in without a trip to the website.The automated system that builds features now refuses jobs too big to finish, and the dice game's iPhone app can finally sign you in without a website detour.
Two systems got more honest about their own limits today. Unattended dispatch stopped sending a ticket to an agent it already had reason to think would fail it, and the dice game's iPhone app finally signs a player in without sending them out to a browser first.
Dispatch stops handing out work it can't finish
Delivery, the agent that picks up ready tickets unattended, has a fixed 160-turn ceiling per job. Dispatch used to send it any ready ticket regardless of size, and JIO-1429, a ticket naming sixteen files, hit that ceiling one test short of done, leaving twenty files uncommitted for a day before anyone noticed. Measured across the 228 Delivery jobs run since September 14, restricted to the tickets filed since September 24 that carry a Touches list of the files they expect to change: tickets naming one to six files hit the ceiling once in 31 tries, seven to nine hit it four times in 12, and ten or more hit it nine times in 11. That last number is close enough to certain to act on. A ticket's own turn estimate can't be the signal, because the agent writes that estimate at the end of the job. So the Touches count is the signal instead. A ticket naming ten files or more no longer dispatches to Delivery at all; one naming seven to nine gets a one-time warning comment at filing time. Both are things a human can still override with a size/accepted label, and a declined ticket is labeled and mentioned in the digest rather than silently skipped, so the two ways out (split it, or accept the size) are said once where someone will actually read them.
Separately, the job that keeps a Claude login's token from expiring went blind on one account for a stretch this afternoon. It holds retries to a 20-minute floor by counting every attempt against that account, but a successful check that answered on a still-valid token without renewing anything was being counted the same as a real attempt. When two of those non-renewing successes landed inside the 30-minute window, the floor held the one retry that would have refreshed the token past its expiry, and the account went unmonitored at 18:27 UTC. Now, once a login's token has actually expired, only a failed attempt holds the floor. A success at that point can only mean the token got renewed.
The dice game signs in without a trip to the website
The iPhone app's build 5 sent players to a browser sheet on dicelockgame.com to sign in, sharing Safari's cookies and popping an iOS consent alert before it even opened. Today's fix replaces that with sign-in the app owns directly: Apple through the OS's own credential prompt, Google through a private sheet with no shared cookies, both exchanged with Clerk by the game's own server rather than proxied through the site. Getting there took clearing two separate walls. Clerk's servers reject a native sign-in attempt with a 403 unless the request carries a header identifying which registered app is asking: the one its own SDKs send automatically, which this server's manual calls weren't. And even after that was fixed, builds 5 and 6 still showed no sign-in button at all: the Account screen's check for whether the app was embedded inside another page's frame treated the iPhone app's own identifier the same as being embedded, so it drew the sentence telling players to go sign in on the website instead of a button. That's what a build-5 bug report of "it just sends me back to the site" actually was. The screen now recognizes the app as framed by nobody, same as no embedding at all, and draws its own sign-in.
Two systems got more honest about their own limits today. The pipeline that hands coding work to an unattended AI agent stopped sending it jobs too big to finish, and the dice game's iPhone app finally signs a player in without sending them out to a web page first.
The work-assigning system stops overloading itself
Part of this project runs by having an AI agent pick up a ticket (a written description of a task) and do the work unattended, inside a fixed budget of back-and-forth steps. That agent has a hard ceiling on how much it can do in one sitting, and the system used to hand it any ticket that was ready, no matter how big. One ticket that listed sixteen files to change hit that ceiling one test short of finishing, and left twenty files half-changed and uncommitted for a whole day before anyone caught it. Looking back over 228 of these automated jobs, restricted to tickets that listed which files they expected to touch: tickets naming one to six files hit the ceiling once in 31 tries, tickets naming seven to nine files hit it four times in 12, and tickets naming ten or more hit it nine times out of 11. That last number is close enough to certain to act on. So now, a ticket naming ten or more files never gets sent to the unattended agent at all, and one naming seven to nine gets a warning comment as soon as it's filed. A person can still force either one through with a label if they're confident it's really one piece of work, and a declined ticket gets flagged clearly rather than just quietly sitting there.
Separately, a different automated job (the one that keeps a login token from expiring so a monitoring account stays active) went dark on one account for part of the afternoon. It was supposed to wait at least 20 minutes between retries, counting every check against that account. But a check that succeeded without actually renewing anything (because the token it used was still valid at the time) was being counted the same as a real, useful attempt. Two of those non-renewing successes in a row meant the system thought it had already tried recently, so it skipped the one retry that would have refreshed the token before it expired, and monitoring on that account went blind starting mid-afternoon. Now, once a login has actually expired, only a real failed attempt counts toward that 20-minute wait. A success at that point can only mean the token got renewed.
The dice game signs you in without leaving the app
Until today, signing into the dice game's iPhone app meant getting sent to a browser window that opened the website, sharing your browser's saved logins and popping up a permission alert first. Now the app handles sign-in itself: Apple sign-in uses the iPhone's own built-in prompt, Google sign-in opens a private browser window with no shared logins, and the game's own server talks to the sign-in service directly instead of routing through the website. Getting there took fixing two separate problems. First, the sign-in service was rejecting the app's requests outright, because it couldn't tell they were coming from a registered app rather than a browser. That was fixed by having the server identify itself on every request the way the official app tools do automatically. Second, even after that was fixed, the app still showed no sign-in button at all for two builds in a row: a check meant to detect whether the screen was embedded inside someone else's page was mistakenly treating the iPhone app itself the same way, so instead of a sign-in button, the screen showed a sentence telling players to go sign in on the website. That explains an earlier bug report that sign-in just bounced players back to the website. It wasn't a redirect, it was a screen that never had a button on it. That check now correctly treats the app as its own thing, and the sign-in button shows up.