okibi.ai

Command Palette

Search for a command to run...

See What an Okibi CLI Install Changes and Remove It Cleanly

Last updated: 11/18/2026

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.

See What an Okibi CLI Install Changes and Remove It Cleanly

Before customers or an IT team run an install command, they ask what it puts on the machine and how to take it off. This guide installs acme-orders into a throwaway home directory, lists every file the installer created, and then removes all of it with the CLI's own uninstall command.

What you will build

A before-and-after file listing around an install, and a clean uninstall.

signed install command  ->  files in $HOME  ->  acme-orders uninstall --confirm  ->  nothing left

AI Prompt

Using the Okibi CLI and the published acme-orders CLI, show what an install changes and that uninstall reverses it.

Requirements:
- Install into a temporary HOME with `CODEX_HOME` and `CLAUDE_CONFIG_DIR` unset, using the command from `okibi clis hosting status acme-orders --json`.
- List every file and symlink the install created.
- Create some local data (`sync` and a `--local-only` feedback entry) with HOME pointing at the temporary directory.
- Run `uninstall` without `--confirm` and report what it says. Then run it with `--confirm`.
- Set `ACME_ORDERS_NO_KEYRING=1` on every command you run from the installed CLI, `uninstall` included, so no system keyring entry can be touched.
- List the files again. Never run uninstall with your real HOME.
- Run the verification step below before finishing.

Prerequisites

  • The Acme Orders mock server, server.py (a fictional orders API). Download it into your working directory:

    curl -fsSLO https://raw.githubusercontent.com/heterochromatic/okibi-examples/main/acme-orders/server.py
    
  • A generated CLI named acme-orders with an official release (okibi clis release set acme-orders --release <release-id>) and the Acme Orders example API running (ACME_API_KEY=demo-key python3 server.py --port 8099).

  • Okibi CLI 0.2.11, logged in.

Note: Every command below uses HOME=$T, a throwaway directory, and ACME_ORDERS_NO_KEYRING=1. HOME isolates files only. It does not isolate the operating system's keyring, which uninstall also clears, so the second variable is required. uninstall deletes credentials, configuration and local data, so keep it away from your real home.

1. Install into a throwaway home

T=$(mktemp -d)
CMD=$(okibi clis hosting status acme-orders --json | python3 -c "import json,sys;print(json.load(sys.stdin)['workspaceInstallCommand']['command'])")
env -u CODEX_HOME -u CLAUDE_CONFIG_DIR HOME=$T ACME_ORDERS_NO_KEYRING=1 sh -c "$CMD"

The command comes from workspaceInstallCommand.command in the hosting status. It is a curl ... | sh line with a signed URL, so do not paste it into logs. The installer ends with a note that $T/.local/bin is not on your PATH. The commands below use the full path, so you can ignore it. Keep using the same terminal, so $T stays set.

2. List what was created

(cd $T && find . \( -type f -o -type l \) | sort)
./.agents/skills/acme-orders
./.local/bin/acme-orders
./.local/bin/acme-orders.okibi-update
./.local/share/okibi/clis/acme-orders/versions/<n>/.okibi-update
./.local/share/okibi/clis/acme-orders/versions/<n>/acme-orders
./.local/share/okibi/clis/acme-orders/versions/<n>/skills/acme-orders/.okibi-managed
./.local/share/okibi/clis/acme-orders/versions/<n>/skills/acme-orders/.okibi-owner
./.local/share/okibi/clis/acme-orders/versions/<n>/skills/acme-orders/SKILL.md
  • The binary lives under versions/<n>, where <n> is the Okibi version number of the release you installed (it was 3 for release 1.0.2 and 5 for 1.0.4 on the test CLI). Read it from the symlink with readlink $T/.local/bin/acme-orders instead of typing it. ~/.local/bin/acme-orders is a symlink to it.
  • ~/.agents/skills/acme-orders is a symlink to the skill folder that ships with that version.
  • The .okibi-update files, .okibi-managed and .okibi-owner are files the installer writes next to the binary and skill. Okibi's help does not describe them. The skill's .okibi-owner held the CLI project id.

3. Create local data

export ACME_ORDERS_API_KEY=demo-key   # the CLI's name for the key the example server calls ACME_API_KEY
HOME=$T ACME_ORDERS_NO_KEYRING=1 $T/.local/bin/acme-orders sync --agent 2>/dev/null | grep sync_summary
HOME=$T ACME_ORDERS_NO_KEYRING=1 $T/.local/bin/acme-orders feedback "temp home note" --local-only
(cd $T && find . -type f | grep -v versions | sort)
{"event":"sync_summary","total_records":12,"resources":3,"success":3,"warned":0,"errored":0,"duration_ms":8}
feedback recorded locally (14 chars)
./.local/bin/acme-orders.okibi-update
./.local/share/acme-orders/data.db
./.local/share/acme-orders/feedback.jsonl

sync created the local database, and feedback created the feedback file. sync needs the example API to be running. Its summary line is printed so that a failure shows: with the API down, errored is not 0 or the line is missing.

4. Uninstall

Without --confirm, the command only describes what it would do:

HOME=$T ACME_ORDERS_NO_KEYRING=1 $T/.local/bin/acme-orders uninstall --agent
This removes the acme-orders command, its credentials, configuration, and local data.
Run `acme-orders uninstall --confirm` to continue.

With it:

HOME=$T ACME_ORDERS_NO_KEYRING=1 $T/.local/bin/acme-orders uninstall --confirm --agent
acme-orders has been uninstalled.

Verify the result

(cd $T && find . \( -type f -o -type l \) | wc -l)

Expected: 0. The binary, the version folder, both symlinks, the skill, the local database and the feedback file were all removed. In the test run, the real home's ~/.local/share/acme-orders (data.db, feedback.jsonl) was untouched, and security find-generic-password -s acme-orders found no keychain entry before or after. The first is isolated by HOME. The second is protected by ACME_ORDERS_NO_KEYRING=1.

How it works

The installer writes a versioned copy under ~/.local/share/okibi/clis/<name>/versions/<n> and links it into ~/.local/bin and ~/.agents/skills. uninstall removes the command, its credentials, configuration and local data, and --confirm is required.

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.

Uninstall is not a dry run

The no-flag form only prints the warning. It does not list files. Use the listing in step 2 first.

Real home directories

If CODEX_HOME or CLAUDE_CONFIG_DIR is set, the installer can link the skill into those directories instead of the temporary home. The env -u in step 1 prevents that.

The bookkeeping files are part of the install

acme-orders.okibi-update stays after sync and feedback create their own files. It is removed by uninstall with everything else.


verification:
  status: verified
  tested_at: "2026-11-02"
  product_version: "okibi 0.2.11; acme-orders 1.0.2"
  command: "find $T -type f -o -type l | wc -l; ./acme-orders uninstall --confirm; find $T -type f -o -type l | wc -l"
  expected_result: "file count before, then 0 after uninstall in the sandboxed home"

Related Articles