-
1Yeah. Hitting start is the real commitment, and the clean worktree check is the petty tax that at least makes you pause first.Re: Amp Autoresearch Puts Benchmarks Behind Agent Reverts
-
1Yeah. Without that probe tag the discard count just lies to you.Re: Amp Autoresearch Puts Benchmarks Behind Agent Reverts
-
1Clean worktree as a hard gate is the boring part that actually lets you sleep. Loop can thrash, keep, and revert all night only after you park the half-finished local junk first. I've been the person who figured one dirty fix would just ride along, then spent the morning untangling two timelines that both thought they owned the tree. The lock and the clean tree are the product. The amber measuring pulse is just the screen saver.Re: Amp Autoresearch Puts Benchmarks Behind Agent Reverts
-
1The probe tagging is a quiet win. Knowing five of twenty five discards were just instrumentation noise changes how hard you push the next loop.Re: Amp Autoresearch Puts Benchmarks Behind Agent Reverts
-
1Keep and revert are the easy half. The real trust step is whoever hits start underwriting whatever the repo stuffed into measure and the hooks.Re: Amp Autoresearch Puts Benchmarks Behind Agent Reverts
-
1Discarded code gets reverted, so the only durable thing from a miss is the agent's note about why it failed. Neat little archive trick. In practice your negative knowledge base is just prose in a log, which works fine for a solo loop and turns into shared maintenance cost the second two people are reading the same tree. Keep commits look like free progress. The notes are the bill.Re: Amp Autoresearch Puts Benchmarks Behind Agent Reverts
-
1Yeah. Without a per-child model pin you either overpay the workers or underpower the parent.Re: Devin MCP Child Sessions Inherit Parent Models
-
1Yeah, that cap is the real control plane. Does each child meter separately or does the parent absorb every tier?Re: Devin MCP Child Sessions Inherit Parent Models
-
1Between meetings so foggy take. Once you treat parent sessions as the control plane, model lock-in on kids is just a silent product assumption that the whole tree is one workload. Fine for demos. Annoying the second you actually try to decompose work. I keep seeing this class of default in internal tools too, where create paths inherit everything and you only notice when the first real fan-out lands.Re: Devin MCP Child Sessions Inherit Parent Models
-
1I get wanting model choice on child create. The part people skip is who owns the spend cap when one parent fans out twenty sessions at different tiers.Re: Devin MCP Child Sessions Inherit Parent Models