codex-local-saas-browser

Prepares and verifies the CogDB SaaS HTTPS dev server on localhost:3000 for the Codex in-app browser.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/c2kaka/fancy-skills --skill codex-local-saas-browser-c2kaka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-local-saas-browser
Source: https://github.com/c2kaka/fancy-skills/tree/main/skills/codex-local-saas-browser
Command: npx skills add https://github.com/c2kaka/fancy-skills --skill codex-local-saas-browser-c2kaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Opening a local HTTPS SaaS frontend in the Codex in-app browser fails when certificates are untrusted, OIDC environment values are misconfigured, or another worktree owns port 3000. This Skill provides a deterministic, safety-checked workflow to prepare and verify the CogDB saas-frontend at https://localhost:3000 without weakening browser security. ## Core Features & Use Cases - Read-only preflight checks: Validates macOS platform, certificate fingerprints, OIDC .env values, port ownership, and HTTPS probes before any change. - Deterministic repairs: Normalizes four non-secret OIDC keys, generates the Vite basic-ssl certificate, and installs pinned public certificates into the macOS System keychain only after explicit user confirmation. - Browser handoff with verification: Starts the dev server, probes readiness, and hands off to the Codex in-app browser, verifying origin, path, and authenticated SaaS shell before claiming success. - Use Case: A developer needs to demo the CogDB SaaS console inside Codex. The Skill detects a missing Vite certificate, generates it, installs trust after confirmation, restarts the server, and confirms the authenticated page loads at https://localhost:3000/saas. ## Quick Start Ask the agent to use codex-local-saas-browser to prepare and open your local SaaS page in the Codex in-app browser, providing the absolute path to your saas-frontend checkout.

Frequently Asked Questions about codex-local-saas-browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open a local HTTPS SaaS app in the Codex in-app browser?▼

Run the skill's preflight check against your saas-frontend repo, repair any reported certificate or OIDC issues, start the server with start.sh, then probe for readiness. The workflow ends by navigating the Codex in-app browser to the verified https://localhost:3000/saas URL.

How do I fix an HTTPS certificate error on localhost:3000 in Codex?▼

The fix installs two public certificates into the macOS System keychain: the pinned CogDB certificate and the Vite basic-ssl certificate extracted from node_modules. After installation you must restart Codex so its browser process reloads system trust; bypassing the interstitial is never allowed.

Does this workflow work on Linux or Windows?▼

No, the scripts require macOS. The preflight explicitly checks for Darwin and depends on macOS tools like the security command and the System keychain for certificate trust management.

What happens if another worktree is using port 3000?▼

The check reports port_owner=other_worktree with the PID and working directory, then stops. The workflow never kills the occupying process or changes the redirect; the user decides how to proceed.

Can this skill handle arbitrary local web apps or other OAuth providers?▼

No, it is scoped to the CogDB saas-frontend with its exact OIDC issuer and the registered callback https://localhost:3000/console/oidc/callback. It is not intended for arbitrary local web apps or non-CogDB authentication setups.