# Agentonomy Connect — DEV connection

DEV client downloads have not been published. No archive or checksum is offered
by this page yet. These commands are for an already installed, verified Agentonomy Connect
client that supports `opc setup`; they do not install or update a client.

DEV is a separate environment, not a promise of testnet-only funds. Check the
network, spender, amount and expiry before any wallet confirmation. Base uses
real assets. This page does not authorize signing or payment.

## Connect an existing client without replacing PROD state

```sh
(
  umask 077
  clink opc setup --agent generic --server https://dev.agentonomy.xyz --state "$HOME/.clink-dev/opc/client.json"
)
```

Use the returned secret-free MCP configuration in a dedicated DEV Agent profile,
not as a replacement for your existing production `clink_node` entry.

For an explicitly separate Codex profile, prepare its configuration instead:

```sh
(
  umask 077
  clink opc setup --agent codex --server https://dev.agentonomy.xyz --state "$HOME/.clink-dev/opc/client.json" --config "$HOME/.codex-agentonomy-dev/config.toml"
)
```

This creates an isolated configuration; it does not switch your active Agent.
Load it only in a dedicated DEV profile with your usual safety instructions.
Do not copy authentication files or replace your existing Codex configuration.

## Continue using the same DEV installation

```sh
clink opc connect --server https://dev.agentonomy.xyz --state "$HOME/.clink-dev/opc/client.json"
clink opc status --state "$HOME/.clink-dev/opc/client.json"
clink opc account --state "$HOME/.clink-dev/opc/client.json"
```

Keep this state path for recovery; do not delete it to retry an unknown outcome.
The state file is private. Do not upload it, wallet links, signatures or tokens.
Opening an authorization page is not signing, approving or making a payment.

## From authorization to your first result

On the official account page, check your wallet, the selected network, spending
purpose, limit and expiry. Follow only the steps requested for your current
account. A valid authorization does not need to be signed again just because
the platform is restarting or a service is temporarily unavailable.

Return to your Agent in the same DEV profile. For example: "Find a service for
my task, show me the price, and use my approved budget to get the result."
Purchases within your approved limits do not require a separate wallet
confirmation each time. Network support alone does not prove that your account
has the balance, authorization or service availability needed to purchase.

Ask for the purchase result, amount paid and delivery status. If the outcome is
pending or unknown, ask your Agent to check the same purchase; do not buy it again.
If payment succeeded but delivery did not, recover the result of that purchase,
not another payment. Reconnect to the same account if the connection expires.

For application integration instead of a local client, use the same DEV
environment's [MCP integration guide](/mcp/third-party/docs).