Installation

Installing GRU953-Studio

Setting up GRU953-Studio is a one-time job, and this page walks you through every step in plain language. There's nothing to break, nothing you can't undo, and it works the same way on whatever computer you use. Take it one step at a time and you'll be ready in a few minutes.

What you need first

GRU953-Studio is an add-on for a program called Claude Code — Anthropic's assistant that you talk to in plain words to build and change software. Think of Claude Code as the workshop, and GRU953-Studio as a skilled team that comes to work inside it. So the very first thing you need is Claude Code itself.

One important point, because it trips people up:

GRU953-Studio needs Claude Code — not the "Claude Desktop" chat app. They sound alike and are made by the same company, but they're different programs. The everyday Claude Desktop chat app can't run GRU953-Studio, because the studio relies on abilities that only Claude Code has. If you only have the Claude Desktop chat app, GRU953-Studio won't appear — that's expected, not a fault.

The good news: GRU953-Studio works wherever Claude Code works. Claude Code runs in a lot of places, so you can almost certainly use it on the setup you already have:

Where you can use Claude Code	What it is
macOS, Windows and Linux	The Claude Code desktop app for your computer
A web browser	Claude Code on the web — nothing to install on your machine
Inside a code editor	The Claude Code extensions for VS Code and for JetBrains editors (handy if you already use one)

If you can run Claude Code in any of those, you can run GRU953-Studio. You do not need to be a programmer to use any of them.

Step 1 — install and sign in to Claude Code

1. Open the Claude Code download page in your web browser.
2. Follow the instructions there to get Claude Code for your computer (or to open Claude Code on the web — whichever you prefer).
3. Sign in with your Anthropic account when Claude Code asks you to.
4. Wait until Claude Code is open and ready, showing a box where you can type.

That's the only sign-in you need to build apps. (Publishing later needs one more small sign-in — covered further down — but you don't need it to start.)

Step 2 — add GRU953-Studio

There are two ways to add the studio. Most people should use Way A. Choose Way B only if you'd rather work from a downloaded file, or you need one specific version.

Way A — the simple way (recommended, always the newest version)

Type these two lines into Claude Code, one at a time, pressing Enter after each and waiting for it to finish before typing the next:

/plugin marketplace add GRU-953/GRU953-Studio

/plugin install gru953-studio@gru953-studio

The first line tells Claude Code where to find the studio's list of add-ons. The second line installs GRU953-Studio from that list. The @gru953-studio on the end simply names which list to install from — here the add-on and its list share the same name, so it looks a little repetitive, and that's fine.

This way always gives you the latest release, and it's the easiest to keep up to date later.

Way B — from a downloaded file (a specific version)

Use this if you'd prefer a file you keep on your own computer, or you want a particular version rather than the newest one.

1. Open the Releases page in your web browser.

2. Under the newest version (at the top of the list), find the .zip file and download it. (A .zip file is just a folder that's been squeezed into a single file for easy downloading.)

3. Unzip that file anywhere on your computer — your Downloads folder is fine. Unzipping gives you an ordinary folder of the studio's files.

4. Make a note of where that unzipped folder is. You'll paste its location into the next step.

5. In Claude Code, type these two lines one at a time, but replace the folder location with your own:

   On a Mac, it might look like this:

   /plugin marketplace add /Users/yourname/Downloads/GRU953-Studio
   /plugin install gru953-studio@gru953-studio
   

   On Windows, it might look like this:

   /plugin marketplace add C:\Users\YourName\Downloads\GRU953-Studio
   /plugin install gru953-studio@gru953-studio
   

The only difference from Way A is the first line: instead of the online address GRU-953/GRU953-Studio, you point it at the folder you just unzipped. The second line is exactly the same.

Two free-to-use tools it relies on

GRU953-Studio leans on two small, well-known tools to do its job safely. Both are free to use (no cost), and you only ever set each one up once.

Tool	What it does	When you need it
Node.js	Powers the studio's built-in safety checks (the automatic checks that look for things like leaked passwords before anything is shared)	Install it once, near the start
GitHub CLI	Lets the studio publish your finished app to your own online account	Only when you're ready to publish

1. To get Node.js, open the Node.js website in your web browser and follow the install instructions for your computer. This is a one-time job.
2. To get the GitHub CLI (needed only when you publish), open the GitHub CLI website and follow the install instructions.
3. After the GitHub CLI is installed, run this line once to connect it to your own GitHub account, then follow the friendly prompts it shows you:

   gh auth login
   

You don't have to rush the GitHub parts. You can install and sign in to the GitHub CLI later, at the moment you first want to publish something.

You won't be left guessing. If either tool is missing at the moment the studio needs it, GRU953-Studio stops and tells you plainly what to install and how — it never fails silently or leaves you staring at a confusing error.

Optional extras (only if you want them)

These are entirely optional. You can build plenty of real apps without either, and you can add them any time later.

• Generated images, audio, or video. If you'd like the studio to create pictures, sound, or video for your app, you can connect a Google Gemini key of your own. This is a paid cloud service that uses your own account, and the studio always shows the cost and asks first. Written text (in Bangla and English) never needs this — it's written by Claude directly. See Connecting Gemini for the full walkthrough.
• AI that runs on your own computer, at no cost. Ollama is a separate tool that runs AI models locally on your machine, without the cloud. It's optional, and the studio always asks before installing anything. See Connecting Ollama to set it up.

The first time you run it

The very first time you use GRU953-Studio, it runs a short, one-off "getting to know you" setup. It asks a few friendly pop-up questions — what to call you, the kinds of things you like to build, your language preference, and (only when you're ready to publish) your GitHub username. This is so it can talk to you the way you'd like.

This happens once, and never again. Every project after that skips straight to the fun part.

Check it worked

To make sure everything is in place:

1. In Claude Code, type /studio and press Enter.
2. GRU953-Studio should greet you and offer to start.

If you're greeted, you're all set. If nothing happens, or /studio isn't recognised, close and reopen Claude Code and try again — the add-on list sometimes just needs a refresh. The Troubleshooting page covers this and a few other common bumps in plain English.

Keeping it up to date

If you installed with Way A, staying current is easy, because that method follows the studio's online list. To pick up the newest version:

1. Type /plugin in Claude Code and press Enter to open the add-ons panel.
2. Find GRU953-Studio in your installed add-ons and choose to update it.

If you'd rather, you can simply re-run the two Way A lines from Step 2 — that also brings you up to the latest version. (If a new release doesn't seem to take effect, close and reopen Claude Code first.)

Removing it

You can take GRU953-Studio out again at any time, and it won't touch the projects you've already built:

1. Type /plugin in Claude Code and press Enter to open the add-ons panel.
2. Find GRU953-Studio in your installed add-ons and choose to remove it.

That's all it takes. You can always add it back later with the two lines from Step 2.

What next

You're ready to build something. A good next stop is Sample use cases — a set of real, plain-English examples you can type in as-is (or tweak) to see the studio in action, from a one-page website to a small phone app. Pick one that appeals, type it between square brackets, and answer the pop-ups that follow.