A half-day build stitched together by leaving state in the repository
This traces how someone who thought they had used up all their available usage found a route still open and finished a 3D racing game in half a day. The gist is the observation that, in the usual chat window, turning reasoning effort all the way up brings up the top model as an option, and that usage through this route is counted separately from the coding-only tool. The way of working is more worth taking away: with the code repository serving as a state store outside the agent, and the agent picking up from whatever results were left rather than being asked afresh each time, the work never went back to square one even when the chat window changed, and it took the shape of about ten large units, each a single handoff that ran on autonomously for over an hour. The finishing touches were handled by remotely controlling the command-line tool on an always-on laptop through an external messenger bot, with approval given only at points needing a human hand, such as installs and sign-ups. However, the figures are all observations from one account, and the risk of a setup in which an external messenger becomes the entry point for execution privileges goes unmentioned.
Key points
- Uses the code repository as a state store so work continues even when the model changes
- Repeats ten times a unit in which one request runs autonomously for over an hour
- A human steps in only at approval points such as installs and sign-ups
- Separate usage counting and per-plan limits both rest on one account, so remain unconfirmed
This is a note: my own write-up after reading several sources. It has no source link; events checked against a source are kept as records.