Update content from depot/app

content/agents/claude-code/quickstart.mdx

@@ -0,0 +1,138 @@
+---
+title: Quickstart for remote Claude Code agents on Depot
+ogTitle: Getting started with remote Claude Code agents on Depot
+description: Step by step guide on how to get up and running with remote Claude Code agents on Depot.
+---
+
+import {CheckCircleIcon} from '~/components/icons'
+import {DocsCTA} from '~/components/blog/CTA'
+
+This guide will help you get started with Depot's remote agent sandboxes for running Claude Code agents. With Depot, you can run your coding agents in a secure, isolated environment in the cloud, allowing you to move your coding sessions off of your local machine and into fast remote environments where you can easily launch, resume, and share coding sessions.
+
+## 1. Install the `depot` CLI
+
+Before you can start running remote agents, you need to install the Depot CLI. The CLI is available for Mac and Linux.
+
+**Note:** Remote agent sandboxes are only available on `depot` CLI version 2.96.2 or later.
+
+For Mac, you can install the CLI with Homebrew:
+
+```shell
+brew install depot/tap/depot
+```
+
+For Linux, you can install the CLI with [our installation script](https://depot.dev/install-cli.sh):
+
+```shell
+# Install the latest version
+curl -L https://depot.dev/install-cli.sh | sh
+
+# Install a specific version
+curl -L https://depot.dev/install-cli.sh | sh -s 2.96.2
+```
+
+For all other platforms, you can download the binary directly from [the latest release](https://github.com/depot/cli/releases).
+
+## 2. Creating a Depot organization
+
+Claude Code agent sandboxes and sandbox secrets live under a Depot organization. So before you can launch your first agent sandbox, you need to create a Depot organization.
+
+![Create a Depot organization](/images/docs/depot-create-organization.webp)
+
+1. Login to your Depot account to get to your [list of organizations](/orgs)
+2. Click on the `Create Organization` button
+3. Enter an organization name
+4. Click `Create organization`
+
+## 3. Get your Anthropic credentials
+
+Today Depot only supports bringing your own Anthropic subscription or API key. We do not provide our own Anthropic API key for use with Depot's remote agent sandboxes.
+
+There are two options for configuring your Anthropic credentials to use with Depot's remote agent sandboxes.
+
+### Claude Code token for Max plan
+
+**This is our recommended method for using Claude Code with Depot's remote agent sandboxes.**
+
+If you're on the **Max plan** from Anthropic, you need to get your Claude Code OAuth token to use with Depot's remote agent sandboxes.
+
+First, using the `claude` CLI, you can generate a new OAuth token:
+
+```shell
+claude setup-token
+```
+
+This will output a token that you can copy and use in the next step.
+
+![Claude Code OAuth token](/images/docs/claude-code-setup-token.webp)
+
+### Anthropic API key
+
+Alternatively, you can generate an Anthropic API key by following their [Developer Platform](https://docs.anthropic.com/en/api/overview) documentation.
+
+## 4. Set your Anthropic credentials
+
+For Depot to use your Anthropic credentials for remote Claude Code agents, you need to configure a secret in your Depot organization for your Anthropic API key or OAuth token.
+
+### Max plan subscribers (OAuth token)
+
+If you generated a Claude Code OAuth token, you can set it as a secret in your Depot organization:
+
+```shell
+depot claude secrets add CLAUDE_CODE_OAUTH_TOKEN --value <your-token-from-step-3>
+```
+
+### Anthropic API key
+
+If you generated an Anthropic API key, you can set it as a secret in your Depot organization:
+
+```shell
+depot claude secrets add ANTHROPIC_API_KEY --value <your-anthropic-api-key-from-step-3>
+```
+
+## 5. Access your git repositories
+
+You can work with public and private git repositories in your remote agent sandboxes. If you want to use private git repositories, you need to either install the `Depot Code` app into your GitHub organization, or set your Git credentials as secrets in your Depot organization.
+
+### Install the Depot Code app into your GitHub organization
+
+To grant remote agent sandboxes access to your private GitHub repositories, you can install the `Depot Code` app into your GitHub organization. This will allow you to clone and push changes to your private repositories from within your remote agent sandboxes.
+
+![Install Depot Code app](/images/docs/depot-code-github-app.webp)
+
+1. Login to your Depot account and [select your organization](/orgs)
+2. Click on the `Settings` tab in the sidebar
+3. Scroll down to the `GitHub Code Access` section
+4. Click `Connect to GitHub`
+
+### Granting access outside of GitHub
+
+If you prefer not to use the Depot Code app, you can set your Git credentials as secrets in your Depot organization. This allows you to clone and push changes to your private repositories using your Git credentials.
+
+To set your Git credentials as secrets, run the following commands:
+
+```shell
+depot claude secrets add GIT_CREDENTIALS --value <your-key>
+```
+
+## 6. Launch your first remote agent sandbox
+
+Once you've configured your Anthropic credentials and Git access, you can launch your first remote agent sandbox using the `depot claude` command.
+
+```shell
+depot claude
+  --session-id feature-auth \
+  --repository https://github.com/foo/bar \
+  --branch main \
+  "Give me a general summary of this repository"
+
+✓ Claude sandbox started!
+  Session ID: 557737f9-6274-4df0-ac78-fda2122b6180
+  Link: https://depot.dev/orgs/12293423849/claude/9842347238947
+```
+
+This command immediately tells the Depot control plane to start a new agent sandbox for Claude Code. Returning a url to the session inside of Depot where you can follow the output.
+
+![Remote Claude Code session inside of Depot](/images/docs/remote-claude-code-session-ui.webp)
+
+And that's it! You now have your Depot organization set up to make use of Depot agent sandboxes for Claude Code. You can pass different git repositories that your git credentials or Depot Code app have access to, you can specify different branches, you can resume a session using the `--resume` flag, and you can fork new sessions from an existing file systems using the `--session-id` flag and `--resume` flag at the same time.

content/agents/overview.mdx

@@ -0,0 +1,100 @@
+---
+title: Remote Agents
+ogTitle: Overview of Depot remote agents
+description: Learn how to use move your coding agents off of your local machine and onto Depot's remote agents platform
+---
+
+import {CheckCircleIcon} from '~/components/icons'
+import {DocsCTA, DocsCTASecondary} from '~/components/blog/CTA'
+
+Depot's remote agent sandboxes provide a secure, isolated environment for running AI coding agents like Claude Code in the cloud. Allowing you to move your agent coding sessions off of your local machine and into fast remote environments where you can easily launch, resume, and share sessions.
+
+Current agent sandboxes support Claude Code, with more agents coming soon. By default, running `depot claude` will start a new session in a remote sandbox.
+
+<DocsCTASecondary>
+  <a
+    href="/docs/agents/claude-code/quickstart"
+    data-ph-capture-attribute-button-id="agents-docs-cta-to-quickstart"
+    className="text-radix-mauve12 font-semibold"
+  >
+    To dive into using remote agents on Depot, check out our Claude Code quickstart guide &rarr;
+  </a>
+</DocsCTASecondary>
+
+## Key features
+
+### Isolated environments
+
+Each agent session runs in its own isolated container, providing a clean and secure environment for your development work. Sessions are completely isolated from each other, ensuring your work remains private and secure.
+
+### Persistent file system
+
+Agent sandboxes work directly with your git repositories and persists files automatically across agents sessions. Allowing you to resume your work exactly where you left off, whether you're picking up a session from last week, sharing with a teammate, or starting a new session from an existing sandbox.
+
+### Pre-configured development tools
+
+Agent sandboxes come pre-installed with popular programming languages, package managers, and development tools.
+
+### Session management
+
+Every agent sandbox not only persists your filesystem, but also the entire context and conversation you have built up with your coding agent in the remote sandbox.
+
+### Git integration
+
+Work directly with Git repositories in your sandbox. Clone public or private repositories (using secrets for authentication), make changes, and push updates - all within the isolated environment.
+
+### High performance
+
+Agent sandboxes run on Depot's optimized infrastructure with plans to provide automatic integrations with our existing Depot services like accelerated container builds, Depot Cache, and more. Every sandbox launches with **2 vCPUs and 4 GB RAM** by default, providing ample resources for most development tasks.
+
+### Web UI for sessions
+
+Easily manage your agent sessions through the Depot web UI. Start, resume, and share sessions with just a few clicks. The web interface provides a simple way to monitor your active sessions and access session logs.
+
+## How it works
+
+To demonstrate how remote agents work in Depot, we will use the `depot claude` command to demonstrate how remote Claude Code agents are launched in Depot.
+
+**Note:** To run the command below, you should complete the [Quickstart guide for Claude Code](/docs/agents/claude-code/quickstart) first.
+
+```shell
+depot claude \
+  --session-id feature-auth \
+  --repository https://github.com/user/repo.git \
+  --branch main \
+  "Implement authentication flow"
+```
+
+This command will fire a request to the Depot control plane to start a new remote agent sandbox and return a url to the web UI where that Claude Code session can be monitored and managed.
+
+Behind the scenes, Depot will do all of the following:
+
+1. **Session creation**: A new isolated container is provisioned for your session, named after the `--session-id` you provided or generate a session ID if not specified
+2. **Environment setup**: The sandbox comes pre-configured with development tools, languages, and libraries
+3. **Load filesystem**: The sandbox can be prepopulated with a filesystem from a previous session via the `--resume` flag. If no previous session is passed in, a brand new file system is provisioned for the session.
+4. **Git repository cloning**: If you specified a `--repository`, Depot will clone the repository into the sandbox and checkout the specified branch (if no branch is specified, it defaults to `main`)
+5. **Session saving**: When Claude Code has finished it's work and exits, the session state is preserved for later resumption
+6. **Easy resumption**: Use `--resume <session-id>` to continue from any environment
+
+Here is an example workflow where we start a new session with one prompt, then resume it later to continue working:
+
+```shell
+# Start a new session with a custom ID
+depot claude \
+  --session-id feature-auth \
+  --repository https://github.com/user/repo.git \
+  "Create a new branch called `feature-auth` and lets implement authentication flow for this new feature. Once you're happy with the initial implementation, commit your changes and push the branch to the remote repository."
+
+# Later, resume the session to continue working
+depot claude --resume feature-auth "This looks good, but we need to add the concept of a user profile now."
+```
+
+## Pricing
+
+Depot remote agent sandboxes are available on **all plans** and are billed at a usage rate of **$0.01/minute** with no included usage for remote agents.
+
+<DocsCTA>
+  <a href="/sign-up" data-ph-capture-attribute-button-id="agents-docs-cta" className="text-radix-grass12 font-semibold">
+    Start your 7-day free trial to try remote agents on Depot &rarr;
+  </a>
+</DocsCTA>

content/cache/authentication.mdx

@@ -4,7 +4,9 @@ ogTitle: Authentication for Depot remote caching
 description: Learn how to authenticate with Depot remote caching
 ---
 
-Depot Cache supports authenticating with user tokens and organization tokens. Additionally, [Depot-managed GitHub Actions runners](/docs/github-actions/overview) are pre-configured with single-use job tokens.
+Depot Cache supports authenticating with **user** tokens and **organization** tokens. Additionally, [Depot-managed GitHub Actions runners](/docs/github-actions/overview) are pre-configured with single-use job tokens.
+
+Project tokens are **not** supported for Depot cache.
 
 ## Token types