# InkRoom — one-paste Agent setup

User experience: one pasted prompt, then ready to create. Reuse supplied credentials; for Grok Bot the prompt deliberately excludes the Key, so obtain it through a supported secure credential request. Never request a Key in ordinary chat. Do not ask for an installation directory, Python, Node, Go, administrator permissions or package managers. Normal host approval rules still apply. Do not claim support when the host cannot execute local programs or discover skills.

1. Use the website origin from the user's pasted prompt (the origin hosting this document). Read `ORIGIN/skills/manifest.json`.
2. Detect the actual operating system and CPU using the host's available environment tools. Map macOS to `darwin`, Windows to `windows`, Linux to `linux`; map Apple Silicon/aarch64/arm64 to `arm64`, x86_64/AMD64 to `amd64`. These are separate native builds, not one binary that runs on all CPUs. Do not guess or emulate a different architecture.
3. Download the matching manifest artifact from this same origin into a temporary directory and verify its SHA-256 against the manifest before executing it. On macOS/Linux set its executable permission. Do not run an artifact with a mismatched hash. No runtime installation is needed.
4. Determine the current Agent's actual supported user-level Skill directory from its environment/configuration. For Codex use `$CODEX_HOME/skills` when set, otherwise `~/.codex/skills`. For other hosts use their confirmed supported directory; do not silently install into an unrelated host. Run the downloaded executable: `inkroom install --origin ORIGIN --skills-dir RESOLVED_DIRECTORY`. The executable automatically discovers the service endpoints and installs itself plus the embedded standard `SKILL.md`. If an `inkroom` Skill already exists, inspect it and reuse compatible existing installation; do not overwrite unrelated or customized contents. If it differs, explain the specific update needed.
5. A registered account and valid MCP Token are required. If absent, stop and direct the user to sign in to InkRoom and copy the account setup prompt. Send the supplied Token to `authorize` through standard input, never command arguments or logs. `authorize` verifies the Token through a read-only tool discovery request before saving it. If verification fails, ask for a valid Token rather than reporting success. Discover tools and read saved account permissions and spending policy. Do not change limits or generate during setup. Never fall back to website guest endpoints. Do not collect machine codes, MAC addresses or hardware fingerprints.

Preserve other skills, preferences and credentials. Host approval rules still apply. Installing does not grant account capabilities or spending authorization; the server enforces them. Use the server-reported available balance and the user's MCP authorization limits.

## Grok Bot

Grok Bot is the third client on both InkRoom installation pages. Its cloud computer is separate from the user's local computer. Detect its actual Linux architecture and supported installation directory, verify the same standalone artifact, and reuse the existing account-only client and billing. Save the credential-free instructions as a private Skill in Grok Bot's skill library and verify discovery in the `/` menu; placing a file in an unconfirmed directory is not proof of registration. Preserve other private skills.

Use a supported secure credential request to pass the MCP Key into `authorize` standard input. If secure transfer or private-skill registration is unavailable, report the exact blocked step. Do not put the Key in the Skill, ordinary chat, command arguments or model-visible tool arguments. Save original images in a project folder under `/workspace`, inspect actual files, and use the host's supported result display. Do not create a routine during installation.

References: [Grok Bot computer and apps](https://docs.x.ai/grok-bot/computer-and-apps), [Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations).