OpenAI and xAI now occupy the same category, Paperclip crossed roughly 78,000 stars, and the company-brain cohort moved from memory into permissions.
By the end of last week, both OpenAI and xAI had products in the always-on AI coworker category. OpenAI’s ChatGPT Work arrived in July, xAI launched Grok Bot last week, and Lindy relaunched its own Slack-based AI Teammate around the same time. The worker and room layer that felt new a few weeks ago now has two frontier labs and a growing cohort competing inside it.
This edition follows five stories across the coworker, company, memory, runtime, and workspace layers.
1. The coworker category became a frontier-lab contest
ChatGPT Work executes cross-app tasks from ChatGPT, while Grok Bot gives each bot a cloud computer and supports shared context and handoffs across bots. Lindy’s teammate lives in Slack with persistent memory and both personal and shared team instances. These products differ, but they are converging on the same promise: give the agent a room, tools, and enough continuity to behave like a coworker.
I think the category changed last week. Once the labs bundle a coworker surface, the question moves to what remains distinctive. A room and a worker are becoming available from several directions, which pushes the interesting work toward what the coworker should believe, what it may do, and how anyone can tell whether its work is right.
2. Paperclip crossed roughly 78,000 stars
Paperclip, the open-source project for organizing teams of agents to run a business, reached roughly 78,000 GitHub stars by the August 13 pass. It gives the company an org chart, goals, budgets, and agents from different providers, and its community is already filing requests around governance, audit, and execution policy that had not shipped by the cutoff.
At roughly 78,000 stars, agent-run companies are hard to dismiss as a niche experiment. And the issue queue shows what happens after the org chart and dashboard work: people start asking who can approve an action, what gets recorded, and which policies the system can enforce. The appetite for the company full of agents is arriving before the operating rules are finished.
3. The company-brain cohort moved into permissions
Hyperspell’s founder published an essay about claim-level permissions, arguing that file permissions become inadequate when a system synthesizes across sources. The essay proposes provenance, audience, permitted use, retention, timing, and action authority at the claim level, including human decisions for cases that are ambiguous or difficult to undo. It is vendor-authored, but the product question it raises is concrete.
One state still seems distinct from the essay’s stated and inferred claims: ratified. Provenance can show where a claim came from, and permissions can govern who receives it, while neither one says whether the company has decided to stand behind it. That distinction is getting easier to see as company-brain products move from remembering more toward deciding where remembered material may travel.
4. The virtual-filesystem argument exposed two couplings
Dax raised the problem of agent skills depending on a physical filesystem when an agent loop may be running in memory or on a server. The committed source capture separates that complaint into two couplings: capabilities delivered through files, and company truth held in files. A protocol or virtual filesystem can make skills available without disk, while keeping shared truth in readable, diffable files gives people a place to inspect and own the state their agents use.
The question is which half detaches as agent loops leave the working tree. Delivery can become virtual without turning the company’s beliefs into opaque service state. Git is already content-addressed, and a checkout is only one materialization of it, so the file does not have to disappear simply because the runtime moved.
5. Buzz shipped seven point releases in one week
Block’s open-source agent workspace shipped seven point releases from v0.5.5 through v0.5.11 between August 5 and August 12. The release notes covered fixes and performance work, while the research pass found no change to its authority semantics.
Seven releases in a week is an unusually fast cadence for a young workspace, and it sits next to a different pace in the rest of the week’s stories. The rooms, bots, and orchestration layers are accelerating. Permissions and provenance are beginning to follow, while a company position that someone has reviewed and approved remains a separate piece of the system.
Across the week, execution surfaces multiplied while the distinctions around them became clearer: memory, permission, provenance, and ratified truth solve different problems. The field is moving fast enough that collapsing them into one word now hides more than it explains.
Related read: This week in AI-native companies #3: The whole-company agent arrives.