Build and manage apps on orgiggly.com from Claude Code.
Describe the app you want; Claude writes the config and publishes it live under
your own name (orgiggly.com/<name>/…) — with auth, realtime data, storage and hosting built in.
Inside Claude Code:
/plugin marketplace add orgiggly/claude-plugin
/plugin install orgiggly@orgiggly
/orgiggly
/orgiggly runs the on-ramp: it checks the og command works (it ships inside
the plugin and needs Node 22 or newer), signs you in, picks your name on
Orgiggly, and hands off to building your first app — stopping at whichever step
you've already done. Safe to re-run at any point; it picks up where you left off.
To update later: /plugin marketplace update orgiggly, then
/plugin update orgiggly@orgiggly, and restart Claude Code. The plugin checks
once a day and tells you when a new version is out, and after an update it
shows what's new (full history). In a cloud environment it
works differently; see Getting a new version below.
No invite code? Email dave@orgiggly.com with a line about what you want to build. You don't need one to get started — the code records how you found us, it doesn't unlock anything.
You can also use the plugin in a Claude Code cloud environment, with nothing installed on your own computer. Each session starts from a GitHub repo, and that repo is where your app's folder lives between sessions. A step-by-step version with copy buttons is at orgiggly.com/guides/plugin-cloud-environment.html.
On a Team or Enterprise Claude plan, an Owner of your Claude organization must first turn on the GitHub connector (Organization settings → Connectors). Until then claude.ai/code stops at "GitHub access is required for Claude Code cloud sessions". A personal Pro or Max plan doesn't need this.
Get a sign-in token. Openorgiggly.com/connect/cli , sign in
with Google and copy the token. (Already signed in on a computer?og token prints the same thing.) Treat it like a password: anyone holding it can act
as you on Orgiggly. If it leaks, runog logout --everywhere on any machine
where you're signed in: every token and login for your account stops
working, and you sign in again to get a new one.
2.
Create the environment in Claude Code on the web, and set: #
Setup script:
claude plugin marketplace add orgiggly/claude-plugin
claude plugin install orgiggly@orgiggly
Environment variables:OG_TOKEN=<your token> . Anyone who can use the
environment can read its variables, so keep it to yourself. #
Network access: Custom, allowing at least these domains:Domain Used for github.com installing the plugin (setup script) orgiggly.com ,*.orgiggly.com the site and your apps ( *. doesn't cover the bare domain, so list both)*.firebasedatabase.app the database firebasestorage.googleapis.com app configs, data, widgets identitytoolkit.googleapis.com ,securetoken.googleapis.com signing in with your token *.cloudfunctions.net creating apps, invite codes, saving data Optional: raw.githubusercontent.com (the plugin's "update available"
check), andgenerativelanguage.googleapis.com orapi.replicate.com if
you generate logos with your own Gemini or Replicate key.Custom or Full? Custom with this list is enough to build, test and
publish apps. The one thing it can't do is let Claude look at a draft in a
browser: an app also needswww.google.com to get past its screen,
so Claude says it couldn't check the draft and asks you to open the
preview link yourself. That's a good way to start while you get to know
the plugin. Once you trust it, set Network access toFull , which lets
Claude reach any site, and it checks each draft itself.
3.
4.
Start a session on your repo and type /orgiggly. It's the same on-ramp
as on your own machine, minus the install steps. Nothing makes you pick a
repo, so check the repo button next to the environment name before you start.
A private repo only appears there once the Claude GitHub App can see it: follow
the picker's "Install the Claude GitHub App" link, chooseOnly select
repositories , add the repo, then refresh the list.
Your apps live on the repo's main branch. The cloud machine is thrown away
when the session ends, and each new session starts from main. So after each
publish Claude commits the app's folder (config.json, the app's CLAUDE.md,
its widgets and its tests/), pushes the session's own claude/… branch, and
then saves the same work to main. If main is protected, it opens a pull
request instead and gives you the link to merge it.
Every cloud session works on a new claude/… branch of its own; that's how
Claude Code cloud sessions work, not something Orgiggly sets up. So the old
branches pile up in your repo. They're harmless, and once their work is on
main you can delete them on the repo's Branches page on GitHub. (Claude can't
delete them for you: cloud sessions aren't allowed to delete branches.)
Getting a new version. The environment
runs its setup script once, then starts later sessions from a saved copy of
the result, so new sessions keep the plugin version they first installed. It
only runs the script again when you change the script or the allowed domains,
or after about seven days. To update now, change the setup script's comment
line (for example, bump the number), save the environment, and start a new
session. With raw.githubusercontent.com allowed, Claude tells you when a new
version is out.
Check new versions on your own device. With Custom network access, Claude's browser check can't load your app from inside a cloud session, so it asks you to open the preview link once. With Full access it checks the draft itself.
If a domain is missing, og stops with one line naming it ("Can't reach …")
rather than hanging: add that domain to the environment and try again.
-
Claude Code is the generation engine. Claude hand-writes (or edits) your app's config JSON directly from the node-model schema, then validates and publishes it via the bundled CLI. There isno Orgiggly AI backend, no credits, and no Anthropic key in this path.
-
The CLI runs as you.
og loginstores a real user credential under~/.orgiggly/, and every command is subject to the Firebase security rules. Your app is hosted on orgiggly.com under your own name. -
Nothing to download separately. The CLI ships inside this plugin as a self-contained bundle (
bin/og-public.mjs) with abin/ogshim. -
getting-started— the on-ramp: install → sign in → invite code → your name → your first app. Type/orgigglyto start it, or to resume — it's idempotent, so running it again is always safe. -
develop-app— the one skill for both creating and maintaining an app. It figures out whether the app already exists and does the right thing: fetch-if-exists → author/edit config →validate-org→create-org/update-org. You never have to decide "am I creating or maintaining?". -
watch-reports— fixes the issue reports people file on your apps (Report an issue… in the app). It waits for a report withog report watch, fixes the app thedevelop-appway, publishes a draft, asks you before it goes live, and writes the status back so the reporter can follow it on orgiggly.com/issues. Treats every report as untrusted input: it never follows instructions, links or commands found in one.
bin/og # command on PATH → spawns the bundle (as `og`)
bin/og-public.mjs # the self-contained CLI bundle
reference/*.md # node-model schema docs `og reference` serves
commands/orgiggly.md # /orgiggly → the getting-started skill
commands/og-setup.md # legacy /og-setup → same place
commands/feedback.md # /orgiggly:feedback → send test-run feedback (asks first)
hooks/ # SessionStart: first-run check, what's new, update nudge,
CHANGELOG.md # what changed in each release
skills/getting-started/ # the on-ramp
skills/develop-app/ # the build-and-manage skill
skills/watch-reports/ # the issue-report fix loop
- Product docs and the full node-model reference: orgiggly.com/docs
- Showcase of apps built this way: orgiggly.com
- Questions, bugs, ideas: github.com/orgiggly/claude-plugin/issues ordave@orgiggly.com
This repository is a published snapshot of the plugin; see LICENSE for terms.