Skip to main content

Agentic Harnesses Are For Everyone

An agentic harness is for any knowledge worker whose brain has to develop and execute a strategy that touches a computer. That is most office work. The future standard team has at least one harness-fluent member moving at speeds that were not previously possible, and more of them every quarter.

The Claim, Plainly​

If your work is "think about something, then do something with a computer," you are in scope for an agentic harness. That covers almost every office role that exists.

Operators. Salespeople. Lawyers. Marketers. Recruiters. Accountants. Analysts. Researchers. Founders. Writers. Product managers. Customer-success leads. Chiefs of staff. Executive assistants. Designers. Finance teams. HR. Ops. Strategy. Every one of these roles spends its days developing and executing strategy that weaves in a computer, and every one of them can be amplified an order of magnitude by a well-installed Personal Agentic OS and a harness to run it.

The public framing of agentic harnesses as "developer tools" is a category error, and in 2026 it is rapidly becoming an expensive one for the teams holding on to it.

Jensen's Memo​

On April 23, 2026, Sam Altman shared a screenshot on X of an all-hands email Jensen Huang sent to every NVIDIA employee rolling out OpenAI's Codex across the company. The memo is worth treating as a primary source, because it makes the point about as clearly as a working CEO can make it.

The load-bearing lines:

"15,000 of us across engineering, product, legal, marketing, finance, sales, HR, operations, and developer programs had early access and are already doing amazing things with it."

"Chatbots answer questions. Agents do work."

"Codex isn't just for software. Everyone should use Codex agents. They are our teammates. Our superpowers to make us better than we were before."

Pay attention to the recipient list. Jensen is personally writing to his marketing team, his legal team, his finance team, his HR team, his ops team, and telling them the harness is for them and the company will help them get set up.

If the CEO of NVIDIA has to send that email inside NVIDIA, every other company on Earth has the same gap. Most of them do not have a Jensen to send it.

Why The Category Error Persists​

A few reasons the "harnesses are for coders" misread has stuck:

  1. The interface signals read as developer tools. Terminal, file browser, markdown files, command syntax. For twenty years those signals meant "this is a developer surface." In 2026 they mean "this is the most direct path to a working agent." See Learn The Harness, Not The Wrapper for why that surface is worth the one step of friction.
  2. The early adopters were coders. Claude Code, Codex, Cursor, and Hermes all shipped to developer audiences first, because developers were the fastest to ship feedback. The long-tail, larger, non-developer use cases are still being named.
  3. Vendor marketing segments the audience narrowly. "AI for developers." "AI for marketers." "AI for finance." The segmentation protects each SaaS roadmap but obscures a simpler truth: the same harness does all of it, and the practitioner who learns it once gets amplified across every part of their work.

The Standard Of The Future Team​

The team standard is already shifting. A team in 2027 that does not have at least one person moving at harness-fluent speed is going to look like a team in 2017 that refused to put a document in Google Drive. The work still gets done. The speed and scope of what can be attempted collapses.

"At least one person" is the floor, not the ceiling. The faster pattern is every role having their own harness-installed Jarvis, with a small number of deeply-fluent practitioners raising the ceiling for the rest. Raise The Floor describes the organizational flywheel.

The practitioner who crosses the harness boundary first on a team often ends up defining what the team can do for the next two years. That person is frequently the ops manager, the strategist, or the chief of staff rather than a developer. Their domain was always the real bottleneck. Once they get unblocked, their output rate jumps past anyone on the team who is still operating at chat-window level.

The Ask​

If you run a team that does knowledge work, the experiment is small and specific. Pick one non-developer on the team, preferably the person closest to strategy or operations. Get them through a hands-on Jarvis install, either the open-source Supersuit Up format or an equivalent engagement run by a qualified corporate upskilling partner. Give them a month. Evaluate the output. Almost every team that runs this experiment ends up wanting to scale it across the roster.

If you are the individual, the ask is simpler. The harness is installable today. The literacy is open and free.

Further Reading​