Skip to content

Troubleshooting

Aninda Sundar Howlader edited this page Jul 20, 2026 · 1 revision

Troubleshooting

Something not behaving? Take a breath — this page is here to help, and most bumps have a one-line fix.

Two things worth knowing before you start:

  • GRU953-Studio explains problems in plain words. When something goes wrong, it tells you what happened and what to do next — not a wall of scary error text. If a message ever confuses you, you can simply ask it "what does that mean?" and it will explain.
  • Your work is safe. Progress is saved constantly, in plain-text notes in your own folder. Even if a session stops halfway — you close your laptop, or run out of daily usage — nothing is lost. You come back and carry on exactly where you left off.

So there's no need to worry. Find your situation in the table below, and follow the fix.

Common bumps and their fixes

The left column is what you might see or notice. The middle explains, in plain words, what's actually going on. The right tells you what to do. A few of these have fuller, step-by-step instructions further down the page.

What you see or notice What it means What to do
command not found: claude Claude Code isn't installed yet. Install Claude Code first, then try again. See Installation.
It won't work in the Claude Desktop app GRU953-Studio needs Claude Code — a different (though related) tool from the Claude Desktop chat app. Use Claude Code, not the Desktop chat app. Both the desktop version and the web version of Claude Code work.
/plugin install didn't seem to take effect The plugin list sometimes needs a refresh before a new install shows up. Close and reopen Claude Code, then run the install line again. See Installation.
A message about Node.js, or a missing safety check Node.js — a small helper program that powers the built-in safety checks — isn't installed. Install Node.js (free to use, no cost) from nodejs.org, then try again.
It says it can't publish, or mentions gh or "not signed in" The GitHub tool it uses to publish isn't set up or signed in yet. Install the GitHub CLI, sign in once, then try publishing again. Steps are below.
It stopped part-way — for example, you ran out of your daily usage Nothing is lost. It saves progress as it goes. Come back later and say "continue", or run /studio again. It resumes exactly where it stopped.
It refused to publish unexpectedly A safety check did its job — perhaps an unconfirmed publish, or a password spotted in the files. This is protection, not a fault. Read the plain-English reason it gives, fix that one thing, and try again.
It asked before generating an image, audio or video This is the built-in cost and privacy check working as designed — generated media uses your own Google account and is sent to Google. Say yes if you're happy with the cost shown, or ask it to try a different description first. See Connecting Gemini.
A pop-up used a word you didn't know It aims to explain every term the first time it appears — but one may slip through. Ask it "what does that mean?" in plain words. It's happy to explain, as many times as you need.
It says Ollama isn't available (on the web) Ollama — a free tool for running AI models on your own computer — can't run in a web session, only on the desktop version of Claude Code. Nothing to fix. It simply switches this off with a note and carries on. Use the desktop version if you want local AI. See Connecting Ollama.

A few of these, step by step

"command not found: claude"

This means Claude Code — the tool GRU953-Studio runs inside — isn't on your computer yet.

  1. Open the Installation page.
  2. Follow the steps there to install Claude Code and sign in.
  3. Come back and add GRU953-Studio.

The GitHub tool isn't set up (can't publish)

Publishing sends your app to your own GitHub account. For that, GRU953-Studio uses a small tool called the GitHub CLI. You only set this up once.

  1. Open cli.github.com in your web browser.
  2. Download and install the GitHub CLI for your computer (it's free to use, no cost).
  3. In Claude Code, type gh auth login and press Enter.
  4. Follow the prompts on screen to sign in to your GitHub account.
  5. Once signed in, ask GRU953-Studio to publish again.

If you'd rather read the whole publishing story first, the Features page explains how private-by-default publishing works.

It refused to publish

This is one of the safety checks doing exactly what it's meant to. Publishing is private by default, and there's a separate, deliberate step to make anything public — so an accidental or unconfirmed publish is stopped on purpose.

  1. Read the short reason it gives you — it names the one thing that needs sorting (for example, a publish that wasn't confirmed, or a password found in the files).
  2. Fix that single thing. If a password or key was spotted in the files, remove it — secrets shouldn't live in your app's files.
  3. Try publishing again.

This is a safety net for honest mistakes, not a sign that something is broken.

It ran out partway through

GRU953-Studio is an AI tool, so it has usage limits — on a long build you may reach your daily cap. That's completely fine.

  1. Don't worry — your progress is already saved.
  2. Come back whenever suits you, even days later.
  3. In Claude Code, say "continue", or run /studio again.
  4. It picks up exactly where it stopped.

Still stuck?

If your problem isn't here, or a fix didn't work, the community is glad to help:

  • Ask a question or share what happened on the GitHub Discussions page. This is the friendly place for "how do I…?" and "is this meant to happen?" — no technical detail required.
  • Report something that seems broken on the GitHub Issues page. Describe what you did and what happened, in your own words.

When you ask, it helps to say: what you typed, what you expected, and what you saw instead. That's plenty.

One important exception — anything security-related

If you think you've found a security problem — a way the safety checks could be got around, a leaked password, or anything that could put people at risk — please don't post it publicly in Discussions or Issues. Report it privately instead, following the steps in the Security policy. This keeps everyone safe while it's being fixed.

See also

  • Installation — getting Claude Code and GRU953-Studio set up.
  • FAQ — plain answers to the questions people ask most.
  • Connecting Ollama — using a free, private AI model on your own computer.
  • Connecting Gemini — turning on optional generated images, audio and video.
  • The README — the full project overview.

Clone this wiki locally