Set up Orgo.ai as a computer for AI agents

LOCAL / laptop agent. Set up one Linux Orgo computer for Takibi. Do not run the BOX commands on this laptop.
Prerequisites: an Orgo account with approved billing/credits, an Orgo API key securely injected into the local environment as ORGO_API_KEY, and the intended ORGO_WORKSPACE_ID. The human must approve the computer's cost and intended Takibi grants before you begin. Refuse unresolved <ORGO-KEY-HERE> or <PASTE-KEY-HERE> values. Never echo keys, headers, or secret-bearing commands. Keep the Orgo control key off the box.

Use the Orgo REST base https://www.orgo.ai/api (verified 2026-10-21). Authenticate with Authorization: Bearer $ORGO_API_KEY, never logging it. The quickstart at https://docs.orgo.ai/quickstart stays a reference for request shapes.
1. Confirm the workspace UUID. GET /workspaces lists computers under desktops; its first call on an empty account can create a workspace. If the human wants a new workspace, explicitly POST /workspaces with its approved name and save the returned id. Never choose by display name alone.
2. If ORGO_COMPUTER_ID already exists, validate it and skip creation. Otherwise POST /computers once with JSON {"workspace_id":"<WORKSPACE-UUID>","os":"linux","name":"takibi-agent","billing_mode":"hourly"}, substituting the confirmed UUID. The hourly setting is required for free credits per the docs checked 2026-10-18; confirm current pricing before creation. Save the returned id as ORGO_COMPUTER_ID. Do not use instance_id or fly_instance_id. This id is desktops[].id in GET /workspaces and desktopId for file uploads. Print only the workspace and computer UUIDs from the response; never print or store vnc_password, which rotates on restart.
3. If creation times out ambiguously, stop and inspect GET /workspaces for the created computer. Never blindly re-create it. Pin the confirmed UUID in local configuration.
4. Readiness: poll GET /computers/{id}, at most 12 attempts spaced 5 seconds apart, with a 10-second timeout per request and a 180-second overall deadline. Stop immediately on error, frozen, or stopped. Once running, probe node -v through POST /computers/{id}/bash with JSON {"command":"node -v"}. A 503 may retry within the same deadline. After the bound, stop and report status plus UUID for the human to inspect; do not create another computer.
5. Every BOX command below goes through POST /computers/{id}/bash with a command string in JSON. Check HTTP status AND exit_code; HTTP 200 with nonzero exit_code is failure. Do not send a Takibi key in this JSON: it would be sent to Orgo and could enter tool payload logs. Pause for human terminal entry instead.

BOX / Orgo terminal. Use Bash as the same Unix user that will run Takibi.
Refuse to run a command while any <PASTE-KEY-HERE>, <ORGO-KEY-HERE>, or other unresolved placeholder remains in its inputs. These are labels, never values to save. Refuse to echo secrets, secret-bearing commands, or authorization headers. Never use set -x. Never put keys in chat, reports, screenshots, uploads, snapshots, or shell history. Keep the Orgo control key on the laptop.

