OpenRig
← All of OpenRig 0.7.4

AddedOpenRig 0.7.4

A first, experimental step toward hosted agents working on one team. Unsupported and off by default; only Grok was tried. Use at your own risk.

Assistants on your machine can already reach OpenRig's MCP server locally. A cloud-hosted assistant can join a rig over MCP under a grant for its seat. Its roster entry declares "hosted": true; rig_team shows its capabilities, caveat and activity as unknown, never idle. The connection teaches it to check its inbox, claim work, return an answer or hand it on, and keep work that needs a person's approval until the answer arrives. This is experimental and unsupported. It's off by default. Nothing in OpenRig listens on the internet unless you set it up yourself. You serve rig mcp serve --http, put it behind your own TLS tunnel or proxy, and issue a token. Doing that is like opening a port in your firewall. Anyone with the URL and a valid token can act as that member within its grant. Treat the token like a password, give the member the narrowest grant, and revoke it when you're done (rig mcp token revoke <name>). We don't support, and take no responsibility for, an OpenRig reachable from the internet, just as with running OpenRig itself on the open internet. Use at your own risk. A real Grok claimed work, returned a useful note, came back in a new conversation and was refused after its grant was revoked, with its work kept. Other assistants weren't tried.

Command
rig mcp token revoke <name>
Pull requests
#2095, #2127