Update to Autonom

{
  "description": "Install or hand off the Autonom harness — the CLI plus all skills — onto a new machine or into another agent. Build a single transferable bundle, copy it, install with one command, verify, and register it with Claude, Grok, or Codex. Triggers when setting up Autonom somewhere new, packaging it for handoff, or asking how to get it onto another device or agent.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 316
    }
  ],
  "name": "autonom-setup",
  "skill_md_contents": "---\nname: autonom-setup\ndescription: Install or hand off the Autonom harness — the CLI plus all skills — onto a new machine or into another agent. Build a single transferable bundle, copy it, install with one command, verify, and register it with Claude, Grok, or Codex. Triggers when setting up Autonom somewhere new, packaging it for handoff, or asking how to get it onto another device or agent.\n---\n\n# Autonom Setup\n\nAutonom is a plugin: 23 skills plus a dependency-free CLI they drive. This skill\npackages the whole thing into one file you can carry to another machine and\ninstall with one command — the skills travel with the CLI and land in whatever\nagent is there.\n\nNot a compiled binary, on purpose: the CLI is stdlib-only Python (nothing to\ncompile), and the network addon must be a real file on disk because `mitmdump`\nloads it by path. So the transferable artifact is a **tarball** — one file to\ncopy, one command to install.\n\n## Build the bundle\n\n```bash\n./scripts/build_release.sh\n# -> dist/autonom-<version>.tgz  (~200 KB: CLI + library + all skills + manifest)\n```\n\nThe bundle carries its own `install.sh`, so the target needs nothing but\n`python3` (already present on macOS and Linux) and, for real device work, the\ndevice tools (`adb`, `xcrun`, `idb`, `mitmdump`) that `doctor` checks.\n\n## Install on another machine\n\nCopy `dist/autonom-<version>.tgz` over any transport, then:\n\n```bash\ntar xzf autonom-<version>.tgz\n./autonom-<version>/install.sh          # checkbox picker: tools, Claude, Codex, Grok\n./autonom-<version>/install.sh --all    # headless: everything\n./autonom-<version>/install.sh claude   # or any explicit subset\n```\n\n`install.sh` copies the bundle to a stable home (`AUTONOM_PREFIX`, default\n`~/.local/share/autonom`) so the extracted folder can be deleted afterwards,\nputs `autonom` on `PATH`, installs the selected device tools and agents, and\nverifies with `autonom doctor`. Headless runs never prompt — no flags means\nCLI only. Overrides: `AUTONOM_PREFIX`, `AUTONOM_BIN_DIR`.\n\n## Into each agent\n\n`install.sh <target>`, or run the layer directly:\n\n```bash\n./scripts/install_claude.sh              # Claude Code plugin (marketplace + install)\n./scripts/install_codex.sh               # Codex plugin (marketplace + add)\n./scripts/install_skills.sh grok         # ~/.grok/skills\n./scripts/install_skills.sh --link <dir> # any skill-root, by symlink\n./scripts/install_skills.sh --copy <dir> # by copy (no live repo)\n```\n\nClaude and Codex install Autonom as a **plugin** from the bundle's marketplace\nmanifests and copy it into a versioned cache. After the source changes, re-run\nthe script — or `claude plugin update autonom@autonom` /\n`codex plugin add autonom@autonom` — so the cache catches up; the version is\nbumped on every release exactly so those caches notice. Skills load namespaced\n(`autonom:mobile-network`). Without the `claude` CLI the Claude path falls back\nto loose `autonom-*` skills in `~/.claude/skills`.\n\n## Verify it actually works\n\n`doctor` reports what is present; a green install still means *installed*, not\n*proven*. Confirm the chain end to end on a connected device:\n\n```bash\nautonom doctor                     # tools + capabilities + session + orphans\nautonom devices                    # a real device/simulator is listed\nautonom session start --platform android --target <id>\nautonom ui tree --max-nodes 5      # a real tree comes back\nautonom session stop\n```\n\nIf any step fails, `doctor`'s per-tool `state` and install hint name what is\nmissing — do not proceed as if it worked.\n\n## Knowledge stays behind\n\nThe bundle ships the **skills**, not the per-app knowledge under\n`~/.autonom/apps/` (see `mobile-memory`). That store is machine-local and\nper-person; it accumulates on each machine as work happens and is not part of\nthe handoff.\n\n## Related\n\n- `mobile-session`, `mobile-screen`, `mobile-network` — the verbs the CLI exposes.\n- `mobile-memory` — per-app knowledge, kept out of the bundle on purpose.\n- `toolchain-doctor` — reading `autonom doctor` output.\n"
}