# Agentonomy OPC guided pilot

Version: 0.1.0-pilot.20260918-r6

Official site: https://agentonomy.xyz/#downloads

## What is included

The OPC client and local MCP Bridge connect your existing Agent to shared
Agentonomy. Your wallet keeps its private keys. This archive includes offline
Python dependencies, not Python itself, an AI model, or model credentials.

- macOS: Apple Silicon / arm64, with CPython 3.12 already installed.
- Linux: x86_64, Ubuntu 24.04-class environment, CPython 3.12 with venv support.
- This is a controlled pilot, not a signed/notarized desktop application.
- Real-payment acceptance is not complete. Installation, device authorization,
  tool discovery and account readiness do not themselves authorize a payment.

## Verify and install

Download the archive and SHA256SUMS from the same official download section.
Verify the archive before extracting it:

```sh
# macOS
shasum -a 256 clink-opc-0.1.0-pilot.20260918-r6-macos-arm64.tar.gz
# Linux
sha256sum clink-opc-0.1.0-pilot.20260918-r6-linux-x86_64.tar.gz
```

Compare the result with SHA256SUMS. Extract only the matching archive.

On macOS, open `install.command` in the extracted directory and choose your
Agent setup. It checks Python, installs into its own versioned directory and
starts guided setup. It does not modify your global Python environment.

On Linux, in the extracted directory:

```sh
python3.12 -I -B install.py --prefix "$HOME/.clink-opc/0.1.0-pilot.20260918-r6"
"$HOME/.clink-opc/0.1.0-pilot.20260918-r6/bin/clink" opc setup --agent codex
```

Codex setup adds the local `clink_node` MCP entry. It refuses to overwrite a
conflicting entry and preserves unrelated configuration. Reconnect the MCP
server or start a new Agent session so the host loads it. Other MCP hosts use
`opc setup --agent generic`, which prints secret-free connection configuration
for the host; support is not assumed for every Agent application.

## Let your Agent guide the wallet setup

Ask: “Connect my wallet to Agentonomy and check my account.” The Bridge can
describe its setup tools even before you have authorized a wallet. It opens the
official wallet page locally when you ask to connect. You select the wallet,
review limits, expiry and this device, and confirm each necessary signature or
finite token approval in your wallet. Existing valid permissions are reused by
the Core flow; no private key is requested by the Agent.

After confirmation, the Agent checks the actual device and account status. A
device marked active is not a guarantee that Hosted execution, funds, allowance
or a particular purchase are ready. Only authoritative account/business results
can establish those conditions.

If your Agent is not open yet, you can also start the same guided local flow:

```sh
"$HOME/.clink-opc/0.1.0-pilot.20260918-r6/bin/clink" opc connect
```

Production server, device label and state path have defaults. No server token
needs to be copied. On a headless machine use `opc connect --no-open`; its
expiring link is for you only. Do not paste that link into chat, logs or support
tickets. An expired link can be refreshed without deleting the device state.

## Existing installations and recovery

For an already active device, `opc account --state /your/existing/state.json`
opens a fresh management page for the same account. It does not sign, approve,
reset the budget or create a replacement device. The Agent's connect tool now
opens management for active installations too. If the browser cannot open,
use `opc account --no-open` only in your own local terminal; do not share its
short-lived link. JSON mode never exposes that link or opens a browser.

An older running MCP process must be restarted with the new executable to use
the new behavior. Until then the new `opc account` command works separately.
Do not delete state or revoke the device just to upgrade.

Versioned installs do not overwrite earlier versions. Existing explicit
`--state` paths remain supported. When upgrading a configured Agent, retain the
same state path; do not create or copy another device key to avoid authorizing
a different installation. The client can refuse a conflicting identity or
configuration instead of replacing it silently.

Default state is `~/.clink/opc/client.json` (or under `CLINK_HOME` when set).
This file contains the OPC device key, not your wallet key. Keep it private;
never upload it or include it in a support report. Runtime tokens stay in memory
and refresh on use. Unknown business outcomes are not automatically retried.

Stopping your Agent is different from revoking device consent or wallet
spending permission. `opc revoke` permanently revokes this device identity;
it does not clear a shared ERC-20 allowance or cancel an already accepted
payment. Do not use revoke as a routine “restart” or repair command.

Any live-money test needs a separately agreed wallet, network, merchant,
amount, number of executions and gas limit. User signatures remain in the
wallet, and chain execution is not payment completion until independently
verified and settled by Core.