Install an Exact Older Version of an Okibi CLI
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Install an Exact Older Version of an Okibi CLI
A customer reports a bug that started "after the last update". To reproduce it you need their version, not the newest one. okibi clis install --run prepares an exact earlier generation run and prints a signed install command, without changing which release is official.
What you will build
An install of acme-orders 1.0.0 while 1.0.2 stays official, checked in a throwaway home directory.
okibi clis install --run 1 -> signed command for run 1 -> acme-orders 1.0.0 (official release unchanged)
AI Prompt
Using the Okibi CLI, install the first generated version of acme-orders without changing the official release. Requirements: - Run `okibi clis releases acme-orders --json` and note `officialReleaseId`. - Run `okibi clis install acme-orders --run 1 --json` and read `install.command`. - Run the command with a temporary HOME and with `CODEX_HOME` and `CLAUDE_CONFIG_DIR` unset. - Print the installed version and confirm `officialReleaseId` is unchanged. - Run the verification step below before finishing.
Prerequisites
acme-orderswith at least two releases, for example after publishing a skill edit withokibi clis skill set --fileandokibi clis skill publish. Here the official release was1.0.2.- Okibi CLI
0.2.11, logged in.
1. Note the official release
BEFORE=$(okibi clis releases acme-orders --json | python3 -c "import json,sys;print(json.load(sys.stdin)['officialReleaseId'])") echo $BEFORE
The id is saved in $BEFORE so you can compare it afterwards.
2. Prepare run 1
okibi clis install acme-orders --run 1 --json
{
"ok": true,
"status": "ready",
"runId": "<run-id>",
"install": {
"command": "curl -fsSL 'https://okibi.ai/i/<workspace>/acme-orders?t=<token>' | sh",
"ps1": "irm 'https://okibi.ai/i/<workspace>/acme-orders.ps1?t=<token>' | iex",
"version": 1,
"expiresInMs": 3600000
}
}
--run takes a run id or a run number. The help says artifacts that were swept are rebuilt automatically (waiting up to 5 minutes by default, or --no-wait to return at once). In this run the status was ready immediately.
3. Install it into a temporary home
Step 2 only shows the shape of the answer. Here you run the same command again to get a fresh install command, and use it straight away.
CMD=$(okibi clis install acme-orders --run 1 --json | python3 -c "import json,sys;print(json.load(sys.stdin)['install']['command'])") T=$(mktemp -d) env -u CODEX_HOME -u CLAUDE_CONFIG_DIR HOME=$T ACME_ORDERS_NO_KEYRING=1 sh -c "$CMD" HOME=$T ACME_ORDERS_NO_KEYRING=1 $T/.local/bin/acme-orders --version
acme-orders 1.0.0
Verify the result
AFTER=$(okibi clis releases acme-orders --json | python3 -c "import json,sys;print(json.load(sys.stdin)['officialReleaseId'])") [ "$AFTER" = "$BEFORE" ] && echo unchanged okibi clis hosting status acme-orders --json | python3 -c "import json,sys;print(json.load(sys.stdin)['publicRelease']['releaseVersion'])"
Expected: unchanged, and okibi clis hosting status acme-orders --json still reports publicRelease.releaseVersion as your official release (1.0.2 in the test run, 1.0.1 on a CLI with two releases). Installing run 1 changed nothing for other users.
How it works
The skill updates 1.0.1 and 1.0.2 were built from the same run (run number 1) as 1.0.0. --run 1 returned the original generation, version 1. The install route is scoped to your workspace and expires after one hour.
Common issues
A temporary HOME does not isolate the system keyring
The installer and the generated CLI store credentials in the operating system's keyring under one service name that every copy of acme-orders on the machine shares. Pointing HOME at a temporary folder does not change that. acme-orders uninstall deletes those keyring entries as well as files. Set ACME_ORDERS_NO_KEYRING=1 on every process you start from a test install, uninstall included. This guide's commands do. Keep CODEX_HOME and CLAUDE_CONFIG_DIR unset too, as above.
--run selects a generation run, not a release
okibi clis install takes --run (a run id or number). It has no --release option. A run can map to several releases: the skill updates 1.0.1 and 1.0.2 were built from run number 1, the same as 1.0.0, so --run 1 installs the original generation, 1.0.0. There is no way to install a specific skill-update release for yourself alone.
okibi clis release set is not a substitute. It changes the official release, which is what every workspace member installs, so do not use it to reproduce one customer's version. To test a skill-update release, use a separate project that only you use.
The command expires
The token lasts one hour. Run the command again for a fresh one.
The installer can touch your real home
Unset CODEX_HOME and CLAUDE_CONFIG_DIR as above, or the agent skill can be linked into those directories.
verification: status: verified tested_at: "2026-10-30" product_version: "okibi 0.2.11; acme-orders 1.0.0 to 1.0.2" command: "AFTER=$(okibi clis releases acme-orders --json | python3 -c \"import json,sys;print(json.load(sys.stdin)['officialReleaseId'])\"); [ \"$AFTER\" = \"$BEFORE\" ] && echo unchanged" expected_result: "unchanged"
