Build with a user ID, proof, and support loop

Prepare the exact Codee commands for a client workspace.

Enter the client basics once. Codee turns them into the command path for identity, course output, route scans, payment, delivery room, and update requests.

Identity tied to workspace Stripe-hosted payment path Delivery room return route Support packet proof Optional browser scan

Client setup

Command inputs

Business name Owner email Client ID Codee user ID Course Service Target URL Plan Priority Support request

Download CLI

Codee is ready to install as a web app.

Generated command path

Run these in order

What this proves

Codee exists as the business layer around the AI tool.

The user can build with Claude, OpenAI, Gemini, a local editor, or Codee Chat. Codee keeps the client ID, payment proof, route scan, delivery room, and support request together.

1. Identity`codee init` creates a local workspace and stable Codee user ID.

2. Output`course-init` exports a teachable QR, flyer, or app starter folder.

3. Proof`scan` and `course-smoke` catch 404s and save report files.

4. Support`support` creates update packets that can submit to Codee backend.

Prepare the exact Codee commands for a client workspace.

Command inputs

Run these in order

Codee backend task status

Codee exists as the business layer around the AI tool.