Orgiggly · Claude Code plugin

Orgiggly in a Claude Code cloud environment

Build Orgiggly apps from your browser, with nothing installed on your computer. You set up a cloud environment once, and every session in it starts with the plugin installed and you signed in. Your apps' files live in a GitHub repo, so they're still there next time.

About 10 minutes, once. Every dark box below has a Copy button: copy it, paste it exactly where the step says, and change nothing unless the step tells you to.

  1. 1

    What you'll need

    • A paid Claude plan with Claude Code on the web (Pro, Max, Team, or an Enterprise seat that includes Claude Code).
    • Claude Code on the web set up with your GitHub account. If you've never used it, open claude.ai/code and follow its onboarding first.
    • On a Team or Enterprise plan, an Owner of your Claude organization must first turn on the GitHub connector. Without it, onboarding stops at "GitHub access is required for Claude Code cloud sessions" and only an Owner can fix that (see the end of this page). A personal Pro or Max plan doesn't need this.
    • A Google account to sign in to Orgiggly with. It becomes your Orgiggly identity, so it doesn't have to be your main one.
  2. 2

    Make a GitHub repo for your apps

    on github.com

    Each cloud session starts from a GitHub repo, and that repo is where your apps' files are kept between sessions.

    1. On GitHub, create a new repository (github.com/new). Name it, for example: 
      my-orgiggly-apps
    2. Private is fine. Tick Add a README file, so the repo isn't empty, then Create repository.

    A private repo only shows up in Claude's repo list once the Claude GitHub App can see it. You'll do that in step 5, from the repo picker.

  3. 3

    Get your Orgiggly token

    on orgiggly.com
    1. Open orgiggly.com/connect/cli and select Sign in, using the Google account you want to build with.
    2. Leave this tab open. Partway through step 4 you'll come back and select Copy my token, which copies it without showing it on screen.

    Treat the token like a password. Anyone who has it can act as you on Orgiggly. Don't paste it into a chat with Claude, an email or a shared doc; it only goes in the environment's settings below.

  4. 4

    Create the cloud environment

    on claude.ai/code
    1. Open claude.ai/code. In the row of controls under the message box, select the first one (the environment selector), then New environment at the bottom of the menu.
    2. Fill in the four parts of the New environment dialog:
    Name
    Orgiggly
    Network access · choose Custom

    Tick Also include default list of common package managers. Then paste this into Allowed domains, one per line as it is:

    orgiggly.com
*.orgiggly.com
*.firebasedatabase.app
*.cloudfunctions.net
    Rather not tick the default list?

    The default list already covers GitHub and Google's APIs, which Orgiggly uses for files and sign-in. Without it, paste this longer list instead:

    orgiggly.com
*.orgiggly.com
*.firebasedatabase.app
*.cloudfunctions.net
firebasestorage.googleapis.com
identitytoolkit.googleapis.com
securetoken.googleapis.com
github.com
raw.githubusercontent.com

    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 needs www.google.com to get past its loading 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 Orgiggly. Once you trust it, choose Full instead, which lets Claude reach any site, and it checks each draft itself.

    Setup script

    This installs the Orgiggly plugin. The environment runs it once and starts later sessions from a saved copy of the result:

    #!/bin/bash
