admin

builds

"🛠 build to dev" on a feedback message (or ＋ below) asks Claude to build it on the dev branch. Within about an hour it's on staging with a note here on how to try it. Try it there, then 🚀 release to live (Claude ships just that change to irreg.dev with a release note), ✎ ask for changes, or ✕ drop it. Needs HELP_GITHUB_TOKEN in this environment.

feedback

widgets to review

Home widgets made in the widget lab (feature "widgets"). Read the code, check the findings and try it: it runs in the same sealed box as on home, with your own data. Approving pins this exact code (its SHA-256): people only ever run what you approved. Switch a widget off to take it off everyone's home at once.

all widgets

questions search couldn't answer

Questions people typed into search (Ctrl+K) that the "how do I" list (public/xhelp.js) didn't match, and what "ask irreg" said. No accounts are kept. Add the missing words to an entry's k, or a new entry, so the list catches them next time.

walk-throughs ask irreg made

When nothing on the list fits, ask irreg walks the person through it live, one click at a time. Ones that got to the end (and weren't a 👎) are kept here and replayed for the same question with no AI. Remove any that go somewhere wrong.

did walk-throughs help?

script errors

Errors that happened in people's browsers (lib/clienterrors.js). The same error is counted once per page and line, with how many people hit it.

on irreg now

Everyone with irreg open in the last few minutes, guests too. Only you see this.

accounts

feature access · pages only the people you add here can open

Add the Google email they sign in with. It works before they've ever signed in, and it's in their menu on their next visit. You (admins) always have every feature.

tester codes

Tester codes are for the staging copy, where the tester gate is on. Open /admin on staging to make and revoke them. (The gate is off here because TESTER_CODES isn't set.)

supporters

gallery

prompt events · an official #tag with a prompt a day, shown in the gallery (/g)

Posts to it carry the tag and #day1, #day2… Each day's prompt shows in the gallery from that day on (in the time zone above); people can still post to a past day for a week after the end.

changelog · shown on /changelog, and once as a popup to everyone when you publish

usage

referral links

A link per streamer or creator you sponsor. It counts visits, and every NEW account made within 30 days of a visit (people who already had one aren't counted). "Still using" = opened irreg in the last 7 days. The landing page greets visitors for them: with their irreg page set (public, with posts) it shows their art made in irreg, otherwise "support them by using irreg".

storage

backups

Loading…

your live data here · test version only

Copies your account from irreg.dev into this test version, so you can try things on your real data. Download a backup on irreg.dev/admin → server → backups, then pick it here. Only the account with the email below is taken from it (yours unless you type another, like the account you test with); other accounts here aren't touched. What that account has here now is replaced. Nothing is sent to irreg.dev.

Riot API key · for TFT match history

…

Kept encrypted on this server and never shown again, only its last 4 characters. Development keys expire every 24 hours: paste the new one here. This copy of the site has its own key (the test version and irreg.dev are set separately).

Discord · alerts and the gallery feed

Paste a webhook link from a Discord channel (the channel's ⚙ → Integrations → Webhooks → New Webhook → Copy Webhook URL). The links are kept encrypted on this server and never shown again.

This copy of the site has its own (the test version and irreg.dev are set separately; messages from the test version start with its name).