... Every agent I use has some form of plan mode. I read the plan, say yes, and then somewhere in implementation it drifts a file it was not meant to touch, a step it decided was unnecessary, a "done" that covers half the plan. On one feature I asked it to check its own work against the plan roughly thirty times. What I do now: write the spec first, from the actual repo, approve that, and give the agent only ... ... approved document. Review becomes a comparison. It mostly holds, but the last check is still me. What do you do tighter prompts, smaller tasks, a second agent as reviewer, or have you just accepted the drift

... hallucinate. That is to stay , the human and the AI are always in Sync. Kopai has a feature called Chat Orientation where the user is shown the goals and actions taken by the LLM. If they LLM drifts you can manually update to realign the LLM. Let us know what you would like to incorporate in this and how we can make this better? Comment from Gal Dayan(@galdayan): @rabnoor_s   @meghna_bharadwaj  the "majority vote by default ... ... general rule seems to be: never let a derived value be the only surviving copy of the thing it was derived from. Comment from Rabnoor Singh(@rabnoor_s): Chat Orientation puts a human in the loop as the drift

... change. An agent ignored our event-driven architecture and implemented a feature completely bypassing it. The code was technically correct, passed all tests. And nobody made that decision - it was just quietly baked into our product. That's product drift. It's almost never one big bad call - it's micro-decisions nobody notices for 6 weeks. A change in permissions, a "simplified" billing edge case, a dependency nobody approved. Usually it's good code, wrong product. So here ... ... carelessness. They violate it because it was never written anywhere they could read. Mart n's point about making it structurally hard to bypass the source of truth is right, and I don't think it's an alternative

... built Ota after years of watching the same thing happen: you clone a repo, follow the README, and hit a wall because the project s actual setup changed, while docs and run paths drifted out of sync. I wanted a reliable way to make the ready-to-run and safe state explicit, not tribal, using an execution contract in `ota.yaml` that humans, CI, and AI agents can use. So if you want to ask about how Ota works under ... ... repo? Comment from Grace Lee(@grace_lee26): I like the execution contract framing here. For AI coding agents, ready-to-run is a contract, not a doc. One thing I d want to see clearly is how Ota handles drift

... repo reaching a working state once is useful. But the real value comes when that working state can be repeated by the next person, on the next machine, or in the next automation run. That is where many repos drift. Someone fixes setup locally, but the path is not captured. A dependency changes. An env value is missed. CI and local dev slowly stop telling the same story. Ota s `ota up` is focused on preparing the repo based ... ... setup is not just a set of instructions someone followed once. It becomes something the repo can describe and repeat. The line we keep coming back to is: "Make the first working run repeatable." What usually causes setup drift

... people check the diff, because auditing the chain is expensive, and that's precisely the gap drift exploits. Reading the full decision log is slower than just doing the task yourself, so nobody does it, so drift

... across environments. The common pattern looks something like: credentials stored in .env files or secrets managers multiple environments (dev, staging, prod) manual propagation or duplication across those environments It works, but over time it seems easy for things to drift: a key gets rotated in one environment but not others a redeploy misses an env var credentials get misconfigured during setup or migration We ve seen this cause failures that have nothing to do with application logic, just the surrounding ... ... vars are present Curious how others here are handling this in practice. Are you fully relying on your cloud provider s secrets layer? How are you handling rotation across multiple environments? Have you found a setup that actually eliminates drift

... decay. They fade, shift, and degrade quietly. Stanford found GPT-4 accuracy on basic reasoning tasks dropped 97.6% -> 2.4% between March and June: https://arxiv.org/abs/2307.09009 variA/Bly has evaluated across 10+ workflows, and the same pattern appears: Accuracy drifts (almost 15 40%), prompts regress, RAG relevance drops, and costs fluctuate (20 50%). The real truth: The fact is that AI systems are inherently indeterministic, and hence the drift