Route Scan
Checks public URLs and writes proof before a service is called ready.
Codee SkillsPlatform tool layer
Skill registry
Public skills run safely on the user machine. Optional skills detect local tools. Backend and owner skills stay credential-gated so Codee can be powerful without leaking access.
Codee is ready to install as a web app.
python3 codee.py skills --access public python3 codee.py toolkit-init ./codee-open-source-toolkit --business "My Business" --force python3 codee.py toolkit-smoke ./codee-open-source-toolkit python3 codee.py admin-training . --write python3 codee.py folder-plan ./my-service --business "My Business" --service codee-course --write --force python3 codee.py domain-plan ./my-service --domain example.com --target-url https://example.com --write --force python3 codee.py business-assistant-init ./restaurant-assistant --business-type restaurant --business "My Restaurant" --force python3 codee.py skill-policy ./my-business --preset operator --force python3 codee.py skill-check browser-scan . python3 codee.py browser-scan . --url https://clients.codee.chat/codee-workbench.html --full-page python3 codee.py skills --access owner
Public and optional
Checks public URLs and writes proof before a service is called ready.
Creates and validates QRCodee, Codee Flyer, and Codee App course outputs.
Writes `.codee/skills.json` and `SKILLS.md` so each workspace has enforceable tool boundaries.
Inspects a service folder and writes what is missing before hosting or support.
Explains registrar, DNS, hosting, SSL, redirects, and route proof in plain language.
Uses local Node/npx and Playwright to screenshot the real browser page.
Ties account, workbench, delivery room, and update requests to one workspace ID.
Creates checkout and invoice links through Codee backend, not local card storage.
Uses exported folders and attachments to support Codee App and guidebook lanes.
Owner and private
Deploys Codee-owned pages only with owner-approved Firebase credentials.
Deploys and checks backend services only from authenticated owner environments.
Mailbox and notification tools stay behind private connector authorization.
Social scheduling uses connected owner accounts and scheduled proof reports.