AI Workspace

Your personal AI developer. Describe what you want to build and the AI writes the code, runs it in a live preview, and keeps everything in a private GitHub repository — all without leaving GetLaunch.

Getting Started

1. Describe what you want to build

Start a new workspace and describe what you want in plain language — no name needed first:

"Build a booking app for my café with a menu, reservation form, and admin dashboard."

GetLaunch creates the workspace with a private GitHub repository, and the AI reads your request and starts building. The workspace names itself from your first message a few seconds later. Click the name at the top of the workspace to rename it at any time.

2. Choose Build or Plan

The switch next to the message box sets how the AI works on your message:

Build (default) — starts editing right away.
Plan — the AI looks through your project and proposes a plan first. Nothing changes until you approve it; you can also ask for changes to the plan before it builds.

3. Watch it build

Each file write, shell command, and check appears in the chat as it happens.

4. Open the preview

Click the Preview button in the top toolbar to open a live running version of your app alongside the chat. Changes show up in the preview as the AI makes them.

The Chat

The agent runs in the cloud. You can safely close the browser tab at any time. When you come back, your workspace will be exactly where you left off and any in-progress work will have completed.

One task at a time. Only one task runs at a time across all your workspaces. Wait for the current task to finish before sending the next message or starting a new workspace.

Stopping a task. Stop a running task at any time and choose Stop & save progress to keep what the AI has done so far, or Stop & discard to throw it away.

Ask the AI about GetLaunch. You can ask the AI questions about the platform itself — publishing, custom domains, pricing, your credit balance, your plan, or why a deployment failed — and it answers from GetLaunch's current information and your account.

Tasks & Phases

For larger requests the AI may break work into phases — each a self-contained chunk of the project — shown in the Tasks panel with their status.

Phases run in order. Each must complete before the next can start.
Start the first phase yourself. After that, Auto-continue (on by default) runs the remaining phases back-to-back. Turn it off to review between phases — the chat then offers a button to start the next one.
Run all starts every remaining phase in one go.

Live Preview

The preview is a real running instance of your app for testing. It is not your production deployment.

How to use it:

Click the Preview button in the toolbar to open the preview panel.
The first load can take 30–90 seconds while your app starts up.
While the AI works, edits appear in the preview live. If something breaks, ask the AI to look at the latest preview error and fix it, then retry the preview.

Device modes: Switch between Desktop, Tablet (768px), and Mobile (390px) using the icons in the preview toolbar.

Navigate pages: Type a path in the address bar (e.g. /dashboard) to jump to any page in your app.

Element picker: Click the crosshair icon (⊕), then click any element in your preview. Use Ask about this to send the element directly to the AI for targeted changes.

Limits:

The preview sleeps after about 4 minutes of inactivity and wakes up again when you open it. Your app's files and preview data are kept (preview data for up to 7 days without use).
The preview sandbox is recycled after about an hour, even while in use; it starts back up on its own.
Preview URLs may change between sessions. Do not share them with end users.

Preview Settings (Environment Variables)

Environment variables for the preview (API keys, database URLs, feature flags) are managed in Preview settings in the top toolbar.

The AI sets up default values automatically. You can override any of them — for example, to try the preview against a different service.

Rules:

You can only change values for keys the AI has already defined. To add or remove a key, ask the AI to update the project configuration.
Values cannot contain newline characters.
Saving changes restarts the preview automatically so the new values take effect.
These values are used by the preview only. Production values are set separately when you publish, so the preview never touches your production database.

Publishing

When the preview works, click Publish to put your app online. You need a hosted production database, and the app is paid for one of two ways. The Publish screen shows which one applies to your account before you confirm:

Pay as you go: no hosting plan. The published app uses your AI credits as people visit it. See Pay-as-you-go web apps.
Hosting plan: an active paid plan (Starter or above). See Pricing.

On the first publish, choose the app name. It becomes part of the app's web address on gtlnch.app.
Review the production environment — real values for your database, API keys and secrets. DATABASE_URL must point to a hosted Postgres database; localhost and 127.0.0.1 are not reachable from production. See Production Databases.
Publish. The published app appears under Projects, with its deployment history, logs, and custom domain settings.

Click Republish any time to publish your latest changes. The workspace keeps working after publishing — keep asking for changes and republish when you're ready.

Downloading Your Code

Click Download in the top toolbar at any time to download your full codebase as a .zip file.

The download includes all project files, cleaned of any internal GetLaunch files, ready to run locally or push to your own repository.

What's Kept and for How Long

Your code is kept for as long as the workspace exists. Every change the AI makes is saved to your workspace's private repository, and Download always gives you the latest version. Your published app and its production database are not affected by anything below.

Some things are only kept for a limited time:

What	How long it's kept
Chat messages — yours and the AI's replies, including the step-by-step details	7 days after each message. Older messages disappear from the chat.
Preview data — what your app stored in its preview database	7 days after you last used the workspace. After that, the preview starts with a fresh database.
The AI's memory of your conversation	7 days after you last used the workspace. After that, the AI continues from your code, plan and tasks rather than the earlier conversation.
Files you attach to a message	A few hours. If your app uses one (like a logo), the AI copies it into your project, where it stays with your code.

Privacy & Security

Your own sandbox. Each workspace runs in its own isolated sandbox. The AI, your preview app and its database run there, separate from every other workspace.
The preview isn't public. It opens only through a signed link tied to your workspace, and each access link expires after a short time.
The preview never touches your production data. The settings you enter when publishing belong to your published app, not to the workspace, so the preview can never connect to your production database.
Secrets stay hidden. Values you mark as secret for your published app can't be read back after you save them, and they're masked in runtime logs.
Attached files are private. They're stored privately, opened only through short-lived links, and deleted after a few hours.
The AI only sees this workspace. When it checks logs or account details to help you, it can only see this workspace's app and your own account.
Deleting a workspace deletes its data. That includes the code repository, chat history, preview sandbox and database, saved snapshots and uploaded files. A published workspace must have its project deleted first.
AI processing. Your messages, files and code are processed by third-party AI providers to generate responses. See our Privacy Policy for details.

AI Credits

Every coding task uses AI credits, based on how much work the AI does. The exact charge is calculated after the task finishes and appears in your workspace history. Failed tasks are not charged.

Quick tweak / one-liner: ~1 credit
Typical edit: ~3 credits
Substantial multi-file change: ~9 credits
Large feature: ~14 credits
Every account gets free credits at signup and each month — see Pricing for the current amounts and credit packs
Check your balance at AI Credits
If you run out, new tasks are blocked until you top up
Pay-as-you-go web apps use the same balance as people visit them. See Pay-as-you-go web apps

FAQ

Can I connect my own GitHub repo? Not yet. Each workspace gets a new private repository managed by GetLaunch. You can download the code at any time and push it to your own repo.

What happens if a task fails? The AI explains what went wrong in the chat, and the preview keeps showing the last working version. Send a follow-up asking it to try again or take a different approach.

Can two people work in the same workspace? Workspaces are currently single-user. Collaboration is on the roadmap.

Is my code private? Yes. All workspace repositories are private and are not shared with other users. See Privacy & Security above for how your workspace data is handled.

How do I delete a workspace? Deleting a workspace also deletes its code repository, so download the code first if you want to keep it. A published workspace can't be deleted while its project exists — delete the project first, then the workspace.

Why did older messages disappear from my chat? Chat messages are kept for 7 days. Your code and every change the AI made are kept for as long as the workspace exists — see What's Kept and for How Long above.