Where to Find the Fragments by E2B Source Code and Sign-In Page

Updated

Fragments by E2B is an open-source project, and its homepage at fragments.e2b.dev is the single entry point you need for both the source code and the sign-in flow. The page header contains a Sign in link for accessing the app, and a Star on GitHub link that takes you to the public repository. If you only want to read or fork the code, use the GitHub link; if you want to use the hosted tool, use Sign in.

What the homepage gives you

The Fragments landing page is intentionally minimal. According to the site itself, it presents:

  • Sign in — the entry point for the hosted application.
  • Star on GitHub — a direct link to the open-source repository.
  • A short description identifying Fragments as an open-source project made by E2B, described as the open-source version of Anthropic's Artifacts.

Both actions live in the top area of the page, so you do not need to scroll or hunt through menus to reach them.

Finding the source code

  1. Go to fragments.e2b.dev.
  2. Click Star on GitHub in the header.
  3. You land on the project's GitHub repository, where you can browse the code, read the README, open issues, or fork it.

The site confirms Fragments is open source and hosted on GitHub, so the GitHub link is the authoritative route to the code. If you prefer searching directly, look for the E2B organization on GitHub and the Fragments repository within it.

Signing in

  1. Go to fragments.e2b.dev.
  2. Click Sign in at the top of the page.
  3. Complete the sign-in flow to reach the hosted app.

The page evidence only confirms that a Sign in entry exists; it does not specify which identity providers are supported or what happens after authentication. Treat the sign-in page itself as the place to confirm available methods.

Which entry point to use

Goal Entry point
Read, clone, or contribute to the code Star on GitHub
Use the hosted Fragments app Sign in
Learn what the project is Homepage description at fragments.e2b.dev

Common snags

  • Confusing the two links. GitHub is for the code; Sign in is for the running app. They serve different purposes.
  • Expecting pricing details on the homepage. The available page evidence contains no pricing signals, so do not assume the hosted service is free or paid based on the landing page alone.
  • Looking for documentation on the homepage. The landing page is a gateway, not a docs site. Once on GitHub, the README is the better starting point for setup and usage.