Merge branch 'main' into feat--can-pipe-into-stdin

Author: matthewlouisbrockman

docs.json

@@ -42,6 +42,13 @@
               "docs/billing"
             ]
           },
+          {
+            "group": "Use cases",
+            "pages": [
+              "docs/use-cases/computer-use",
+              "docs/use-cases/ci-cd"
+            ]
+          },
           {
             "group": "Code Interpreting",
             "pages": [
@@ -82,12 +89,15 @@
               "docs/sandbox/lifecycle-events-api",
               "docs/sandbox/lifecycle-events-webhooks",
               "docs/sandbox/persistence",
+              "docs/sandbox/git-integration",
               "docs/sandbox/metrics",
               "docs/sandbox/metadata",
               "docs/sandbox/environment-variables",
               "docs/sandbox/list",
               "docs/sandbox/connect",
               "docs/sandbox/internet-access",
+              "docs/sandbox/pty",
+              "docs/sandbox/ssh-access",
               "docs/sandbox/connect-bucket",
               "docs/sandbox/rate-limits",
               "docs/sandbox/secured-access",
@@ -118,7 +128,8 @@
                   "docs/template/examples/nextjs-bun",
                   "docs/template/examples/expo",
                   "docs/template/examples/desktop",
-                  "docs/template/examples/claude-code"
+                  "docs/template/examples/claude-code",
+                  "docs/template/examples/docker"
                 ]
               },
               "docs/template/migration-v2",
@@ -152,12 +163,6 @@
               "docs/commands/background"
             ]
           },
