Sovereign Fleet is learning to do work that is not code. The feature is called Privateer, after ships that sailed with a written, limited commission and had to prove every prize in court. What the name commits the software to, what exists today, and what is only planned.

A Letter of Marque for an Agent: Why the Fleet's New Feature Is Called Privateer

Sovereign Fleet lets coding agents work inside a kernel sandbox and lands their commit only when a gate is green. It is now learning to do work that is not code: read pages, pull numbers from an interface, write a report. The application keeps its name. The new feature needed one, and “bot” says nothing about what makes it different.

It is called Privateer.

The commission and the court

For centuries, until the Declaration of Paris ended the practice in 1856, a naval power did not build and crew every ship itself. It commissioned private ones. Two institutions made that something other than piracy.

The first was the letter of marque: a written commission from the sovereign that named what the ship was allowed to do, where, and for how long. A captain who sailed without one, or outside its terms, was a pirate under the law of every nation.

The second is the half people forget. A privateer did not own what it brought home on the captain’s word. It had to bring the prize into port, hand over the ship’s papers, and prove before a prize court that everything had happened within the commission. Only the court’s decision made the result count.

I am not interested in the plunder. I am interested in those two institutions, because they are the two things an autonomous agent needs and usually lacks: a permission that is written down and limited, and a judge who is not the captain.

What the name commits the software to

In the storyIn Sovereign Fleet
The sovereignyou, the operator: your machine, your keys, your data, the last word
The privateeran agent with a third-party tool, sent out on one job
The letter of marquethe job’s commission: which tool, which domains, how many calls, how much memory, enforced by the kernel and a proxy
The ship’s loga hash-chained record of every tool call and a record of every network request, both written where the agent cannot reach
The prize courta gate that decides from those records and a schema, never from the agent’s own account

The point of the picture is where each thing lives. In Sovereign Fleet, a letter of marque refers to a per-task capability contract enforced outside the model, because kernel filters and egress proxies hold even when a prompt fails. A prize court is defined as a verification gate that accepts or rejects from append-only call logs, response bodies, and egress logs rather than self-reports.

The commission is not a paragraph in a prompt. When an agent or its tool reaches for a domain off its list, a unix socket or another local port, the kernel and the proxy refuse before a packet leaves the machine. For example, in Experiment E4 the confined browser completed three calls in 13 seconds inside its sandbox limit (3 GB in E4, tuned to 1 GB for daily use after the C1 memory benchmark) with 0.37 ms median gate overhead, and refused an off-list host before a packet left the machine. The court does not ask the agent how it went. In an early experiment a local model’s browser tool failed, and the model fetched the page another way, wrote the correct answer and once reported plain success. The answer was right and the route was forbidden, because a proxy log captures routes the agent omitted. A court that reads the log sees that. A court that reads the report does not.

So the guiding sentence is short:

A Privateer sails with a letter of marque: confined by the kernel, checked at the gate, signed on return.

And the claim beside the fleet’s coding one (“Let them code. Make them prove it. Ship your ideas.”):

Send them out. Make them prove it. Sign what counts.

Rules that follow

Some of this is built and some is planned. I mark which.

Where this sits next to the agents you can buy

I have not used either vendor product. Their columns come from their official documentation and pricing pages read on 2026-11-16, and plan details change fast. The fleet column is the state of today, gaps included.

Grok BotClaude CoworkSovereign Fleet with Privateer
Where the work runsits own cloud computer at the vendor, on while you are awayClaude Desktop on folders you pick (plus cloud scheduled tasks on Anthropic servers)your own machine, one kernel sandbox per job
Modelthe vendor’sthe vendor’slocal first, a paid model only where you allow it
Your apps and loginssigns in to your tools on the cloud computer (with Vault and Secure Forms)connectors to external apps and toolsno account connectors yet; confined browser and fetch capabilities for reading
Recurring workroutines on a schedule or an eventscheduled tasksnot built
What stops a wrong actionAuto Review permission modes, including Always allowpermission modes (Manual, Auto, or Skip)rules outside the model: kernel sandbox, default deny per tool, call budget, domain list, non-empty effects, and hash-bound draft capture (phone Nostr signature planned)
How you know the result is rightthe bot reportsthe assistant reportsa gate decides from records the agent cannot write (hash-chained call logs, response bodies, egress logs, and schema checks)
Where your data goesto the vendorto the vendor’s modelnowhere, as long as the job stays on the local model
Costpart of The X Subscription (Premium from 30 USD/month)paid plans (Pro from 20 USD/month, 17 USD/month billed annually)hardware and power
Using itmobile and web appdesktop, web, and mobile appchat message, issue or MCP call, CLI (fleet draft) and dashboard
Sourceclosedclosedopen
Strongest pointworks across apps today, without your computerlowest entry, strong model, many connectorslimits and proof that do not depend on the model, for any agent
Weakest pointyour sessions live on someone else’s computerthe same model does the work and reports on itdoes far less today, and you run it yourself

Privateer does not replace either of them. An assistant can sit in front, talk, remember and hand over the job. What the fleet adds is the commission and the court, on your own machine, for whichever agent does the work.

What exists today

The foundation exists and is tested as of November 2026 (1354 passing tests): third-party tool servers (browser under a 1 GB memory limit and a confined fetch capability under 512 MB with a shared provenance cache) inside kernel sandboxes, one gate in front of them, two-phase draft capture capped at 5 drafts and 24 hours (with phone Nostr signature planned), hash-chained call and response body logs the agent cannot touch, and a native evidence check that verifies results and recognises an honest “could not”. How it is built, what broke on the way and what is still open is in the engineering article, and the feature status overview is on the Sovereign Fleet page.

What does not exist yet: scheduled routines, service logins, and a full run of real daily days on a live job. The first one will be the wind and snow report for my home region. When it has run for a few real days, with a record of forecast against reality, the numbers go here.

Was this worth it? Zap the article.

Value for value, no signup. Sats go straight to the writer.

… sats zapped
… zaps
Today 7d 30d All-time
Unique readers — — — —
Page views — — — —
—
All Article Insights →