Customer setup help

Setup prompts for your agent

Copy these prompts into your coding agent (OpenClaw, Codex, Claude Code, Cursor, and similar). They guide install and validation using public Dexgate docs and supported packages only.

Use workspace identifiers and credentials issued through the Dexgate console. Confirm activation with the validation checks below.

How to use

Pick the prompt that matches your stage (free check, then paid connection).
Copy it into your agent session. Keep secrets out of chat when possible—point the agent at files or environment variables you control.
When it asks for proof, paste real command output or console screenshots.
If free vs paid is unclear, re-read the linked docs or contact us.

Production validation

A production connection is validated only when:

The adapter connects to a live licensed Dexgate runtime.
The workspace and runtime identifiers match those issued in the console.
The runtime returns an authenticated policy decision.
The resulting governed action and evidence record are visible in the customer workspace.

Local demonstrations, static samples, and simulated responses do not satisfy these validation criteria.

Operating rules

Follow the linked Dexgate docs and supported public package commands.
Use only credentials and identifiers issued through the Dexgate workspace.
Free self-check success: dexgate-assess packageSelfCheck PASS means packaged policy self-check passed (no Passport; env inspect is best-effort and does not prove live interception).
Free local hard-gate success: adapter installed and enabled per the OpenClaw free quickstart.
Paid success: live licensed runtime path that meets the production validation criteria above.

Download all prompts (.md) Get started Enterprise rollout

Prompts

1. Free first success

When: first evaluation · Goal: free policy self-check PASS, then free adapter install · No licensed runtime required

You are helping me evaluate Dexgate free local hardening for a coding agent.

Constraints:
- Follow only these docs:
  - https://dexgate.ai/get-started/
  - https://dexgate.ai/compatibility/
  - https://dexgate.ai/docs/openclaw/quickstart/  (recommended free path)
  - https://dexgate.ai/docs/codex/quickstart/
  - https://dexgate.ai/docs/setup-prompts/
- Use only supported public packages and commands from those docs.
- Free mode has no Passport and does not require a licensed runtime.
- Free defaults are conservative and adapter-specific (OpenClaw: read_file / list_files / search_files only; Codex: read-only shell allowlist; apply_patch and mutations blocked). Exact surfaces: https://dexgate.ai/compatibility/
- High-consequence actions (for example git push, unrestricted shell, writes/deletes, apply_patch on Codex free) should stay blocked free unless the operator deliberately expands the allowlist.
- dexgate-assess always runs a packaged representative-action policy self-check and a best-effort OpenClaw/plugin environment inspect. It does not install or enable the plugin, and it does not prove a real agent turn was intercepted.
- Optional claim URL stores the sanitized package self-check only (not environment fields).

Tasks:
1. Confirm my agent runtime and OS.
2. Optionally run the free policy self-check (OpenClaw: npx --yes --package=@dexgate/openclaw-trusted-mode@1.0.18 dexgate-assess). Read packageSelfCheck and environment fields; treat package PASS as policy self-check passed — not proof of live interception.
3. Install and enable the matching free adapter using the official quickstart so free allowlist policy applies in real sessions.
4. Summarize: packageSelfCheck, useful env fields (if present), whether the adapter is installed/enabled, what works free, what is blocked free, and the single next step if I later want a paid pilot.

If a step fails, show the exact error and the matching doc section. Do not claim live enforcement from packageSelfCheck PASS alone; do not disable the free hard gate after install.

2. Paid pilot connection

When: after a successful free self-check · Goal: live licensed runtime + governed path

You are helping me complete Dexgate paid pilot first success (minimum production topology).

Constraints:
- Canonical docs only:
  - https://dexgate.ai/docs/dexgate/minimum-setup/
  - https://dexgate.ai/docs/enterprise-rollout/
  - https://dexgate.ai/docs/setup-prompts/
