← AnsightCONTENT HISTORY

Update to Ansight

Snapshot Sep 30, 2026 · 23:15 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "ansight-install-ios",
  "description": "Install the native iOS Ansight SDK with automatic Simulator registration and one-shot CLI QR enrollment for physical devices. Add the aggregate SwiftPM product or pod, initialize from app startup, expose the SDK scanner from a developer-only surface, add only Apple-required privacy descriptions, verify the build, and inspect the app through the Ansight CLI.",
  "included_files": [],
  "skill_md_contents": "---\nname: ansight-install-ios\ndescription: Install the native iOS Ansight SDK with automatic Simulator registration and one-shot CLI QR enrollment for physical devices. Add the aggregate SwiftPM product or pod, initialize from app startup, expose the SDK scanner from a developer-only surface, add only Apple-required privacy descriptions, verify the build, and inspect the app through the Ansight CLI.\n---\n\n## OpenAI plugin integration\n\nRun Ansight CLI commands using the execution tools in ChatGPT Work or Codex on the machine that owns the resident host. If this environment cannot execute commands or reach that host, explain the missing prerequisite and do not claim a live inspection succeeded. A remote workspace or cloud agent does not automatically have access to the developer’s local host. Resolve relative helper paths from this skill’s directory. When this workflow references another bundled skill, read its local SKILL.md completely before following it.\n\nUse these bundled files for the canonical skill URLs referenced below; keep public URLs when writing documentation for the user’s app:\n\n- https://www.ansight.ai/skills/agents/ansight-app-inspection.md → [ansight-app-inspection](../ansight-app-inspection/SKILL.md)\n- https://www.ansight.ai/skills/ios/ansight-app-inspection-ios.md → [ansight-app-inspection-ios](../ansight-app-inspection-ios/SKILL.md)\n\n\n# Ansight iOS Install Skill\n\nUse this skill for native SwiftUI or UIKit apps.\n\n## Outcome\n\nThe finished app must:\n\n- link the aggregate `Ansight` product for local development;\n- initialize `AnsightRuntime.shared` once from app startup;\n- register automatically in Simulator or Mac Catalyst and expose the SDK QR\n  scanner from a developer-only UI for physical devices;\n- reconnect automatically after the first successful scan;\n- add only the privacy descriptions required by the chosen flow; and\n- require no generated JSON, build setting secret, certificate, or manual app\n  registration.\n\n## Workflow\n\n1. Identify the app target, bundle id, startup delegate, dependency manager,\n   debug configuration, and existing developer menu.\n2. Add the aggregate SwiftPM product:\n\n```swift\n.package(\n    url: \"https://github.com/ansight-ai/ansight-sdk.git\",\n    exact: \"1.4.0-preview.1\"\n)\n```\n\n   Use `pod 'Ansight', '1.4.0-preview.1'` when the project already uses\n   CocoaPods.\n3. Keep both the import and initialization behind the app's Debug or explicit\n   internal-build compilation condition. Initialize once:\n\n```swift\n#if DEBUG\ntry AnsightRuntime.shared.initializeAndActivateAnsightSdk()\n#endif\n```\n\n4. Add a developer-only scanner action:\n\n```swift\nlet result = await AnsightRuntime.shared.connect(\n    .qrCode(title: \"Scan Ansight Enrollment QR\")\n)\n```\n\n5. Add `NSCameraUsageDescription` because the SDK scanner uses the camera. Add\n   `NSLocalNetworkUsageDescription` for physical devices connecting to the CLI host.\n   Do not add Bluetooth, location, contacts, photos, Bonjour, or ATS clear-text\n   exceptions.\n6. Keep reflection, secure-storage access, writes, and deletes disabled unless\n   the requested development workflow requires them.\n7. Create or update `ansight-readme.md` with the scanner location, build\n   verification command, and CLI enrollment commands. Do not add an enrollment\n   payload or token to it.\n8. Build the relevant simulator and, where practical, physical-device target.\n9. Start or reuse the resident CLI host. Simulator and Mac Catalyst builds\n   register automatically. For a physical device, issue one generic host QR and\n   scan it from the developer-only surface:\n\n```sh\nansight host run\nansight pairing issue --qr\nansight session list --connected --app-id <app-id> --json\nansight app tools <session-id> --detail summary --include-unavailable --max-results 50 --json\n```\n\n   Do not require `ansight app register` before the first connection. After the\n   SDK supplies its real App ID, optionally link the discovered app to the\n   repository with `ansight app register <app-id> --codebase <repository-path>`.\n\n## Enrollment Behavior\n\nSimulator and Mac Catalyst register automatically through loopback. The first\nphysical-device scan registers the app installation and stores a random installation\nid and enrollment state privately. Later developer launches reconnect\nautomatically. The client uses Network.framework for its local clear-text\n`ws://` development connection, so no ATS exception or certificate is needed.\n\n## Recommended Inspection Skills\n\nUse the main router to select the core inspection workflow. Add the native iOS\ncompanion only when SwiftUI, UIKit, or Apple-platform semantics are material:\n\n```text\nhttps://www.ansight.ai/skills/agents/ansight-app-inspection.md\nhttps://www.ansight.ai/skills/ios/ansight-app-inspection-ios.md\n```\n"
}

SHA-256: e1582cfb64169d9440646701a775c05085a78b4b0c968808998a6da3e156848d