Show HN: Claude Code sessions that persist across CI, teammates, and machines

6 hours ago 2

We're excited to launch Claude Code sessions for Depot. This enables seamless collaboration between AI coding agents and your team by allowing anyone in your organization to pick up and resume Claude sessions. Perfect for collaborating with Claude across your entire team and between your local & CI environments.

Whether you're handing off a complex debugging session to a teammate, running an AI-assisted code review in CI, or continuing work started by an automated agent, Claude Code sessions make it easy to maintain context and momentum across your entire development workflow.

What are Claude Code sessions for Depot?

With this latest command for the Depot CLI, you can now save, share, and resume conversations with Claude across your entire organization by using depot claude. Each session maintains full context—including conversation history, code changes, and project understanding—that can be picked up by any team member or automated process with the correct permissions.

This transforms Claude from a personal coding assistant into a collaborative team resource. Sessions can flow seamlessly between:

Developers and AI agents - Hand off work between human developers and automated Claude agents
Team members - Share complex problem-solving sessions across time zones and teams
Local and CI environments - Start debugging locally and continue in CI, or vice versa
Different stages of development - Maintain context from design through implementation to review

How to use Claude Code sessions in Depot

Getting started with Claude Code sessions in Depot is simple. Just use the depot claude command instead of the regular claude command:

# Start a new session with a custom ID depot claude --session-id feature-auth-redesign # Resume a session by ID depot claude --resume feature-auth-redesign # Use in CI with non-interactive mode depot claude --session-id pr-1234 -p "review the changes in this PR and suggest improvements" # Pass through any Claude CLI flags depot claude --session-id debug-memory-leak --model opus -p "help me find the memory leak"

You can specify a custom session ID with --session-id, or use --resume <session-id> to continue an existing session. If you don't specify a session ID, Depot will generate one for you.

When you run depot claude, it will automatically save your session state, including conversation history and code context, to your Depot organization. This means you can pick up where you left off from any machine with access to your organization.

You can also list all available sessions in your organization using the list-sessions command:

depot claude list-sessions

From there, you can choose to resume any sessions by selecting the session from the list:

Behind the scenes, the depot claude command wraps the standard Claude Code CLI, automatically handling session persistence while passing through all Claude's native functionality. Sessions are uploaded when you exit, and can be resumed from any machine with access to your Depot organization.

Real-world examples

Internally, we've been collaborating on Claude Code sessions for the past month, and it's already transformed how we work. Here are some real-world examples of how we've been using this feature:

Cross-timezone collaboration

We're a globally remote team, so handoffs between developers in different time zones are a common occurrence. We can easily collaborate with our other team members and include Claude in the collaboration via sessions.

# Developer in SF starts implementing a feature depot claude --session-id payment-integration # Developer in London continues the next day depot claude --resume payment-integration -p "continue implementing the webhook handlers"

CI/CD integration

We've started looking at ways to integrate Claude into our code reviews. Anthropic already has some great actions around this, but we want to maintain context between the PR review and addressing the feedback locally. So, you can install Claude Code in your CI environment, tell it to do a code review while using the pull request number as the session ID, and then continue that session locally to address the feedback.

# In your GitHub Actions workflow - name: Install Claude run: npm install @anthropic-ai/claude-code - name: AI Code Review run: | depot claude --session-id pr-${{ github.event.pull_request.number }} \ -p "review this PR for security issues and best practices"

Debugging handoff

Much like everyone else, we've found Claude particularly useful for debugging. Now we can start a debugging session connected to our internal MCP tools and then hand off the session to a teammate to continue working on it. This is especially useful for complex bugs that require multiple iterations to resolve.

# Developer hits a complex bug depot claude --session-id bug-user-sync-issue # Senior engineer picks up the session later depot claude --resume bug-user-sync-issue -p "let's look at the database queries"

Why we built this

We're on a mission to make the entire software delivery lifecycle exponentially faster and more efficient. We are demonstrating that with our relentless focus on build performance across all of Depot. However, as we all know, the delivery pipeline encompasses more than builds. It also involves collaboration, debugging, code reviews, and more.

AI tools are giving us a new tool in our toolbelt. The ability to rapidly iterate on ideas, problem solving, and functionality, without having to actually write all of it ourselves.

But much like how CI providers were extremely ephemeral, underpowered, and siloed before Depot came along, AI coding agents are also limited in their ability to maintain context and collaborate effectively across teams and environments.

This results in a number of challenges:

Lost context when switching between local development and CI environments
Repeated work when multiple developers tackled similar problems without shared AI context
Limited automation because AI agents couldn't maintain state between runs
Knowledge silos where valuable problem-solving sessions were trapped on individual machines

With Depot, we solve these problems by making AI conversation context a shared team resource, just like your codebase. This enables entirely new workflows where AI agents can work continuously on long-running tasks, hand off to humans for review, and pick up where they left off—all while maintaining full context.

The End

You can utilize Claude Code sessions in Depot regardless of the plan you are on. Every session is scoped to your organization, ensuring your code and conversations remain secure and private.

We're already working on what's next, including more session state, enhanced tooling inside of agents, and even moving the agent into different environments.

Wanna give it a try? Try out Claude Code sessions in Depot today with depot claude. Have feedback or ideas? Join us in the Community Discord.