-          {
-            "group": "Git",
-            "pages": [
-              "docs/git"
-            ]
-          },
           {
             "group": "MCP Gateway",
             "pages": [
@@ -196,13 +201,7 @@
           {
             "group": "Troubleshooting",
             "pages": [
-              {
-                "group": "SDKs",
-                "pages": [
-                  "docs/troubleshooting/sdks/workers-edge-runtime"
-                ]
-              },
-              {
+{
                 "group": "Templates",
                 "pages": [
                   "docs/troubleshooting/templates/build-authentication-error",
@@ -333,6 +332,11 @@
       "source": "/docs/getting-started/installation",
       "destination": "/docs/quickstart",
       "permanent": true
+    },
+    {
+      "source": "/docs/git",
+      "destination": "/docs/sandbox/git-integration",
+      "permanent": true
     }
   ]
 }

docs.mdx

@@ -4,37 +4,69 @@ sidebarTitle: Home
 icon: house
 ---
 
-import { Concepts } from '/snippets/Concepts.jsx';
-import { CodeInterpreting } from '/snippets/CodeInterpreting.jsx';
 import { Quickstart } from '/snippets/Quickstart.jsx';
 
-Here you'll find all the guides, concepts, and SDK references for developing with E2B.
+## What is E2B?
+
+E2B provides isolated sandboxes that let agents safely execute code, process data, and run tools. Our SDKs make it easy to start and manage these environments.
+
+Spin up a sandbox and run code in a few lines:
 
 <CodeGroup>
 ```bash JavaScript & TypeScript
-npm i @e2b/code-interpreter
+npm i e2b
 ```
 ```bash Python
-pip install e2b-code-interpreter
+pip install e2b
 ```
 </CodeGroup>
 
-## What is E2B?
-E2B is an [open-source](https://github.com/e2b-dev) infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.
-To start and control sandboxes, use our [Python SDK](https://pypi.org/project/e2b/) or [JavaScript SDK](https://www.npmjs.com/package/e2b).
+<CodeGroup>
+```javascript JavaScript & TypeScript
+import { Sandbox } from 'e2b'
+
+const sandbox = await Sandbox.create() // Needs E2B_API_KEY environment variable
+const result = await sandbox.commands.run('echo "Hello from E2B Sandbox!"')
+console.log(result.stdout)
+```
+```python Python
+from e2b import Sandbox
+
+sandbox = Sandbox.create()  # Needs E2B_API_KEY environment variable
+result = sandbox.commands.run('echo "Hello from E2B Sandbox!"')
+print(result.stdout)
+```
+</CodeGroup>
+
+## E2B Building Blocks
+
+A quick overview of the core building blocks you'll interact with when using E2B.
+
+- [**Sandbox**](/docs/sandbox) — A fast, secure Linux VM created on demand for your agent
+
+- [**Template**](/docs/template/quickstart) — Defines what environment a sandbox starts with
+
+## How to use the docs
+
+The documentation is split into three main sections:
+
+- [**Quickstart**](#quickstart) — Step-by-step tutorials that walk you through spinning up your first E2B sandboxes.
 
-Some of the typical use cases for E2B are AI data analysis or visualization, running AI-generated code of various languages, playground for coding agents, environment for codegen evals, or running full AI-generated apps like in [Fragments](https://github.com/e2b-dev/fragments).
+- [**Examples**](#examples) — In-depth tutorials focused on specific use cases. Pick the topics that match what you're building.
 
-### Under the hood
-The E2B Sandbox is a small isolated VM the can be started very quickly (~150ms). You can think of it as a small computer for the AI model. You can run many sandboxes at once. Typically, you run separate sandbox for each LLM, user, or AI agent session in your app.
-For example, if you were building an AI data analysis chatbot, you would start the sandbox for every user session.
+- [**SDK Reference**](https://e2b.dev/docs/sdk-reference) — A complete technical reference for every SDK method, parameter, and configuration option.
 
 ## Quickstart
-<Quickstart/>
 
-## Code interpreting with AI
-<CodeInterpreting/>
+<Quickstart />
 
-## Learn the core concepts
-<Concepts/>
+## Examples
 
+<CardGroup cols={2}>
+  <Card title="Computer Use" icon="desktop" href="/docs/use-cases/computer-use">
+    Build AI agents that see, understand, and control virtual Linux desktops using E2B Desktop sandboxes.
+  </Card>
+  <Card title="GitHub Actions CI/CD" icon="gears" href="/docs/use-cases/ci-cd">
+    Use E2B sandboxes in your GitHub Actions workflows to run testing, validation, and AI code reviews.
+  </Card>
+</CardGroup>

docs/billing.mdx

@@ -18,7 +18,7 @@ E2B uses [usage-based pricing](#usage-based-pricing) - you pay only for what you
 | **Concurrent sandboxes** | 20 | 100 - 1,100 | 1,100+ |
 
 <Note>
-Pro plan includes 100 concurrent sandboxes. Higher concurrency up to 1,100 is available as a purchasable [add-on](https://e2b.dev/dashboard/tberan/billing).
+Pro plan includes 100 concurrent sandboxes. Higher concurrency up to 1,100 is available as a purchasable [add-on](https://e2b.dev/dashboard?tab=billing).
 </Note>
 
 Plans have different [API rate limits](/docs/sandbox/rate-limits).
@@ -64,6 +64,10 @@ Template.build(
 
 See [template quickstart](/docs/template/quickstart) for more details on building custom templates.
 
+<Note>
+Need higher CPU or RAM limits? Contact [support@e2b.dev](mailto:support@e2b.dev) for more information.
+</Note>
+
 ---
 
 ## Monitoring usage

docs/git.mdx docs/sandbox/git-integration.mdxdocs/git.mdx renamed to docs/sandbox/git-integration.mdx

@@ -1,6 +1,6 @@
 ---
-title: "Git"
-sidebarTitle: Overview
+title: "Git Integration"
+description: "Clone repositories, manage branches, and push changes using the sandbox.git methods."
 ---
 
 Use the `sandbox.git` methods to run common git operations inside a sandbox.

docs/sandbox/persistence.mdx

@@ -276,13 +276,6 @@ If you resume the sandbox, the service will be accessible again but you need to
 
 ## Limitations while in beta
 
-### Lifecycle duration
-- A sandbox can exist for **up to 30 days** from the initial `create` call.
-- After 30 days, sandbox data **may be deleted** and the sandbox can no longer be resumed.
-- Attempting to resume a deleted or non-existent sandbox will result in:
-  - `NotFoundError` in the JavaScript SDK
-  - `NotFoundException` in the Python SDK
-
 ### Pause and resume performance
 - Pausing a sandbox takes approximately **4 seconds per 1 GiB of RAM**
 - Resuming a sandbox takes approximately **1 second**
@@ -292,4 +285,3 @@ If you resume the sandbox, the service will be accessible again but you need to
   - **24 hours** on the **Pro tier**
   - **1 hour** on the **Base tier**
 - After a sandbox is paused and resumed, the continuous runtime limit is **reset**
-- The **30-day total lifetime limit** still applies regardless of how many times the sandbox is paused or resumed