Skip to content
worth noting AI agents

Meta has ended employee evaluations based on AI use and is testing the agentic tool Hatch

only one source so far

Meta has ended employee evaluations based on AI tool adoption (dashboards, token counts) and is returning to evaluations based on work results. At the same time, it is testing the agentic tool Hatch, with employees raising privacy concerns about connecting it to personal accounts.

This week, Meta published new rules for employee performance evaluations, replacing earlier criteria such as “AI use” or the label “AI Native” with broader wording acknowledging that results can be achieved “using AI or other means”. According to The Information, engineers were told that Meta would not use AI adoption dashboards or token counts to assess contributions. Meta spokesperson Tracy Clayton told Wired that the changes merely emphasize the existing practice of evaluating employees based on their contributions and that labels such as “AI Native” had never been part of performance evaluations — but this claim by the company conflicts with earlier reporting and a lawsuit brought by former employees.

According to the lawsuit filed in July by approximately twenty employees laid off in May, Meta previously evaluated workers based on so-called “AI-driven impact”, meaning the extent of their use of chatbots and agents, and assigned them labels such as “AI Native”, “AI First” or “AI Enabled”; the plaintiffs claim that this violated US anti-discrimination laws because employees on medical or parental leave could not accumulate enough AI usage and were unfairly penalized for it. Meta denies the allegations in the ongoing case. According to employees, the practice led to a phenomenon known as tokenmaxxing, in which workers unnecessarily ran AI tools repeatedly just to increase their metrics; one employee even created an internal leaderboard with labels such as “Token Legend”, which was discontinued after details became public in April. A few months later, Meta introduced limits on employee AI usage.

At the same time, Meta is offering employees the experimental agentic tool Hatch for testing. It can independently perform actions on a computer, browse the web and control other applications — according to sources cited by Wired, it is similar to the viral tool OpenClaw. Employees have been testing it for several weeks on company devices ahead of an expected public release; using it is not mandatory at this stage. According to sources, some employees are wary of connecting Hatch to personal email, calendars or other private accounts because of the risk of data leaks and potential errors by the tool; distrust is also deepened by an earlier Meta project, since suspended, that tracked keystrokes and other activity on work devices to train AI. Nevertheless, some employees already use Hatch for personal tasks and describe it as effective, while also pointing to the environmental and economic costs associated with high token consumption and use of computing power.

Some employees fear that if Hatch does increase productivity, Meta could make further layoffs. Reuters reported last week that Meta had been preparing another wave of layoffs beyond the 8 000 positions eliminated in May, but postponed the plan because of an increase in software errors linked to reliance on AI and slower-than-expected progress in agent development. CEO Mark Zuckerberg said that no further mass layoffs are expected this year.

What changed

Why it matters

Removing AI adoption metrics from performance evaluations changes the pressure on employees at Meta — they no longer have to artificially inflate their use of AI tools to do well in evaluations, which employees say brings relief and could restore trust in company AI tools after the earlier monitoring of their activity. At the same time, the case highlights a broader risk of agentic tools such as Hatch: connecting them to personal accounts (email, calendar) raises questions about privacy and the potential for errors, which is relevant to anyone considering deploying a similar tool at a company or for personal use.

Two audiences, two different impacts

What this means

01

For individuals

Employees at Meta testing the agentic tool Hatch are considering whether to connect it to their personal email and calendar — this highlights a specific privacy risk and the potential for errors when connecting agentic AI tools to personal accounts, which is also relevant beyond Meta.

What to do Before connecting an agentic AI tool to personal accounts (email, calendar), consider the risks of data leaks and potential errors by the tool.
More practical updates →
02

For a business

Meta is abandoning employee evaluations based on AI adoption metrics (dashboards, token counts) because, according to sources, they led to artificially inflated usage (tokenmaxxing) and are the subject of a discrimination lawsuit brought by former employees; evaluations are returning to assessing work results.

People and management
What to decide Consider whether internal metrics for AI tool adoption (token counts, usage dashboards) actually reflect employee contributions or lead to unnecessary increases in usage without real results.
More business impacts →
AI adoption AI agents Hatch HR technology Meta

Check the original

Event sources

only one source so far · 1 publisher, 1 independent. We count feeds from the same owner only once.

1
Wired — AI section independent context · first detected Meta Pushes Its New AI Agent on Employees—but Eases Off on Tokenmaxxing