- Topology: one Linux Docker host for the licensed Dexgate runtime + one agent host (Windows/macOS/Linux is fine for the agent).
- Workspace and runtime identifiers, download packages, and credentials come from the customer console I provide. Use only credentials issued through the Dexgate workspace.
- A live licensed runtime is required for production validation.
- Local demonstrations do not qualify as production-runtime validation.

Production validation (all required):
1. The adapter connects to a live licensed Dexgate runtime.
2. Workspace and runtime identifiers match those issued in the console.
3. The runtime returns an authenticated policy decision.
4. Governed action and evidence are visible in the customer workspace.

Tasks:
1. Confirm free baseline already passed on my adapter.
2. Walk console downloads (runtime package, configuration, credentials) using values I provide—never fabricate them.
3. On the Linux Docker host: install/bootstrap per docs; confirm runtime health using the console-documented health check.
4. For OpenClaw: after runtime is healthy, install/start Decision Middleware (SDE_PDP_* env on that process only), then set toolPolicyMode=MIDDLEWARE + decisionMiddlewareUrl (no pdpAuthToken on the plugin). Choose gatewayId yourself (e.g. gw-dev).
5. Stop when production validation criteria are met.
6. List Day-2 verify steps (console deployments, one evidence row, re-run paid check).

If I only have Windows and no Linux Docker path yet, stop and explain the Linux requirement.

3. Day-2 verify (paid pilot)

When: after first connection · Goal: consistent and repeatable governed path + evidence

You are helping me complete Day-2 verification for a Dexgate paid pilot.

Confirm activation using the validation checks below (all must be real outputs):
1. Runtime health check from the console-documented procedure returns healthy.
2. Adapter paid check shows a governed path against the live licensed runtime.
3. Customer console Deployments looks healthy for this pilot.
4. After one gated action, decision or Passport evidence exists in the customer workspace.

Docs:
- https://dexgate.ai/docs/dexgate/minimum-setup/
- https://dexgate.ai/docs/enterprise-rollout/
- https://dexgate.ai/docs/setup-prompts/

Tasks:
1. Run through the four checks in order. For each, ask me for real command/UI output if you cannot run it.
2. Mark PASS / FAIL with the evidence snippet.
3. If FAIL, give the smallest fix tied to docs (credentials, runtime URL, free mode still enabled, wrong host).
4. When all PASS, write a 5-bullet summary for platform and security (scope, still free-blocked items, where evidence lives, rollback = free-only or uninstall adapter).

Do not expand to multi-runtime mesh until Day-2 is consistent and repeatable.

4. Troubleshoot free vs paid confusion

When: checks disagree or Passport never appears · Goal: diagnose path with real evidence

You are diagnosing whether my Dexgate setup is still on the free local hard gate or on the paid licensed-runtime path.

Constraints:
- Docs: https://dexgate.ai/get-started/ , https://dexgate.ai/docs/dexgate/minimum-setup/ , https://dexgate.ai/faq/ , https://dexgate.ai/docs/setup-prompts/
- Free self-check: package self-check + best-effort env inspect; no Passport; not proof of live interception; claim stores package self-check only.
- Free local hard gate: adapter installed and enabled; still no Passport.
- Paid: live licensed runtime; authenticated policy decision; evidence in the customer workspace.
- Use console package credentials only on the runtime and Decision Middleware processes; for MIDDLEWARE, do not put the runtime authorize bearer token (plugin pdpAuthToken) on the OpenClaw plugin.

Tasks:
1. Collect free policy self-check output (if any), evidence the free adapter is installed/enabled (if claimed), and paid check output (if any).
2. State clearly: self-check only, free local hard gate, paid path, or mixed/misconfigured.
3. List the smallest ordered fixes to reach the intended path.
4. Do not recommend unrestricted host execution as a substitute for Dexgate governance.

Supported integrations and status: compatibility matrix. Free policy self-check: npx --yes --package=@dexgate/openclaw-trusted-mode@1.0.18 dexgate-assess.