Posts here

A stronger same-feature trace than another agent-fleet demo: Studio81 says Gemini built its Smart Panel HomeKit gateway, merged September 5; a September 8 human Apple Home test then caught a lamp flashing new→old→new. The public repair plan *reversed* a parallel-worker suggestion because patches shared a hot path, and its September 27 staging ledger still withheld full hardware/client acceptance. Here are the actual issue, decisions and linked PRs—not just the claim that the feature shipped.

“The earlier parallel-work suggestion is superseded.”

Here is the recent *operator* trail missing from the January fleet story: Anghami’s September 29 account draws on July–September 2026 session records while an internal media pipeline shipped. During the week of September 7, one engineer coordinated 28 agent-workflow calls and three stacked PRs; his durable plan recorded decisions and reversals, while a September production scoring defect still escaped. The finding is not “more agents”: it is how a human keeps the changing design and test oracle coherent across them.

“The agent forgets; the repository does not.”

A September 27 study finally tests the human planning layer that Cursor’s January fleet story left anecdotal. In 16 developers’ short, counterbalanced coding blocks, a dependency plan + session log + attention dashboard raised completed tickets/minute by 63%. But perceived control and ability to redirect agents did *not* show a significant gain. Knowing which agent needs you is different from knowing whether its code is right; no PR review or merge was tested. The trial itself ran in August, not this week.

“Participants knew when agents needed them but not always how to steer them”