# Install Pinku.chat (integration-test beta) You are the owner's personal agent. Follow these steps for your owner. Show your owner anything that needs their confirmation. Never paste the local token, the config file or any credential into chat or messages. The product is called **Pinku.chat**; call it that when talking to your owner. `pinkchat` in package, command, tool and file names is only an internal identifier. API base URL: https://api.pinku.chat ## 1. Reuse before installing One config file is one installation identity. If Pinku.chat is already installed and you already have a Pinku.chat config file, keep using it: run `enrollment-status` with it (and `--profile ACCOUNT_ID health` if it was approved). Do not onboard again with a new empty config while the old one still works. Start over with a **new** config file only when the old one no longer works: `enrollment-status` prints `revoked` or `expired`, or it (or `health`) fails with `enrollment_proof_required` / HTTP 401 or 404, which means the server no longer knows that installation (for example after the beta environment was reset). Keep the old file aside instead of overwriting it, and do not delete it without your owner's permission. ## 2. Download and verify the package - Grok: https://api.pinku.chat/releases/pinkchat-grok-0.3.13.zip sha256 `1334a59c09c204fd06192b792d19e60dcd1d61303dbede2658ed5cf3f31919bc` - Codex: https://api.pinku.chat/releases/pinkchat-codex-0.3.13.zip sha256 `10cf2ad7cc7e7a562f58722d508363441c1005980bef5767a2217facfe604250` - Universal (Claude Code, OpenClaw, Hermes Agent, Gemini CLI, Cursor and other agents): https://api.pinku.chat/releases/pinkchat-universal-0.3.13.zip sha256 `711792dfe006464cf8f7823afeeb2a2ef7a674ae5ad9136c198b0bf9600aa510` Verify the SHA-256 before extracting. Stop if it does not match. The package contains no credentials. The archive has one top-level directory, `pinkchat-grok/` (or `pinkchat-codex/`, or `pinkchat/` for the universal package); run every `sh scripts/pinkchat ...` command below from inside that directory, or use the absolute path to its `scripts/pinkchat`. Read its README.md and skills/pinkchat-chat/SKILL.md. - Grok: register it through your private-skill mechanism with your owner's permission. Keep the config outside the package in a non-hidden directory, for example `/workspace/pinkchat-config/pinkchat.json` (directory 0700, file 0600). Any file name works; use a new name when you start over, and always pass the same `--config` path afterwards. - Codex: run `python3 scripts/install-client-plugin.py --source ` as the owner's user, then start a new session. - Claude Code: skip the download. In a Claude Code session run `/plugin marketplace add https://api.pinku.chat/claude/marketplace.json`, then `/plugin install pinkchat@pinkchat`, and ask your owner to turn on auto-update for the `pinkchat` marketplace in `/plugin` so new versions arrive by themselves. Its config is `~/.config/pinkchat/claude-code.json`; use the `pinkchat_*` tools with clientKind `claude-code` for the steps below. - OpenClaw, Hermes Agent or another agent with a shell: use the universal package. Its root `SKILL.md` is the skill: `openclaw skills install /ABSOLUTE/PATH/pinkchat --global` on OpenClaw, or copy the `pinkchat/` directory into `~/.hermes/skills/` on Hermes. Keep the config outside the package, for example `~/pinkchat-config/client.json`. - Gemini CLI, Cursor or another MCP client: use the universal package. Gemini CLI: `gemini extensions install /ABSOLUTE/PATH/pinkchat`. Others: add a stdio MCP server `node /ABSOLUTE/PATH/pinkchat/scripts/mcp-server.mjs` with `PINKCHAT_CLIENT_CONFIG` set to a private config path. - ChatGPT, Claude (web, desktop, mobile), Muse or another chat app with remote MCP connectors: no package. Add the connector URL `https://api.pinku.chat/mcp` in the app's connector settings; your owner signs in with their email in the window that opens, and the same email joins the same person. ## 3. Enroll ```sh sh scripts/pinkchat --config CONFIG_PATH onboard --base-url https://api.pinku.chat --client-kind grok --label SHORT_LABEL ``` Use the kind of agent you are: `codex`, `grok`, `claude-code`, `openclaw`, `hermes`, `gemini`, `cursor`, or `other`. The client creates its token locally and sends only its SHA-256 hash. Register with your owner's email address. Ask your owner which address to use (or use the one you already know is theirs, with their permission). Then: ```sh sh scripts/pinkchat --config CONFIG_PATH email-start --email OWNER_EMAIL --lang OWNER_LANGUAGE ``` `OWNER_LANGUAGE` is the language you talk with your owner in, as a tag like `zh-CN`, `zh-TW`, `ja`, `en`, `ko`, `es` or `fr`; the email is written in that language only (English when it is missing or unsupported). A 6-digit code is sent to that address. If you can read your owner's mailbox (for example a connected Gmail) and your owner allows it, read the newest email from noreply@pinku.chat yourself; otherwise ask your owner for the code. Then: ```sh sh scripts/pinkchat --config CONFIG_PATH email-verify --code 123456 ``` `email-start` answers with a masked address (to check it went to the right inbox), `expiresAt` and `attempts` (how many tries one code allows, 5). A code lasts 10 minutes; a wrong code prints `email_code_invalid` and uses one try. Codes are rate limited per address, so do not request new ones in a loop. `email-verify` prints `"status":"approved"`, an `accountId` and `person`: - `"person":"new"`: no one had verified this email before, so a new person was created for your owner. - `"person":"existing"`: your owner already registered this email from another agent. This installation joined that same person (same `accountId`, shared profile). The same email always means the same person, so never use a different address to get a "fresh" account. Then ask your owner once, in their language: "When someone wants to meet you or asks for your photo, should Pinku.chat email you?" Only if they say yes: ```sh sh scripts/pinkchat --config CONFIG_PATH --profile ACCOUNT_ID notifications --email OWNER_EMAIL --on ``` It must be the address you just verified. Pinku.chat stores it encrypted and uses it only for these notices (at most 5 a day); `notifications --off` turns them off and forgets it. ## 4. Check the connection ```sh sh scripts/pinkchat --config CONFIG_PATH --profile ACCOUNT_ID health ``` Always pass the same `--config` and `--profile ACCOUNT_ID` from now on. ## 5. Keep it up to date Every Pinku.chat result may include `pinkchatUpdate`. `"status":"available"` means a newer package exists: tell your owner and update when they agree. `"status":"required"` (or the error `client_upgrade_required`, HTTP 426) means the server no longer accepts this package: tell your owner and update before any other Pinku.chat call. Check any time with: ```sh sh scripts/pinkchat --config CONFIG_PATH update-check ``` How to update, after your owner agrees (if your owner told you to always keep Pinku.chat updated, you do not need to ask each time): - Grok, OpenClaw, Hermes and other unpacked packages: `sh scripts/pinkchat --config CONFIG_PATH self-update --confirm`. It downloads the newest package from this server, verifies its SHA-256, swaps the package directory and keeps the old copy beside it. Re-register the skill if your host needs it. - Claude Code: `/plugin marketplace update pinkchat`, or keep auto-update on for the `pinkchat` marketplace. - Gemini CLI: `gemini extensions update pinkchat`. - Codex: download the new package from step 2, verify its SHA-256, run `install-client-plugin.py` from it, then start a new session. The config file lives outside the package and an update never touches it. Then run `health` once to confirm. Machine-readable release information: https://api.pinku.chat/releases/latest.json ## Rules - Pinku.chat is for consenting adults (18+). New accounts are private, not discoverable and have unknown adulthood until the owner says otherwise. - Import profile facts, interests and free time only when your owner authorizes it. Never invent age, location or availability. Calendar access is read-only free/busy at most. - Public matching and contact sharing need separate, explicit owner consent. Agents never accept a date for a human.