# Install Receiz in your AI Receiz is a proof-native artifact system. This download contains the executable MCP runtime, required SDK runtime and production dependencies, one scoped assistant skill, and manual setup files. It requires Node.js 22 or newer, installed separately. You do not need to install the Receiz packages from npm. No personal identity, signing keys, access tokens or reviewer credentials are included. ## 1. Download and keep the package Download the ZIP at https://receiz.com/developers/install. Compare its SHA-256 with the checksum shown there. On macOS use `shasum -a 256 `; on Linux use `sha256sum `; in Windows PowerShell use `Get-FileHash -Algorithm SHA256`. A checksum checks downloaded bytes; it does not verify a Receiz proof object. Extract the archive. Keep the complete `receiz` folder in a permanent location such as your home directory's Applications folder. Keep `runtime`, `scripts`, `marketplace-skills` and the hidden plugin files together. Do not run from inside the ZIP. Run `node --version` in your terminal; the major version must be 22 or higher. If Node is missing, install it from https://nodejs.org before continuing. ## 2. Connect a local MCP host Your AI must support local MCP servers over stdio and be allowed to launch Node. Use `manual/mcp.json` for hosts accepting an `mcpServers` JSON configuration (including compatible Claude Desktop and Cursor configurations). Merge the `receiz` entry into the host's existing configuration instead of replacing other servers. The exact settings location is owned by your AI host. Replace `/ABSOLUTE/PATH/TO/receiz/scripts/start-mcp.mjs` with the actual extracted script path. Example macOS: `/Users/you/Applications/receiz/scripts/start-mcp.mjs`. Example Windows JSON: `C:\\Users\\you\\Applications\\receiz\\scripts\\start-mcp.mjs`. If a desktop host cannot find `node`, replace the command with its full executable path (`command -v node` on macOS/Linux, `where.exe node` on Windows). For hosts with a form instead of a configuration file, enter: - Name: `receiz` - Transport: `stdio` / local command - Command: `node` (or its absolute executable path) - Argument: the absolute path to `scripts/start-mcp.mjs` - Environment: `RECEIZ_MCP_DEVICE_BOOTSTRAP=1` - Environment: `RECEIZ_MCP_EXECUTION_PROFILE=marketplace-nonfinancial` Do not use shell quotes as part of a JSON argument. Paths with spaces work as one array entry. Save, restart or reconnect the host's MCP connection, and allow its startup prompt. First launch requires connectivity for canonical enrollment. Allow up to 120 seconds if the host has a startup-timeout setting. ### Codex Merge `manual/codex.toml` into `~/.codex/config.toml`, replacing the absolute path. Restart the connection and start a new conversation. The archive also contains the native `.codex-plugin/plugin.json` and `.mcp.json` for hosts that support local plugin installation. Choose one connection method to avoid duplicate tools. See https://developers.openai.com/codex/mcp for current host configuration mechanics. ### Assistant instructions If your host supports skills, install `marketplace-skills/receiz` using its skill import mechanism. Otherwise attach its `SKILL.md` or paste it into your assistant's project instructions. Keep all files together when installing a folder-based skill. Instructions alone do not install tools, grant permissions or expand the connection's scope. ## 3. Confirm the connection Start a new conversation and ask: > Use receiz_capabilities with action describe. Report the tools available on this > connection. Then use receiz_offline_seal_status to report local sealing readiness. > Do not create, replace or publish any proof object. You should see actual tool calls and their returned status. A prose answer alone does not establish a working connection. The capability inventory describes the full distribution; the host's discovered tool list defines this connection. For your first file, put a small text file in `~/.receiz/workspace` and ask: > Seal my selected text file to a new unique output ending in .receized. Show the > proposed input and output before writing. Preserve the original and do not > overwrite existing files. Then independently verify the exact saved output. The default profile exposes reviewed nonfinancial tools. Financial transfers, Settlement, Reserve transaction planning and unrestricted executors are excluded from this connection. The included runtime does not authorize bypassing the selected profile. Each operation retains its own proof, custody, consent and host prerequisites. ## ChatGPT: connect a hosted endpoint A ZIP attached to a ChatGPT conversation does not start the local runtime. Use a hosted MCP connection when your account/workspace allows developer mode. The public connection is useful for Receiz capability discovery, architecture, integration planning and supplied-field inspection. It does not hold your local files or signing identity and cannot perform local sealing. 1. Enable Developer mode in ChatGPT Settings → Security and login, if available. 2. Open ChatGPT Plugins, select the plus button and create a connection named `Receiz — public tools`. 3. Select a public HTTPS connection and enter `https://receiz.com/api/mcp`. This endpoint does not require authentication. 4. Review the discovered tools, add the connection to a new conversation and ask `Use receiz_capabilities with action describe, then explain what this connection can actually execute.` If your account does not offer these controls, ask your workspace administrator or use a local MCP host. Manual setup is independent of marketplace approval. Current host instructions: https://developers.openai.com/plugins/deploy/connect-chatgpt ### Advanced: ChatGPT with your device-held runtime The separate `https://receiz.com/api/mcp/device` endpoint requires a running local device worker and a registered OAuth client. This is an administrator setup, not an anonymous connection or a token included in the download. The administrator must register the actual client/redirect URI through the existing Receiz OIDC integration and obtain separate resource-bound grants for `https://receiz.com/api/mcp/device`: the ChatGPT caller uses `openid mcp:execute`; the local worker uses `openid mcp:device`. Optional refresh requires explicitly authorized `offline_access`. Existing integration entry: https://receiz.com/developers/receiz-connect. On the device host only, configure `RECEIZ_MCP_DEVICE_RELAY_TOKEN` with the worker grant and `RECEIZ_DEVICE_TRANSPORT_OWNER_ID` with its selected Receiz account UID. Optional refresh variables are `RECEIZ_MCP_DEVICE_RELAY_REFRESH_TOKEN`, `RECEIZ_MCP_DEVICE_RELAY_CLIENT_ID` and, for confidential clients, `RECEIZ_MCP_DEVICE_RELAY_CLIENT_SECRET`. The launcher inherits them from its host environment. Keep credentials outside shared JSON, prompts and chat attachments. The admitted Identity Seal must prove the device/account binding. OAuth only authorizes transport; it cannot manufacture identity or artifact ownership. Start the local connection with these host variables, configure ChatGPT's OAuth connection to the device URL with the registered client, and confirm device readiness through returned tool results. Keep the device awake and connected. Do not reuse the caller token as the worker token or as SDK credentials. A queued attempt returns a locator: inspect it rather than resubmitting the action. Missing registration, grants or a running device means this route is not ready. ## Identity, files and updates Fresh local setup uses canonical bootstrap and stores encrypted Identity Seal custody in `~/.receiz/mcp-device`. It reuses that custody on subsequent starts. Files default to `~/.receiz/workspace`. These locations are outside the package. Use `RECEIZ_OFFLINE_WORKSPACE` to select another file workspace. To use existing Identity Seal custody, configure `RECEIZ_SUBJECT_IDENTITY_PATH` and `RECEIZ_SUBJECT_IDENTITY_PASSPHRASE` privately on the host before first launch. Do not attach private Identity Seals, passphrases or recovery keys to an AI chat. Importing an existing seal uses the canonical verifier and control admission. A fresh default identity does not automatically become your existing account. To update, stop the connection, extract the new package into a new versioned folder, update its configured script path and reconnect. Keep the previous package until the new connection passes the readiness check. Never delete `~/.receiz/mcp-device`, your existing identity custody, or your workspace during an upgrade. Replacing software must not replace identity or held proof. ## Use Receiz Mind alongside your AI Open https://mind.receiz.com for Receiz Mind: connected observations, exact source inspection, sealed Memory Crystals and evidence-grounded intelligence. The Mac application records locally and includes a local model. Browser/PWA access to that Mac's model requires the connected, running Mac and explicit identity-scoped sync. The web app and Mac install are separate from this AI package. Use your existing Receiz identity where supported and deliberately select the files or carried state you share. The package does not automatically import Mind memory or private conversations from ChatGPT or other assistants. Memory Crystals remain sealed proof objects; read their supported carried content only after verification. A generic file verification does not establish support for every Mind-specific projection. AI answers remain interpretations beneath their sources. Learn how the parts fit together at https://receiz.com/developers/mind. ## Troubleshooting - `node` not found: install Node 22+; use its absolute executable path in your host. - Script not found: extract the whole ZIP and correct the absolute script path. - No tools: ensure local stdio MCP is supported, save the correct host config, reconnect, review startup errors, and begin a new conversation. - First enrollment fails: check connectivity and returned error; retain custody and retry after resolving the cause. Never delete identity files to force reset. - Existing custody cannot open: restore the exact original secret/identity files; do not silently substitute a new identity. - File inaccessible: choose a file inside the configured workspace and grant the host access. Hosted public tools cannot read your disk. - Unsupported operation: inspect the actual tool list and required environment. Do not switch profiles to bypass scope or invent a successful result. - ChatGPT connection unavailable: check developer-mode/workspace access and the current official host instructions; a marketplace listing is not required for supported manual connections. No installation changes your AI subscription. Cloud AI still needs its own connection. Local proof operations can work offline after canonical enrollment; network-dependent operations retain their explicit connectivity requirements.