GitHub works entirely in your browser — no software installation required. Use github.com to create repos, upload files, and manage issues. Press the period key to open github.dev, a full code editor in your browser. For a complete development environment, launch GitHub Codespaces from any repository. All three tools run in your browser with zero setup.
Everything You Need Is Already in Your Browser
One of the biggest barriers for non-technical founders is the assumption that using GitHub requires installing Git, a terminal, or specialized software. That's no longer true. GitHub provides three browser-based tools that cover every level of need. First, github.com itself — the website you're already familiar with — handles repository creation, file uploads, issue tracking, and pull request reviews. Second, github.dev is a lightweight VS Code editor that opens instantly when you press the period (.) key on any repository page. It lets you browse and edit files across your entire project. Third, GitHub Codespaces is a full cloud development environment — like having a complete computer in your browser tab, pre-configured with all the tools your project needs. If you're using AI builders like Lovable or V0 to generate code, you may only ever need github.com for reviewing what the AI built. But knowing about all three options means you're prepared for any situation.
Prerequisites
- A GitHub account (free plan works for github.com and github.dev; Codespaces has a free tier)
- A modern web browser
Step-by-step guide
Manage your project on github.com
Manage your project on github.com
Sign in to github.com and navigate to any repository. From here, you can do almost everything without installing anything. Click any file to view its contents. Click the pencil icon to edit a file. Click "Add file" → "Upload files" to drag and drop files from your computer. Use the "Issues" tab to create tasks and the "Pull requests" tab to review changes. Click the "Code" dropdown button (green) to download a ZIP of your entire project. The github.com interface is the command center for your project.
Expected result: You can browse, edit, upload, and manage files entirely on github.com.
Open the github.dev editor for multi-file editing
Open the github.dev editor for multi-file editing
Navigate to any repository on github.com. Press the period (.) key on your keyboard. The page transforms into a full VS Code editor at github.dev. On the left sidebar, you'll see the Explorer panel showing all your project files. Click any file to open it in a tab. You can open multiple files, search across the entire project with Ctrl+Shift+F (or Cmd+Shift+F on Mac), and make edits to multiple files. When you're ready to save, click the Source Control icon in the left sidebar (the branch icon with a number badge), type a commit message, and click the checkmark to commit your changes.
Expected result: A VS Code editor opens in your browser with full access to your repository's files.
Launch a Codespace for a full development environment
Launch a Codespace for a full development environment
Navigate to a repository on github.com. Click the green "Code" dropdown button, then click the "Codespaces" tab. Click "Create codespace on main." GitHub will spin up a cloud-based development environment — this takes 30 to 60 seconds. Once loaded, you'll see a full VS Code interface in your browser with a terminal, file explorer, extensions, and live preview. Codespaces come pre-configured based on your repository's settings, so dependencies are already installed. This is the most powerful browser-based option — it can run servers, install packages, and execute your app, all without installing anything on your computer.
Expected result: A full VS Code development environment opens in your browser with terminal access.
Choose the right browser tool for your task
Choose the right browser tool for your task
Here's a simple decision framework. Use github.com when you need to upload files, create issues, review pull requests, or make quick single-file edits — it's the fastest for simple tasks. Use github.dev when you need to edit multiple files, search across your project, or make bigger changes to text and configuration files — it's like a lightweight editor. Use Codespaces when you need to run code, test your app in a preview, install packages, or do development work — it's a full computer in the cloud. If you're a non-technical founder using Lovable or V0 to build your app, github.com is usually all you'll need for reviewing and managing your project.
Expected result: You understand when to use github.com, github.dev, and Codespaces.
Complete working example
1<!DOCTYPE html>2<html lang="en">3<head>4 <meta charset="UTF-8">5 <meta name="viewport" content="width=device-width, initial-scale=1.0">6 <title>My Project</title>7 <style>8 body { font-family: system-ui, sans-serif; max-width: 600px; margin: 40px auto; padding: 0 20px; }9 h1 { color: #333; }10 p { color: #666; line-height: 1.6; }11 .badge { background: #238636; color: white; padding: 4px 12px; border-radius: 12px; font-size: 14px; }12 </style>13</head>14<body>15 <h1>My Project</h1>16 <p><span class="badge">Live</span></p>17 <p>This page was created and edited entirely in the browser using GitHub's web tools.</p>18 <p>No terminal. No installation. Just a browser.</p>19</body>20</html>Common mistakes when using GitHub Without Installing Anything
Why it's a problem: Trying to run code or install packages in github.dev
How to avoid: github.dev is an editor only — it can't run code. If you need to execute code or see a live preview, use GitHub Codespaces instead.
Why it's a problem: Leaving a Codespace running and burning through free hours
How to avoid: Codespaces auto-stop after 30 minutes of inactivity by default. You can also manually stop them by going to github.com/codespaces and clicking the three-dot menu → Stop codespace.
Why it's a problem: Confusing github.dev with GitHub Codespaces
How to avoid: github.dev is a lightweight file editor (no terminal, no code execution). Codespaces is a full development environment (terminal, live preview, package installation). Think of github.dev as Notepad and Codespaces as a complete workstation.
Why it's a problem: Forgetting to commit changes before closing the github.dev tab
How to avoid: Always click the Source Control icon and commit your changes before closing the tab. Uncommitted changes in github.dev are lost when you close the browser.
Best practices
- Use github.com for quick edits, uploads, and project management
- Use github.dev for editing multiple files without leaving the browser
- Use Codespaces only when you need to run code or test locally
- Stop Codespaces when you're done to conserve free hours
- Always commit your changes in github.dev before closing the browser tab
- Bookmark your most-used repositories for quick access
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I'm a non-technical founder who wants to manage my AI-built project on GitHub without installing any software. Explain the difference between github.com, github.dev, and GitHub Codespaces in simple terms with examples of when I'd use each one.
Frequently asked questions
Is github.dev free?
Yes. github.dev is completely free with no usage limits. It opens instantly in your browser when you press the period key on any repository page.
How much does GitHub Codespaces cost?
GitHub's free plan includes 120 core-hours per month (about 60 hours on a 2-core machine) and 15 GB of storage. After that, it's $0.18/hour for a 2-core machine. Most non-developers stay well within the free tier.
Can I use Codespaces with a Lovable or V0 project?
Yes. Once your Lovable or V0 project is connected to GitHub, you can open a Codespace on that repository to browse the code, run the app locally, or make manual adjustments.
Do I lose my changes if I close the browser?
On github.com, changes are saved when you click Commit. On github.dev, you must commit before closing or changes are lost. Codespaces save your environment even if you close the tab — just resume from github.com/codespaces.
Can RapidDev help me set up a browser-based workflow?
Yes. RapidDev helps non-technical founders configure browser-only GitHub workflows, including Codespaces configurations and github.dev best practices, so you never need to install developer tools on your computer.
Can I use these browser tools on a tablet or Chromebook?
Yes. github.com and github.dev work on any device with a modern browser, including tablets and Chromebooks. Codespaces also works on these devices, though a larger screen is recommended for the full editor experience.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation