🏠 Portal 🧭 Setup 👀 Preview 🧾 Logs 📝 Shared Notes ✅ Task Board 🎮 Mini Games ⭐ Subscribe 🚀 GitHub

AI co-pilot

OpenAI Workbench

Bring your own OpenAI API key, chat with GPT-4o, and share transcripts through GunDB.

Instructions

Deployment guide hub

Step through GitHub PATs, Vercel tokens and IDs, and alias setup without leaving the Workbench.

Open guides

Opens in a new tab so you can paste secrets directly into the panels below.

Workflow

Setup, preview, and logs

Use these hubs to keep PRs, deploys, and publish steps aligned.

🧭 Setup 👀 Preview 🧾 Logs

Shared defaults + account keys

Load team defaults fast, then swap in personal tokens when you are ready.

Quick start

Use shared defaults

Admins can publish shared OpenAI, Vercel, and GitHub keys. Apply them here to start building fast.

    Guide: setup checklist Guide: add secrets to CI

    Saved to your Gun account first when available; otherwise stored on this device.

    Sign in so keys attach to your account instead of this device.

    Shared keys are rate limited: guests 2/day, accounts 5/day, supporters 20/day, pro members 100/day.

    Compose

    Chat with Codex

    Pick a model, type a prompt, and stream the reply into the shared history.

    Guide: Workbench flow
    Waiting for response...

    Prototype

    Live preview

    Apply HTML/CSS answers in a sandbox to test ideas before committing them.

    Guide: Preview tips

    Publish

    Deploy to Vercel

    Turn the current response into a live site by deploying a static index.html.

    Guide: Vercel token Guide: Dev alias

    Token stays in localStorage; the deployment request is proxied through this domain. Need the steps?

    Letters, numbers, and dashes only. A new Vercel project will be created if needed.

    Paste your token and project name to start.

    Commit

    Publish to GitHub

    Save the generated HTML into a repository so teammates can track changes.

    Guide: GitHub token Guide: Create repo

    Token stays in localStorage; commits use the GitHub contents API. Open the guide for PAT scopes.

    Seeing “Resource not accessible by personal access token”? Confirm the token targets the right owner, has read/write contents scope, and is SSO-authorized in your org. The GitHub token guide lists the full checklist.

    New repo

    Create directly from the Workbench

    Use the same token to spin up a GitHub repository without leaving this page. Leave the name blank to auto-generate one.

    Letters, numbers, and dashes. Owner comes from the radio buttons above. Leave empty to auto-name.

    Required only when creating inside an organization.

    Paste a token above to start.

    The repo must already exist and your token must grant contents access.

    Add your token and repo to push HTML.

    Record

    Recent commits

    Saved to ai/github/<sessionId> in Gun to track publish events.

    Guide: CI secrets & workflow

      Reuse

      Shared transcript

      Entries are stored at ai/workbench/<sessionId> in Gun so teammates can find successful prompts.

      Guide: Share with the team

      Audit

      Recent deployments

      Saved to ai/vercel/<sessionId> in Gun so the team can reuse URLs.

      Guide: Wire CI and previews

      Backup

      Gun secret vault

      Optional encrypted vault for when you need a passphrase-based backup beyond your account.

      Guide: Backup and sync secrets

      Letters, numbers, and dashes only. Defaults to your account handle when signed in.

      Passphrase never leaves the browser; it only decrypts your secret locally.

      Choose which field to pull from and where the decrypted secret should be applied.

      Enable auto-sync to encrypt secrets immediately after you save them.

      Use the vault when you need a passphrase-protected backup alongside your account.