How to build apps with Claude Code without touching a terminal

You can use Claude Code without a terminal. Claude Code is one of the strongest AI coding assistants available, and it is included with Claude Pro and Max plans, but it was built for developers: you type into a command line, approve shell commands and run your own dev server. Jig is a free desktop app that puts a friendly window on top of it. You describe the app, Jig drives Claude Code for you, and you watch the result in a live preview.

This guide explains what that looks like, what you still have to set up once, and where the limits are.

Why Claude Code lives in a terminal

Claude Code is an agent, not a chat window. It reads the files in a folder, writes new ones, runs commands such as installing packages, and checks its own work. A terminal is the natural home for that: it is where developers already run those commands, and it lets Claude Code work on a real project on your computer instead of in a sandbox.

For someone who does not write code, that design leaves a lot to figure out before the first useful result:

• Making a project folder, choosing a framework and starting from a sensible template.
• Starting a development server, finding the right port and opening the preview.
• Deciding whether to approve each command Claude Code wants to run.
• Saving progress with git so a bad change can be undone.
• Keeping API keys out of the chat and out of the code.

None of that is hard for an engineer. All of it is a wall for everyone else.

Using Claude Code without a terminal

Jig runs on your Mac, Windows or Linux computer and makes those decisions for you. It looks like the hosted app builders people already know, with a chat on the left and a live preview on the right, but the work happens on your machine, using the Claude Code you already have signed in.

Here is what Jig handles so you do not have to:

• Projects as folders. Every app is an ordinary folder and git repository under ~/Jig, started from a modern template (Vite, React, TypeScript, Tailwind and shadcn/ui).
• The preview. One click starts a dev server Jig owns, installs dependencies if needed and picks a free port. You can switch device sizes and open a console drawer.
• Errors. Runtime, network and build errors show up as a banner with an Ask Jig to fix button.
• Permissions. Claude Code runs with a safe allowlist of commands (package managers, read-only git, file edits) and a deny list for destructive ones, so you are not asked to approve shell commands you cannot judge.
• The raw output. It is there if you want it, behind Show details, with keys redacted. By default you see progress in plain language.

The one-time setup, honestly

We want to be straight about this, because the title promises a lot. Today, setup looks like this:

1. Download Jig and install it like any desktop app.
2. Open it. Jig checks whether Claude Code is installed and signed in, and reports what it finds.
3. If Claude Code is missing, Jig shows the official install command with a copy button. Pasting that one command is the only time most people will see a terminal. Then sign in to Claude Code with your Claude account, or paste an Anthropic API key into Jig instead.
4. Pick Claude Code as your default assistant and model. Done.

After that, everything happens in Jig’s window. You also need a desktop computer: Jig does not run on phones or tablets, and it is not a website you open in a browser tab.

Your first app, step by step

1. Describe it

Start a new project and say what you want in plain words: “A booking page for my dog-grooming business, with a calendar and a form that emails me.”

2. Answer a short interview

Instead of guessing, Jig asks a few questions tailored to your idea, such as who uses it and what must be on the first screen, and shows a look-and-feel picker with eight designed themes. Your answers become a written brief, the app’s theme and a set of skills Claude Code should use. If you would rather jump in, Skip interview builds straight from your description.

3. Approve the plan

For bigger changes, Claude Code writes a plan first and Jig shows it to you with Approve, Edit and Discard. Replying to a plan revises it. Small, obvious changes go ahead without the extra step.

4. Watch it build

Progress streams into the chat in plain language: which files are being written, what is being installed. When the step finishes, the preview reloads with the result.

5. Keep going

Ask for changes the way you would ask a colleague: “Make the header smaller and add a price list.” Jig keeps project notes, decisions and a to-do list in the project folder, so Claude Code remembers what you built yesterday.

6. Publish

When you are happy, publish to your own Netlify account, download a zip of the built site for any static host, or take a Dockerfile to your own servers. More hosting targets are coming.

Checkpoints, keys and mistakes

The fear with any AI that edits files is that it breaks something you cannot fix. Jig is built around undo:

• A checkpoint every step. Each change is saved as a git commit on a separate jig branch. You can keep it, revert just that change, or go back to any earlier point. Going back is itself saved, so nothing is lost.
• Keys stay out of the chat. When the app needs a key, for example for a payment or email service, Claude Code asks through a secure box in the chat. The key is saved in your operating system’s keychain and the AI only ever sees its name. If you paste a key into the chat by mistake, Jig catches it.
• Your files stay yours. The project is a normal folder. If you stop using Jig tomorrow, it still opens in any editor.

What Jig does not do

A few honest limits, so you can decide if it fits:

• It needs a desktop computer and an AI assistant or API key. There is no hosted, in-browser version.
• It does not include AI usage. If you do not have a Claude plan, an API key or another supported assistant, you will need one. If you would rather pay one company for everything, a hosted builder may suit you better; see our comparisons.
• Real-time multiplayer editing is not a feature. Teams share work through git instead.
• Claude Code has the deepest integration today. OpenAI Codex and opencode work too, and are newer. If you use ChatGPT, read building apps with ChatGPT Plus or Enterprise.

If you are setting this up for a team, the guide for IT covers policy, approved AI providers and company git. If it is just you, start with Jig for individuals.