IntelligenceX

Web Onboarding Flow

Edit on GitHub

Understand the local web onboarding flow, shared path contract, and apply commands for new setup, auth refresh, cleanup, and maintenance.

Web Onboarding Flow

This flow runs locally and never uploads tokens to a backend.

Canonical Path Contract

CLI, Web, and Bot all use the same path contract in SetupOnboardingContract .

Path IDDefault OperationGitHub AuthRepo SelectionAI AuthTypical Apply Command
new-setupsetupRequiredRequiredRequiredintelligencex setup --repo owner/name --with-config
refresh-authupdate-secretRequiredRequiredRequiredintelligencex setup --repo owner/name --update-secret --auth-b64 <base64>
cleanupcleanupRequiredRequiredOptionalintelligencex setup --repo owner/name --cleanup
maintenancesetupRequiredRequiredOptionalintelligencex setup web

Path Flow Diagram

flowchart TD
  classDef trigger fill:#38BDF8,stroke:#0369A1,color:#082F49,stroke-width:2px;
  classDef path fill:#A7F3D0,stroke:#047857,color:#052E2B,stroke-width:2px;
  classDef auth fill:#FDE68A,stroke:#B45309,color:#451A03,stroke-width:2px;
  classDef apply fill:#E9D5FF,stroke:#7C3AED,color:#2E1065,stroke-width:2px;
  classDef decision fill:#FBCFE8,stroke:#BE185D,color:#500724,stroke-width:2px;

  A["Start intelligencex setup web"] --> B["Run doctor auto-detect"]
  B --> C{"Choose path"}

  C --> D["new-setup"]
  D --> D1["GitHub auth required"]
  D1 --> D2["Repo selection required"]
  D2 --> D3["Configure reviewer and workflow"]
  D3 --> D4["AI auth required"]
  D4 --> D5["Plan apply verify setup"]

  C --> E["refresh-auth"]
  E --> E1["GitHub auth required"]
  E1 --> E2["Repo selection required"]
  E2 --> E3["AI auth required"]
  E3 --> E4["Plan apply verify update-secret"]

  C --> F["cleanup"]
  F --> F1["GitHub auth required"]
  F1 --> F2["Repo selection required"]
  F2 --> F3["Cleanup options"]
  F3 --> F4["Plan apply verify cleanup"]

  C --> G["maintenance"]
  G --> G1["GitHub auth required"]
  G1 --> G2["Repo selection required"]
  G2 --> G3["Inspect workflow config and secrets"]
  G3 --> G4{"Choose operation"}
  G4 --> D5
  G4 --> E4
  G4 --> F4

  class A,B trigger;
  class C decision;
  class D,E,F,G path;
  class D1,D2,D4,E1,E2,E3,F1,F2,G1,G2 auth;
  class D3,E4,F3,G3,G4 apply;
  class D5,F4 apply;

Bot Contract-Check Flow

.Chat + .Tools should validate contract metadata before mutating setup:

flowchart LR
  classDef bot fill:#BAE6FD,stroke:#0369A1,color:#082F49,stroke-width:2px;
  classDef verify fill:#FDE68A,stroke:#B45309,color:#451A03,stroke-width:2px;
  classDef ok fill:#A7F3D0,stroke:#047857,color:#052E2B,stroke-width:2px;
  classDef stop fill:#FECACA,stroke:#B91C1C,color:#450A0A,stroke-width:2px;
  classDef decision fill:#DDD6FE,stroke:#5B21B6,color:#2E1065,stroke-width:2px;

  A["reviewer_setup_pack_info"] --> B["setup autodetect --json"]
  B --> C["reviewer_setup_contract_verify"]
  C --> D{"Metadata matches"}
  D -->|yes| E["Run setup update-secret or cleanup command"]
  D -->|no| F["Stop and request contract/tool update"]

  class A,B,C bot;
  class D decision;
  class E ok;
  class F stop;

Steps

  1. Start web UI: intelligencex setup web
  2. Run auto-detect first and review suggested path.
  3. Confirm path requirements shown in step 1.
  4. Authenticate with GitHub and select repositories.
  5. Plan, then apply.

Notes

  • Auto-detect response includes contractVersion , contractFingerprint , paths, and command templates.
  • Web step-1 path hints are derived from contract metadata to reduce CLI/Web drift.