# orgiggly plugin: change this line to pick up a new version (1)
claude plugin marketplace add orgiggly/claude-plugin
claude plugin install orgiggly@orgiggly
    Environment variables

    Copy this line and paste it into Environment variables:

    OG_TOKEN=

    Then go back to the orgiggly.com tab from step 3, select Copy my token, and paste it straight after the =: no space, no quotes.

    It should end up as one line: OG_TOKEN=og1. followed by the rest of your token.

    Anyone who can use this environment can read its variables. Keep the environment to yourself; don't share it with a team.

    1. Select Add environment.
  5. 5

    Start a session and build

    on claude.ai/code
    1. On the new-session screen, pick the Orgiggly environment, then click the repo button next to it and pick my-orgiggly-apps. Nothing makes you choose a repo, so check it's there before you send anything.
    2. If your repo isn't in the list, click Install the Claude GitHub App under it, choose Only select repositories, add my-orgiggly-apps and save. Back on claude.ai/code, refresh the repo list.
    3. Send this as your first message: 
      /orgiggly
    4. Claude checks you're signed in. The first time, it helps you pick your name on Orgiggly (2 to 20 letters, digits or underscores); your apps will live at orgiggly.com/name/app. Then it asks what you want to build. Try one of these, or say anything you like: 
      A book club: we suggest books, vote on the next one, and see when we're meeting.
      A volunteer rota for our village fete: people pick shifts, and I can see the gaps.
      Our family recipe book, plus who's cooking this Sunday.
    5. Claude builds the app, shows you a preview link, and asks before making it live. It can't open orgiggly.com from inside the session, so open the preview link yourself once and check it looks right.
    6. After each publish, Claude saves the app's files to your repo's main branch, so nothing is lost when the session ends.
    7. Every session works on a new claude/… branch of its own; that's how Claude Code cloud sessions work. Your apps are safe on main, and once their work is there you can delete old claude/… branches on the repo's Branches page on GitHub. Claude can't delete them for you.
  6. 6

    Next time

    Start a new session with the same repo and the Orgiggly environment. It starts from main, so you're already signed in and your apps' files are there. Just say what you want:

    What Orgiggly apps are in this repo, and what does each one do?
    In my book club app, add a page where members can rate the books we've read.

    Getting a new plugin version: new sessions keep the plugin version the environment first installed, until you change the setup script or allowed domains, or about seven days pass. To update now, edit the environment, change the setup script's comment line (for example, bump the number), save, and start a new session.

If something goes wrong

claude.ai/code says "GitHub access is required for Claude Code cloud sessions"

Your Claude account belongs to a Team or Enterprise organization whose Owner hasn't turned on the GitHub connector. You can't change this yourself. Either:

  • ask an Owner to turn on GitHub under Organization settings → Connectors, then reload claude.ai/code and start again, or
  • use a personal Pro or Max plan instead. If your Claude login belongs to more than one organization, Switch organization on that page moves you to it.
Claude says "Can't reach <a domain>"

That domain is missing from the environment's allowed list. Open the session's menu (the caret after its title at the top), select Edit cloud environment, add the domain Claude named on its own line under Allowed domains, and save. It takes effect within about a minute. Then:

I've allowed that domain. Please try again.
Claude says it couldn't check the draft in a browser

With Custom network access, your app can't load past its loading screen inside the session, because it needs www.google.com, which isn't on the list. Nothing is wrong with the app. Open the preview link Claude gave you to check it yourself, or switch the environment's Network access to Full so Claude can check drafts itself.

/orgiggly isn't recognised

The plugin didn't install. Check the Setup script in the environment matches step 4 exactly, then start a new session. Saving a changed setup script makes the environment run it again; otherwise new sessions reuse the result of its first run.

Claude says a new Orgiggly plugin version is out, or doesn't know a feature that's been released

Your environment is still using the plugin version it installed first. Edit the environment, change the comment line in the Setup script (for example, bump the number), save, and start a new session. To check, ask Claude "what version of the orgiggly plugin is installed?"

Claude says you're not signed in

Check the Environment variables line reads OG_TOKEN=og1.…, all on one line with no spaces or quotes. A change to it reaches new sessions only, so start a new one after fixing it.

"OG_TOKEN didn't sign you in"

The token no longer works. Get a fresh one from orgiggly.com/connect/cli, replace the old one in the environment, and start a new session.

Your changes weren't there next session

A new session starts from your repo's main branch, and the old one's work may only be on its own claude/… branch (for example, from before the plugin saved to main, or when main is protected). In a new session, ask:

Merge my other claude/ branches into main and push main.
Your token got out

Email dave@orgiggly.com and we'll cancel it, which signs you out everywhere. Then get a new one from orgiggly.com/connect/cli.

Prefer to work on your own computer? Install the plugin locally instead.

← all guides