# GitHub1s: A VS Code Interface for Browsing GitHub Repositories in the Browser

> GitHub1s lets you browse any public GitHub repository in a VS Code interface by adding '1s' after 'github' in the URL. It runs entirely in the browser, requires no installation for public repositories, and includes an AI chat panel for querying the codebase.

**conwnet/github1s** — One second to read GitHub code with VS Code.

- Repository: https://github.com/conwnet/github1s
- Website: https://github1s.com
- Stars: 23,301 · Forks: 907
- Language: TypeScript
- License: MIT
- Published: 2026-09-10 · Updated: 2026-09-10 · Language: en
- Canonical page: https://hysenlabs.com/projects/conwnet-github1s

## A URL Shortcut That Opens Any GitHub Repository in VS Code

GitHub1s requires no installation for public repositories. The entire entry point is a URL change: add 1s after github in any GitHub repository URL and the repository opens in a VS Code interface in your browser.

The transformation is:

```text
https://github.com/microsoft/vscode
        ↓
https://github1s.com/microsoft/vscode
```

The result is a browser tab with a VS Code layout: a file tree in the left sidebar, an editor pane in the center, and tabs for open files. You can browse directories, open files, and search code without cloning the repository or installing anything locally.

Public repositories can be browsed without signing in, subject to the upstream services' access and rate limits. The README notes that access and rate limits are governed by the upstream GitHub services, not by GitHub1s itself. Heavy use of unauthenticated access can hit those limits faster than authenticated access would.

## How GitHub1s Loads Repository Data in the Browser

GitHub1s is built as a browser-based VS Code instance. The repository structure shows a vscode-web directory and extensions built separately: an extensions directory containing github1s and github1s-ai extensions. The package.json scripts show build steps for the webpack bundle and separate watch processes for the main application and each extension.

The architecture documentation referenced in the README covers components, data flow, and source layout. The README table of guides lists a dedicated architecture.md at docs/architecture.md for developers who want to understand how repository data flows from GitHub's API to the browser editor panes.

The deployment guide referenced in the README covers hosting, OAuth configuration, and service configuration. The repository includes a functions directory, which based on the package.json devDependencies includes @cloudflare/workers-types, suggesting the backend functions run on Cloudflare Workers.

Remote repositories are read-only. The README states this directly: you can explore, trace changes, and understand code, but you cannot commit or push through the interface.

## GitLab Repositories and npm Packages

GitHub1s extends the same URL pattern to other code hosts. GitLab repositories open at gitlab1s.com using the same path convention. Published npm packages open at npmjs1s.com.

The README describes these as additional entry points maintained alongside the main GitHub integration. The usage guide at docs/usage.md documents the URL formats, authentication methods, and navigation patterns for each platform.

For private repositories on GitHub or GitLab, you can connect your account or supply an access token with the necessary permissions. The README states that private repository access requires authentication and that access is subject to the permissions of the supplied token.

Branches, tags, commits, and file history are accessible through the interface. The README lists tracing a change as a core feature: you can switch branches or tags, inspect commits and file history, and review pull or merge request diffs on GitHub and GitLab.

## The Built-In AI Chat Panel

GitHub1s includes a built-in AI chat panel called GitHub1s AI. The README describes it as a tool for getting a repository overview, explaining a file or selection, and asking follow-up questions. The assistant can look up relevant code during the conversation.

To open the panel, click Toggle Secondary Side Bar in the layout controls at the top of the GitHub1s interface.

The AI feature requires connecting a model endpoint. The README specifies that the endpoint must accept browser requests, because messages and code context are sent directly from the browser to the selected endpoint. This means you need a model provider that allows cross-origin requests from browser-based clients, or a proxy that does.

The README links to a separate AI guide at docs/ai.md that covers model setup, context handling, the tools the assistant can use, and data handling. The README does not name specific model providers that are known to work; it defers to the guide.

## Access Limits and What GitHub1s Cannot Do

GitHub1s is a read-only interface. You cannot save changes, create branches, commit code, or open pull requests through it. If you need to modify files and commit them, you need a local clone or a cloud IDE that provides a writable workspace.

Code search and navigation depend on the repository platform and available upstream services. The README notes this directly under capabilities and limits in the usage guide. Not every search feature works the same way for all repositories or all sizes of codebase.

Browsing without signing in is subject to rate limits from GitHub's API. For large repositories or intensive browsing sessions, those limits can interrupt access. Connecting a GitHub account or supplying a personal access token increases the rate limit.

The AI chat feature requires a model endpoint that accepts browser requests. This is a concrete constraint: many LLM API providers do not allow direct browser-to-API calls due to CORS policy or token exposure concerns. Teams that want to use GitHub1s AI in a controlled environment need to configure an appropriate proxy or use a provider that explicitly allows it.

## Maintenance, Deployment, and Licensing

GitHub1s is actively developed. The last push was on 2026-09-22 and version 0.35.2 was released on 2026-09-20. Prior to that, 0.35.1 was released on 2026-09-14, suggesting a release cadence of roughly one release per week in September 2026.

The repository is maintained by three people: conwnet, xcv58, and Siddhant Khare, as listed in the README maintainers section.

The project is MIT licensed. The README credits Sourcegraph, searchcode, and OSS Insight as third-party tools and services used by GitHub1s.

For teams that want to self-host, the repository includes a deployment guide at docs/deployment.md covering hosting, OAuth configuration, and service configuration. The development guide at docs/development.md covers running GitHub1s locally, the build process, and the test setup. Tests use Playwright and are in the tests directory.

## Conclusion

GitHub1s is the right tool for developers who need to read and explore an unfamiliar repository quickly without cloning it. The URL trick is its entire install step for public repositories. It is not a development environment: the repository is read-only, so you cannot save edits or push changes through the interface. Teams that need to write, test, and commit code should use a local clone or a cloud IDE. The last push was on 2026-09-22, with version 0.35.2 released on 2026-09-20 under the MIT license.

## FAQ

### What is GitHub1s?

GitHub1s is a browser-based VS Code interface for reading GitHub repositories. Add 1s after github in any GitHub URL to open that repository in a VS Code layout in your browser, with no installation required for public repositories.

### Is GitHub1s safe to use for private repositories?

GitHub1s accesses private repositories using a GitHub account connection or a personal access token that you supply. Messages and code context sent to the AI chat feature go directly from your browser to the model endpoint you configure. The README links to docs/ai.md for data handling details.

### Does GitHub1s work with GitLab?

Yes. GitLab repositories open at gitlab1s.com using the same URL pattern. Published npm packages open at npmjs1s.com. The usage guide at docs/usage.md covers URL formats and authentication for each supported platform.

## Sources

- [conwnet/github1s on GitHub](https://github.com/conwnet/github1s)
- [License: MIT](https://github.com/conwnet/github1s/blob/master/LICENSE)
- [Project website](https://github1s.com)
- [README](https://github.com/conwnet/github1s/blob/master/README.md)
- [Releases](https://github.com/conwnet/github1s/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/conwnet-github1s