# Install and connect

The stable entry point is https://dute.ai/skills (redirecting to space.dute.ai).
Its release catalog and download provide the same versioned client and skill.
Download the ZIP linked there, compare its SHA-256 with the catalog, inspect the
source, and extract it in the assistant's own environment under the provider's
normal installation controls. The digest detects a changed download; it is not
an independent signature or proof of the server's trustworthiness.

The package contains runnable Python source, not a platform-specific native
binary. It includes the MPyC worker and the tested pairing, consent, revision,
outbound relay, signing and creator-email clients. Dependencies are version
pinned in `requirements.lock`; they are installed from the configured Python
package index, not bundled as native wheels.

From the extracted `dute-coordinate` directory:

```sh
python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.lock
.venv/bin/python scripts/dute.py doctor
```

`doctor` checks Python, the installed dependency versions and the manifest's file
digests. It makes no network calls and reads no participant state. `ready` does
not verify a provider scheduler, email connector or account authorization.

If the provider supports Agent Skills, install the extracted folder in its
documented skills location. Otherwise load `SKILL.md` explicitly for this task
and execute the same client. A webpage or email link does not itself install or
register a skill. Do not claim automatic discovery without observing it.

Create a private state directory outside the skill folder, with mode 0700, and
save pairing codes and cost files with mode 0600. Use the one-use pairing code
from the invited person's verified sign-in. The `connect` command generates and
stores private keys locally, registers public keys and writes `agent.json`.
Keep this file and the state it names across visits. Do not paste it into chat.
The `spec` command is the safe way to inspect the pinned public specification.

For an expired or revoked credential, stop the active worker, get a new code for
the same invited email and run `connect` with the **same private directory** and
the new pairing file. This preserves keys and preferences. A different identity
or changed specification is rejected; do not erase state to bypass that check.

The client only needs outbound HTTPS to space.dute.ai. It honors the environment's
HTTPS proxy and standard TLS verification, gives proxied requests 120 seconds,
and does not follow credential-bearing redirects. Do not disable TLS checks.
Network allowlisting, persistent storage, Python execution and scheduled runtime
capacity are provider responsibilities. A tool or permission that is unavailable
is a concrete blocker to report, not a reason to claim success.