1. Record whoami and printf '%s\n' "$HOME". The image user may be root or use /home/user. Confirm this is the user that will run Takibi; keep both key and skills in that user's home. Stop on a mismatch.
2. Gate 1: run node -v and npm --version. Require Node major 20 or newer and working npm. If either is missing or too old, stop and ask the human to provision them. Confirm permission to install global npm packages; on EACCES stop for a writable npm prefix, never silently switch users with sudo.
3. Run npm view takibibase version first and record the exact version. Stop on registry failure.
4. Gate 2: install that explicit version with npm i -g takibibase@<recorded version>, then run takibi --version. Require output exactly equal to the recorded version. Stop on install failure or mismatch. Expected output ("CLI"): takibi --version prints the recorded version, e.g. 1.21.0.
5. Inspect for local customization first: check SKILL.md under ~/.agents/skills/takibi-use, ~/.claude/skills/takibi-use, and ~/.codex/skills/takibi-use. Stop for review if any contains local edits. Otherwise run takibi skill --install --force --agents --claude --codex; --force deliberately replaces the installed takibi-use skill.
6. Pause for the human. They create a scoped key in the Takibi app and type it into the non-echoing input in the Orgo terminal, never into chat or a remote bash JSON request. Do not ask them to replace <PASTE-KEY-HERE> in this prompt. Use the guide's terminal-only key entry block. Never overwrite an existing key silently; on reruns preserve it and verify its grants. chmod 600 does not isolate agents sharing the same Unix user. The CLI reads $TAKIBI_KEY_FILE when set, else ~/.takibi/key. Report this handoff with filled values, never secrets: "Installation checks passed on computer <UUID>, running as <user>. Enter your key using the terminal block, then confirm completion and provide the expected collection, folder, and a harmless search phrase." At this pause, ask the human for the expected collection name, folder name, and a harmless search phrase from a known indexed document.
7. After the human confirms key entry, Gate 3: run takibi version, then takibi projects. The first checks the API and Jev, the evidence-scoring service, not the installed CLI. Expected output ("API/Jev"): takibi version prints e.g. takibi-api 1.2.3 · jev wired · via https://…. If TAKIBI_KEY_FILE is set to an unexpected path, stop: verification may be using a different key. Confirm the collections and grants are exactly those the human intended; the human confirms grants in the Takibi app under Settings → Profiles. Empty or unexpected grants are a stop. Select the intended collection UUID for the human-provided collection name and run takibi folders --project with that UUID. Select the intended folder UUID for the human-provided folder name, then run takibi search -q with the human-provided harmless phrase, --project with that collection UUID, and --folder with that folder UUID. Use actual validated values, never literal placeholders. Confirm a result from the expected document. If there is no result, stop and have the human check indexing and scope.
8. Report only the Unix user/home, CLI version comparison, API health, intended grant check, and scoped-read outcome. Never include credentials or document contents. Installing the CLI and skill does not install, authenticate, or start Claude Code, Codex, or another agent. The human chooses and starts that agent separately.

Failure rules: missing Node/npm or readiness timeout means stop. Orgo 400 missing workspace_id: fix the request; 401: check the laptop control key; 403 size or plan error: check account plan and computer size; 404 Desktop not found: verify the saved computer UUID; 409: check running state; 503: retry only within the readiness bound. A nonzero bash exit_code is failure even with HTTP 200. Empty collections: check the Takibi Profile's grants. 422 SECRET_BLOCKED: remove the secret, never bypass the filter. Notes 403: opt-in capability is missing. Boards 403 with a folder-only key: boards need a whole-collection grant. abstained: true can exit 0; it means there was no supported answer. Jev-down does not mean the app is down; search still works. Support measures evidence support, not confidence.

BOX / Orgo terminal. Use Bash as the same Unix user that will run Takibi.
Run the BOX steps from the laptop bootstrap prompt above, starting at step 1 ("Record whoami...") through step 8 and the failure rules. Skip the laptop preamble: no workspace lookup, no computer creation, no readiness polling — this computer already exists.
Refuse unresolved placeholders and never echo secrets, headers, or secret-bearing commands.

# TERMINAL / human only. Open Bash in the Orgo terminal.
# Type the key at the hidden prompt, never as a shell command or in chat.
# Refuse placeholders such as <PASTE-KEY-HERE>; preserve any existing key.
(
  set +x
  umask 077
  mkdir -p "$HOME/.takibi" || exit 1
  chmod 700 "$HOME/.takibi" || exit 1
  if [ -e "$HOME/.takibi/key" ] || [ -L "$HOME/.takibi/key" ]; then
    printf '%s\n' 'Key already exists. Review its grants; do not overwrite it.'
    exit 1
  fi
  IFS= read -r -s -p 'Takibi key (hidden): ' takibi_key
  printf '\n'
  case "$takibi_key" in
    ''|*'<'*|*'>'*) unset takibi_key; printf '%s\n' 'Empty key or placeholder refused.'; exit 1 ;;
  esac
  set -C
  printf '%s\n' "$takibi_key" > "$HOME/.takibi/key" || exit 1
  unset takibi_key
  chmod 600 "$HOME/.takibi/key"
)