Install. Pair.
Run your first session.

Before you start

You need macOS or Linux, a supported coding agent installed and authenticated, and access to your team in the Misconfig console. Installation needs curl, tar and the platform checksum utility. No Go compiler or source checkout is required.

Start with Codex for the live-tested path. The release contains a Claude adapter, but authenticated Claude live acceptance remains open. Check the release compatibility file before using another client version.

Step 1

Install the runtime

Not sure? Run uname -m. Apple silicon reports arm64; Intel/AMD reports x86_64. Linux ARM may report aarch64.

(
  set -eu
  install_dir="$(mktemp -d)"
  cd "$install_dir"
  curl --fail --location --proto '=https' --tlsv1.2 \
    --output misconfig_0.1.10_darwin_arm64.tar.gz \
    https://github.com/misconfig-cloud/agent-runtime/releases/download/v0.1.10/misconfig_0.1.10_darwin_arm64.tar.gz
  printf '%s  %s\n' 'f370ef9be79ebb11f0aa1a46111ae8bebc9f4004836418bb5551f7bb148b6d8f' 'misconfig_0.1.10_darwin_arm64.tar.gz' | shasum -a 256 -c -
  tar -xzf misconfig_0.1.10_darwin_arm64.tar.gz
  ./install.sh --prefix "$HOME/.local" --require-version 0.1.10
  printf 'Installer files: %s\n' "$install_dir"
)

This downloads v0.1.10, checks its pinned SHA-256 checksum, and installs to ~/.local/bin. It does not use sudo or change your shell configuration. Stop if verification fails.

gh attestation verify misconfig_0.1.10_darwin_arm64.tar.gz -R misconfig-cloud/agent-runtime

Make the command available in this terminal

export PATH="$HOME/.local/bin:$PATH"
misconfig version
misconfig doctor

Expected version: misconfig 0.1.10. Repeat the PATH line in a new terminal, or add it once to your shell profile. doctor checks local prerequisites; it does not change infrastructure.

Step 2

Pair your device

Sign in to the console first, then run:

misconfig setup --control https://console.misconfig.cloud

The runtime shows the local changes and opens browser approval. Confirm your own device in the correct team. Keep pairing codes and tokens private. If this device is already paired to this console, skip setup.

When pairing completes, run misconfig profile list. An empty list means your team has not created an access profile yet—not that pairing failed.

Step 3

Choose what the agent may do

Open Access & rules. Select an existing profile for your workspace and intended system. Review its environment, resource boundary and permitted work. If none fits, create access or ask your team administrator to help.

For a verified typed-action connection, choose work from its catalog and review access before saving. Advanced scope configuration still uses resource prefixes: these include IDs that extend the prefix, not just one exact resource. Saving access does not execute a change.

Step 4

Launch and check one action

In Access & rules, copy Start a session's command. Run it in the exact workspace configured by that profile. The command contains your actual profile ID; don't substitute another team's ID.

Ask the agent to perform one permitted, non-mutating check, report its result and stop. For an AWS profile explicitly configured to allow the identity lookup, a suitable test is:

Run aws sts get-caller-identity once using my selected read-only AWS profile. Report the account ID, then stop. Do not change any resource.

In Sessions, confirm the system and workspace, then check Activity. A local-hook result is Observed; Verified means a separate verifier checked provider state. Don't test denial by attempting a destructive command on real resources.

To test remote stop, stop the session in the console with a reason, then request another harmless read. Once the runtime observes the stop, it must perform no further governed calls. This does not revoke existing external credentials in local-credential mode.

If something gets in the way