.

Author: jayhack

docs/docs.json

@@ -28,9 +28,9 @@
           {
             "group": "Integrations",
             "pages": [
+              "integrations/github",
               "integrations/slack",
               "integrations/linear",
-              "integrations/github",
               "integrations/notion",
               "integrations/figma",
               "integrations/circleci",
@@ -43,8 +43,9 @@
             "pages": [
               "sandboxes/overview",
               "sandboxes/setup-commands",
-              "sandboxes/editor",
               "sandboxes/environment-variables",
+              "sandboxes/secrets",
+              "sandboxes/editor",
               "sandboxes/web-preview"
             ]
           },

docs/introduction/api.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Codegen SDK"
 sidebarTitle: "API"
-icon: "code"
+icon: "bolt"
 iconType: "solid"
 ---
 

docs/sandboxes/editor.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Remote Editor (VSCode)"
 sidebarTitle: "Editor"
-icon: "pencil"
+icon: "laptop-code"
 ---
 
 Codegen provides access to a remote VSCode editor instance that is directly connected to your active sandbox environment. This powerful feature allows for real-time interaction with the agent's workspace, offering capabilities for live debugging, manual intervention, and detailed progress monitoring.

docs/sandboxes/secrets.mdx

@@ -0,0 +1,41 @@
+---
+title: "Repository Secrets"
+sidebarTitle: "Secrets"
+icon: "key"
+---
+
+Manage environment variables and secrets for your repository. These are securely injected into the agent's sandbox environment during code execution.
+
+<Warning>
+  Only use staging credentials and non-production secrets. Never store
+  production API keys, database passwords, or sensitive credentials.
+</Warning>
+
+## How Secrets Work
+
+Repository secrets are environment variables that get automatically injected into the sandbox when agents execute code:
+
+- **Secure Storage:** Secrets are encrypted and stored securely per repository
+- **Sandbox Injection:** Automatically available as environment variables during agent execution
+- **Development Support:** Enable agents to run dev servers, connect to staging databases, and test integrations
+
+## Common Use Cases
+
+- **Development Server Credentials:** API keys for staging services and development APIs
+- **Database Connections:** Connection strings for staging/test databases
+- **Third-Party Integrations:** Non-production tokens for services like Stripe test mode, staging analytics
+- **Build Configuration:** Environment-specific build variables and feature flags
+
+## Managing Secrets
+
+Add secrets through your repository settings:
+
+1. Navigate to your repository settings
+2. Go to the Secrets tab
+3. Add key-value pairs for your environment variables
+4. Secrets are immediately available to agents in the sandbox
+
+<Note>
+  Agents can access these secrets when running code, starting development
+  servers, or executing tests that require environment configuration.
+</Note>{" "}