Skip to content
Get packs

Guide · Open source

How to use GitHub1s: browse GitHub code in your browser

Updated · written with AI from the project's own documentation and checked against our catalogue data

GitHub1s is a browser-based code explorer built on VS Code. It lets you read a repository's files, search its code and review changes without cloning it to your computer. This guide shows you how to open a repo, what you can and cannot do in it, and how to use the optional AI chat.

GitHub1sconwnet/github1s · ★ 23.3k · MIT

Quick start

  1. 1Pick a repository. Choose a public repository on github.com that you want to read.
  2. 2Change the URL. Replace github.com with github1s.com in the address, keeping the owner and repo path.
  3. 3Browse the files. Use the file explorer to open directories and files, and search for code.
  4. 4Review changes. Switch branches or tags, or open commits and pull or merge request diffs to see what changed.
  5. 5Set up AI chat (optional). Connect a model endpoint that accepts browser requests, then open the AI panel with Toggle Secondary Side Bar.

Open a public repository in GitHub1s

Add "1s" after "github" in a repository URL. The source gives this example, which opens the microsoft/vscode repository in GitHub1s.

Public repositories can be browsed without signing in, subject to the upstream services' access and rate limits.

  • Start from any public repo URL on github.com.
  • Change the host from github.com to github1s.com.
  • Keep the rest of the path the same, for example owner/repo.
https://github.com/microsoft/vscode ↓ https://github1s.com/microsoft/vscode

Browse files, search code and check changes

GitHub1s shows a VS Code-like interface with a file explorer. You can browse directories, find files and search code. To look at history, switch branches or tags, inspect commits and file history, and review pull or merge request diffs on GitHub and GitLab.

The usage guide covers navigation, search and troubleshooting in more detail.

  • Browse directories and open files in the explorer.
  • Switch between branches or tags.
  • Inspect commits and file history.
  • Review pull or merge request diffs on GitHub and GitLab.

Access private repositories

To browse private repositories, connect your GitHub or GitLab account, or supply an access token with the necessary permissions. The source does not list the exact token scopes, so check the usage guide for authentication details.

  • Connect your GitHub or GitLab account, or
  • Provide an access token that has the permissions the repository needs.

Use the AI chat to explain code

GitHub1s has an optional AI chat. You can ask for a repository overview, have a file or selection explained and ask follow-up questions. The assistant can look up relevant code as you chat.

To open the AI panel, click Toggle Secondary Side Bar in the layout controls at the top of GitHub1s. You need to connect a model endpoint that accepts browser requests. Messages and code context are sent to the selected endpoint, so read the AI guide before you use it with code you need to keep private.

  • Open the panel with Toggle Secondary Side Bar.
  • Use a model endpoint that accepts browser requests.
  • Messages and code context go to the endpoint you choose.

Know the limits before you start

Remote repositories are read-only. You can read and review code, but you cannot edit files and push changes. Search and code navigation depend on the repository platform and the upstream services available, so results may not match a full local IDE.

  • Read-only: you cannot edit and push code.
  • Search and navigation depend on upstream services.
  • Public repos are subject to upstream access and rate limits.

What people use it for

  • Reading an unfamiliar public repository quickly before deciding whether to use it.
  • Learning how a real project is organised by browsing its folders and files.
  • Reviewing branches, commits or pull request diffs in an editor-style view.
  • Browsing a private GitLab or GitHub repo with your own account or a token.
  • Asking the AI chat to explain a file or selected code.

Frequently asked questions

How do I use GitHub1s?

Add "1s" after "github" in a repository URL, for example change github.com/microsoft/vscode to github1s.com/microsoft/vscode. The repo opens in a VS Code-like interface where you can browse and search files.

Is GitHub1s free?

The project is released under the MIT licence, and the source lists the hosted site at github1s.com. The source does not describe any pricing, so check the site for current terms.

Do I need to install anything to use GitHub1s?

No. GitHub1s is a web app, and the source lists no prerequisites. You use it by changing the URL in your browser.

Can I use GitHub1s with private repositories?

Yes, you can connect your GitHub or GitLab account or supply an access token with the necessary permissions. See the usage guide for authentication steps.

Can I edit code and push changes with GitHub1s?

No. Remote repositories are read-only, so GitHub1s is for reading and reviewing code rather than editing and pushing it.

What are alternatives to GitHub1s?

The source lists GitHub Codespaces, Sourcegraph and vscode.dev as comparable projects. Codespaces is suited to editing and running code in a cloud environment, while GitHub1s focuses on reading repositories without cloning them.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

GitHub1s suits developers, students and reviewers who want to read or review a repository quickly in an editor-style view without cloning it. Skip it if you need to edit and push code, need search that matches a full local IDE, or do not want code sent to a third-party model endpoint.

Install options & downloads