Update to Qodo

{
  "name": "qodo-setup",
  "description": "Set up Qodo in a coding agent — install the CLI, sign in, and verify tools. Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 344
    },
    {
      "relative_path": "references/authentication.md",
      "size_in_bytes": 3062
    },
    {
      "relative_path": "references/host-recovery.md",
      "size_in_bytes": 1059
    },
    {
      "relative_path": "references/runtime.md",
      "size_in_bytes": 4838
    },
    {
      "relative_path": "references/skill-updates.md",
      "size_in_bytes": 1663
    }
  ],
  "skill_md_contents": "---\nname: qodo-setup\ndescription: Set up Qodo in a coding agent — install the CLI, sign in, and verify tools. Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login.\nowner: Qodo\nmetadata:\n  vendor: qodo\n  version: \"1.0.8\"\n  recommended: \"true\"\n  package: \"qodo\"\n  distribution: \"marketplace\"\n  instruction_mode: \"embedded\"\n---\n\n# Set up Qodo\n\n## Description\n\nInstall, connect and verify Qodo in this conversation. Plugin installation does not connect an account.\n\n## Prerequisites\n\nA shell and browser sign-in. Never request or read credentials.\n\n## Instructions\n\nResolve `references/...` links relative to this installed `SKILL.md` directory.\nRuntime/login setup does not authorize enterprise installation or maintenance.\nFor a separately requested enterprise install, disclose selected installations, packages and verified-source\nautomatic maintenance before approval. Preserve opt-outs, edits, owners and optional-package choices.\n\n### 1. Find or install the runtime\n\nRun:\n\n```sh\nqodo --version\n```\n\nIf missing, try `\"${QODO_HOME:-$HOME/.qodo}/bin/qodo\" --version` on POSIX.\nFor PowerShell or a missing CLI, read [runtime.md](references/runtime.md).\nFollow that procedure and continue. Setup requests cover CLI installation, subject to host\napprovals and user restrictions. Plugin installation alone is not authorization.\n\nKeep the working executable as `<qodo>`. Require Qodo CLI **0.1.0-next.37 or newer**.\nIf older or unparseable, follow the runtime reference before any authenticated command.\n\n### 2. Connect\n\nRun:\n\n```sh\n<qodo> read whoami --json --skill qodo-setup --skill-version 1.0.8 --distribution marketplace --host codex\n```\n\nIf successful, retain the verified identity and continue to step 3 without repeating it.\nFor a failed check, read [authentication.md](references/authentication.md) to distinguish\nmissing credentials, sandbox access, and other failures before choosing login.\n\nFor Qodo Cloud, announce and run `<qodo> login` when signed out. For any customer deployment,\nread the authentication reference first: preserve its exact login endpoint and never guess\nor fall back to Cloud. Wait for login to finish, then rerun the identity command above.\nBrowser opening alone is not success.\n\nRemember the execution context where identity or login worked. Use that context for later\ncredential-dependent commands, requesting each required host approval; a diagnostic approval\ndoes not grant blanket permission. Do not repeat a known-failing sandbox probe after login.\nStop on cancellation or denied permission.\n\n### 3. Verify tools\n\nOnly after identity succeeds, run:\n\n```sh\n<qodo> tools --refresh --json --skill qodo-setup --skill-version 1.0.8 --distribution marketplace --host codex\n```\n\nRequire a successful, nonempty usable catalog. Inspect structured results with bounded output\n(exit status, error, tool count and relevant names); do not dump every tool schema.\nIf refresh fails, report that sign-in succeeded but tools are unavailable, with the exact error\nand `<qodo> tools --refresh` as the retry. Do not log in again for a catalog failure.\n\n## Configuration\n\nThe CLI owns credentials, transport and runtime updates; the package's\nlifecycle owner updates skills. For `QODO_NOTICE` updates or repeated Kiro read approvals,\nread [host-recovery.md](references/host-recovery.md) only when encountered.\n\n## Error Handling\n\nGive the actual error and one next action. Never report readiness after a failed\nidentity, canceled login or unavailable catalog. Never disable the keychain, copy credentials,\nchange host permission files, or offer unrestricted command approvals to make setup pass.\n\n## 4. Hand off\n\nConfirm verified readiness in plain prose, then suggest one next action supported by the\ncatalog and loaded skills, e.g. “Qodo is connected and ready. Ask ‘Explain this codebase.’”\nMention account or deployment when useful. Omit routine versions, counts and repeated summaries.\nDo not launch another workflow or install optional Standards during setup.\n"
}