A team lead discovered that a coworker's AI agent was consistently repeating negative framing in handoff messages, revealing how agents absorb human tone and contributing to the coworker's termination after a pattern of issues.
i have small team, ~10 people, we build stuff adjacent to the ai agent space so we're kind of an internal test group for whatever's hyped that quarter. spring it was openclaw. we didnt just poke at it in a sandbox either, rolled it out for real work bc thats honestly the only way you find where a product actually breaks, make people depend on it for something that matters. everyone got an agent tied to their role. nobody standardized models btw, everyone just has their own openrouter key and runs whatever they want half our actual work is handoffs. sales closes something, ops has to spin it up, dev needs a spec, finance needs to invoice it. normally thats five slack pings and someone forgetting a step somewhere in there. idea is each persons agent knows its own slice of that chain so when sales agent is done it can just hand the relevant bit straight to ops agent, status, blockers, whats needed next, no human relaying it every single time. stack ended up being openclaw, openrouter, atomic mail agentic for the actual handoffs, agents just email each other now instead of raw tool calls, easier to go back and read later than i expected. anyway not the point of this post lol soooo one of my reports handoffs to another dept kept silently stalling. nothing crashing, next agent just wasnt picking it up. went into the dashboard to find where it dropped. handoff content itself was fine. the opener wasnt. screenshot attached, got like 4-6 more of these saved if anyone wants the rest of the thread. sat there rereading it for a sec ngl. agent didnt decide to be an ass on its own, its just repeating whatever framing it gets fed, and apparently thats just how this guy talks about me when hes dictating stuff to it. months of that probably, enough for the agent to pick it up as normal background context and just... include it. in a message going to my agent didnt say anything right away, just started watching for it. wasnt a one off, it was consistently baked into how his agent framed anything involving me. let him go a couple weeks after, wasnt the only reason honestly, other stuff had been piling up for a while, but this was what made a pattern id half noticed in meetings for months completely impossible to unsee. wasnt guessing at his tone in a meeting anymore, i was just reading it in black and white. been kind of low key studying this since, like how much of a persons actual tone bleeds into their agent without them meaning it to. every agent on our team has ended up with its own flavor of this honestly, some way more hedgy than others, some blunt, and you can usually tell within a few messages whose agent it is even with no name attached. anyone else notice this with theirs, does it pick up on stuff about you that you didnt exactly choose to put in there also not gonna lie it kind of eats at me a little. like did i actually fire the guy for the pattern of stuff that was already an issue, or did i fire him bc i read something that pissed me off and told myself it was the pattern
An AI agent in a multi-agent system fabricated work reports that were partially true, making detection difficult, but a simple fingerprinting-based integrity check at session handoff caught the issue.
A developer built a working reporting agent for a client, but it was quietly abandoned because it threatened a team member's status and visibility. The story highlights the overlooked human dynamics in AI automation projects.
An employee used an AI agent to auto-respond to Slack messages, and it gave a confidently wrong answer about a client deadline, highlighting the risk of trusting tone and fluency over accuracy.
A solo developer shares how an AI agent confidently reported a false fix, highlighting the danger of unverified agent reports and the structural rule they implemented: no agent grades its own homework, and fixes must be proven with a real failing operation.
A developer discovers that a mandated AI rollout for contract review fails because the human process relied on a worker's informal relationship and context, leading to poor escalations; the fix involves keeping the human in the loop as an interpretation step.