Open-source project behind CodeLayer, an IDE for orchestrating AI coding agents built on Claude Code, with keyboard-first workflows, team context engineering, and parallel Claude Code sessions across worktrees and cloud workers.
by HumanLayer · submitted by JPette1783·added 2026-06-05·
CodeLayer orchestrates AI coding agents that edit files and run commands in your repositories, so it inherits the execution risks of the underlying Claude Code agent., MultiClaude runs multiple Claude Code sessions in parallel across git worktrees; review changes per worktree before merging to avoid conflicting or unreviewed edits., Remote cloud workers can run agent sessions on external infrastructure; understand where code executes before enabling them., Scaling agent workflows to a whole team increases the blast radius of automated edits, so keep human review and branch protections in place.
Privacy notes
Because it builds on Claude Code, repository code and context are sent to Anthropic's API to power the agent., Remote cloud workers process your code and context on external infrastructure; review the provider's terms before sending private code., Any API keys or credentials used by Claude Code and CodeLayer should be stored as secrets, not committed to source control., Team and context-engineering features can share prompts, context, and workflow data across collaborators, so avoid placing secrets in shared context.
Author
HumanLayer
Submitted by
JPette1783
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
4 prerequisites to line up before setup. Have accounts and credentials ready first.
0/4 ready
Account & credentials1General3
Safety & privacy surface
Safety & privacy surface
4 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.
5 areas
SafetyLocal filesCodeLayer orchestrates AI coding agents that edit files and run commands in your repositories, so it inherits the execution risks of the underlying Claude Code agent.
SafetyCredentials & tokensMultiClaude runs multiple Claude Code sessions in parallel across git worktrees; review changes per worktree before merging to avoid conflicting or unreviewed edits.
SafetyCredentials & tokensRemote cloud workers can run agent sessions on external infrastructure; understand where code executes before enabling them.
SafetyGeneralScaling agent workflows to a whole team increases the blast radius of automated edits, so keep human review and branch protections in place.
PrivacyThird-party handlingBecause it builds on Claude Code, repository code and context are sent to Anthropic's API to power the agent.
PrivacyNetwork accessRemote cloud workers process your code and context on external infrastructure; review the provider's terms before sending private code.
PrivacyCredentials & tokensAny API keys or credentials used by Claude Code and CodeLayer should be stored as secrets, not committed to source control.
PrivacyCredentials & tokensTeam and context-engineering features can share prompts, context, and workflow data across collaborators, so avoid placing secrets in shared context.
Disclosure: editorial
Safety notes
CodeLayer orchestrates AI coding agents that edit files and run commands in your repositories, so it inherits the execution risks of the underlying Claude Code agent.
MultiClaude runs multiple Claude Code sessions in parallel across git worktrees; review changes per worktree before merging to avoid conflicting or unreviewed edits.
Remote cloud workers can run agent sessions on external infrastructure; understand where code executes before enabling them.
Scaling agent workflows to a whole team increases the blast radius of automated edits, so keep human review and branch protections in place.
Privacy notes
Because it builds on Claude Code, repository code and context are sent to Anthropic's API to power the agent.
Remote cloud workers process your code and context on external infrastructure; review the provider's terms before sending private code.
Any API keys or credentials used by Claude Code and CodeLayer should be stored as secrets, not committed to source control.
Team and context-engineering features can share prompts, context, and workflow data across collaborators, so avoid placing secrets in shared context.
Prerequisites
Claude Code, since CodeLayer is built on top of it and orchestrates Claude Code sessions.
An Anthropic account or API access for the underlying Claude Code agent.
A recent CodeLayer build from the project's GitHub releases or the waitlist for early access.
Git, since parallel-session workflows rely on worktrees.
## Overview
HumanLayer is the open-source project behind CodeLayer, an IDE for orchestrating
AI coding agents. It is built on Claude Code and aims to help builders and teams
get AI coding agents to solve hard problems in large, complex codebases — from a
single laptop up to an entire team.
The project is released under Apache-2.0. CodeLayer focuses on keyboard-first
workflows, context engineering for scaling AI-first development across a team,
and running Claude Code sessions in parallel.
## Features
- Keyboard-first workflows designed for speed and control.
- Context engineering to scale AI-first development across a team.
- MultiClaude: run multiple Claude Code sessions in parallel, including across
git worktrees and remote cloud workers.
- Built on Claude Code, so it reuses the underlying agent and its tooling.
- Open-source under Apache-2.0, with team and consulting services available.
## Use Cases
- Drive several Claude Code sessions at once across isolated worktrees.
- Standardize AI-assisted development context and workflows across a team.
- Tackle large-codebase tasks that need orchestration beyond a single session.
- Offload agent sessions to remote cloud workers when local resources are tight.
## Disclosure
Editorial listing. No paid placement or affiliate relationship. CodeLayer is
open source (Apache-2.0); HumanLayer also offers team and consulting services.
About this resource
Overview
HumanLayer is the open-source project behind CodeLayer, an IDE for orchestrating
AI coding agents. It is built on Claude Code and aims to help builders and teams
get AI coding agents to solve hard problems in large, complex codebases — from a
single laptop up to an entire team.
The project is released under Apache-2.0. CodeLayer focuses on keyboard-first
workflows, context engineering for scaling AI-first development across a team,
and running Claude Code sessions in parallel.
Features
Keyboard-first workflows designed for speed and control.
Context engineering to scale AI-first development across a team.
MultiClaude: run multiple Claude Code sessions in parallel, including across
git worktrees and remote cloud workers.
Built on Claude Code, so it reuses the underlying agent and its tooling.
Open-source under Apache-2.0, with team and consulting services available.
Use Cases
Drive several Claude Code sessions at once across isolated worktrees.
Standardize AI-assisted development context and workflows across a team.
Tackle large-codebase tasks that need orchestration beyond a single session.
Offload agent sessions to remote cloud workers when local resources are tight.
Disclosure
Editorial listing. No paid placement or affiliate relationship. CodeLayer is
open source (Apache-2.0); HumanLayer also offers team and consulting services.
Open-source project behind CodeLayer, an IDE for orchestrating AI coding agents built on Claude Code, with keyboard-first workflows, team context engineering, and parallel Claude Code sessions across worktrees and cloud workers.
Open-source status companion for Claude Code and Codex with live local session state, your-turn alerts, usage views, and native macOS and Windows applications.
Open-source infrastructure for securely running AI-generated code in isolated sandboxes that start in milliseconds, with SDKs for Python, TypeScript, and other languages, persistent snapshots, and an optional managed cloud.
Open-source infrastructure for running AI-generated code in secure, isolated cloud sandboxes, with Python and JavaScript SDKs, a Code Interpreter package, and self-hosting options.
✓CodeLayer orchestrates AI coding agents that edit files and run commands in your repositories, so it inherits the execution risks of the underlying Claude Code agent.
MultiClaude runs multiple Claude Code sessions in parallel across git worktrees; review changes per worktree before merging to avoid conflicting or unreviewed edits.
Remote cloud workers can run agent sessions on external infrastructure; understand where code executes before enabling them.
Scaling agent workflows to a whole team increases the blast radius of automated edits, so keep human review and branch protections in place.
✓Agent Island reads local Claude Code and Codex session files to determine session state; review the requested filesystem access before use.
The macOS release is ad-hoc signed rather than Apple-notarized, so first launch requires right-clicking the app and choosing Open.
Windows packages are distributed through GitHub Releases, Scoop, and winget; verify the release source before installation.
✓Daytona is purpose-built to execute arbitrary, AI-generated code; only run untrusted code inside its isolated sandboxes, never on the host.
Each sandbox has its own kernel, filesystem, and network stack, but sandboxes can make outbound network requests unless network limits are configured.
Sandboxes support computer use, Git operations, and command execution; scope what an agent can do and review declarative builder configurations before use.
Self-hosting runs runner compute nodes and Docker services that need elevated host privileges; isolate the deployment from production systems.
Persistent snapshots retain sandbox filesystem state across sessions, which can preserve secrets or sensitive files written during execution.
✓E2B is built to execute arbitrary, AI-generated code; run such code only inside its isolated cloud sandboxes, never directly on a developer machine.
Sandbox network and filesystem access depend on configuration; review and restrict sandbox capabilities before running untrusted code.
Generated code can still perform destructive or unexpected actions within a sandbox, so treat sandbox outputs and side effects with caution.
Self-hosting deploys cloud infrastructure via Terraform that you are responsible for securing, patching, and isolating from production systems.
Privacy notes
✓Because it builds on Claude Code, repository code and context are sent to Anthropic's API to power the agent.
Remote cloud workers process your code and context on external infrastructure; review the provider's terms before sending private code.
Any API keys or credentials used by Claude Code and CodeLayer should be stored as secrets, not committed to source control.
Team and context-engineering features can share prompts, context, and workflow data across collaborators, so avoid placing secrets in shared context.
✓Session monitoring is local and the project states that the app has no Agent Island account and no product telemetry.
Usage views may call provider usage APIs with existing local credentials; those requests remain subject to the provider's privacy terms.
Local transcript files and provider credentials can contain sensitive data and should not be included in public screenshots, issues, or logs.
✓Using the managed cloud sends your code, files, and execution data to Daytona-operated infrastructure; review their terms before processing sensitive data.
The platform emits OpenTelemetry metrics, log streaming, and audit logs that can capture command output and activity.
API keys grant access to your sandboxes and organization; store them as secrets and never commit them to source control.
Self-hosting keeps execution data on your own infrastructure but you become responsible for log retention, access control, and isolation.
✓On the managed cloud, your code and execution data are sent to and run on E2B-operated infrastructure; review their privacy terms before processing sensitive data.
API keys grant access to your sandboxes; store them in environment variables or a secrets manager and never commit them to source control.
Data passed into a sandbox (files, inputs, environment variables) lives in that sandbox for its lifetime; avoid sending secrets you do not need there.
Self-hosting keeps execution data on your own infrastructure, making log retention, access control, and isolation your responsibility.
Prerequisites
Claude Code, since CodeLayer is built on top of it and orchestrates Claude Code sessions.
An Anthropic account or API access for the underlying Claude Code agent.
A recent CodeLayer build from the project's GitHub releases or the waitlist for early access.
Git, since parallel-session workflows rely on worktrees.
macOS 13 or later, or Windows 10 or later.
A local Claude Code or Codex installation with session data available to the current user.
A Daytona Cloud account and API key for the managed service, or self-hosted infrastructure for the open-source platform.
Python 3.8+ for the `daytona` SDK or Node.js 18+ for the `@daytona/sdk` TypeScript SDK.
Docker and Docker Compose to run supporting services (PostgreSQL, Redis) when self-hosting.
Nix with flakes enabled or a devcontainer-compatible editor for local development of the platform itself.
An E2B account and API key from the dashboard, set as the `E2B_API_KEY` environment variable, for the managed cloud.
Python 3.8+ for the `e2b` / `e2b-code-interpreter` SDK, or Node.js 18+ for the `e2b` / `@e2b/code-interpreter` SDK.
Self-hosting requires Terraform and a supported cloud provider to deploy the sandbox infrastructure.