Meta's push into agentic AI is taking sharper shape. Following reports from FT and The Information that the company is building a consumer-grade autonomous agent codenamed Hatch, fresh signals inside Meta's own surfaces confirm that preparation work is already underway in the codebase. The agent appears positioned as Meta's answer to OpenAI's OpenClaw, reframed for a mainstream audience that the current crop of agentic tools has largely shut out.
Traces in the code suggest Hatch will roll out behind a waitlist, meaning early access is likely to be tightly gated at launch. The scope of tasks being prepared is notably wide:
- Image and video generation
- Shopping flows
- Learning sessions and research workloads
- Groundwork for scheduled tasks and file generation
That feature mix overlaps with Microsoft's Copilot Tasks and its Auto, Researcher, and Analyst modes, but Meta's version carries a clear twist. The agent is expected to draw on social grounding, reaching deeper into Instagram and Facebook than any Meta AI surface so far, and potentially turning feed exploration, creator discovery, and shopping research into agent-driven workflows.
The strategic logic lines up with what Mark Zuckerberg outlined on Meta's most recent earnings call, where he framed the company's agent ambitions as systems that work day and night toward user goals. According to The Information, Meta is targeting internal testing of Hatch by the end of June, with mock environments built to resemble Reddit, Etsy, and DoorDash for training in tool use behavior. The Financial Times points to Muse Spark, Meta's new assistant-tier model family, as the eventual backbone, with Anthropic's Claude Opus 4.6 and Sonnet 4.6 reportedly serving as a transitional layer in the meantime.
Hatch also sits alongside a parallel agentic shopping tool being prepared for Instagram, targeted for Q4 2026, that would let users research and check out products without leaving Reels or the feed. Together, they sketch a clear posture: Meta wants its agents to live where billions of users already spend their time, rather than asking them to migrate to a separate chat surface. Whether the Hatch codename survives to launch remains open, but the build cadence suggests it sits closer to release than early reporting alone implies.
