HumanLayer

Orchestrator · Last verified 2026-09-30

TL;DR

HumanLayer is a closed-source commercial IDE and cloud service from the HumanLayer team that runs Claude Code and Codex sessions inside shared tasks with plan artifacts, review comments and remote daemons. Its GitHub repository is now a public issue tracker whose README calls the code there deprecated. It suits teams coordinating coding agents.

Key facts

HumanLayer key facts. Data as of 2026-09-30.
Type Orchestrator
Languages / SDKs Go, TypeScript
License unknown
Pricing model Hosted, paid
Orchestration pattern Pipeline
GitHub stars 11,630 (as of 2026-09-30)
GitHub forks 958
Last push 2026-06-19
Latest release pro-0.20.0
Repository humanlayer/humanlayer
Website www.humanlayer.dev
Documentation docs.humanlayer.com
Last verified 2026-09-30

Key features

  • Tasks group several agent sessions, a synced .humanlayer/tasks/<slug>/ folder of artifacts, and comments, so work can continue across agents, people and machines. (source)
  • Guided workflows (Oneshot, RPI, PRD-Oriented, Freeform) split work into research, design, structure outline, plan and implementation phases, each producing a reviewable artifact. (source)
  • Sessions run Claude Code or Codex; since 0.179.0 a session can be handed from one agent to the other on the same task and worktree. (source)
  • Remote daemons run sessions on a VM, workstation or private-network host, controlled from app.humanlayer.com in a browser or on a phone. (source)
  • RPI skills start sub-agents (codebase locator, analyzer, implementer, reviewer) with documented model and effort rules for Claude Code and Codex. (source)
  • Codex sessions can target Amazon Bedrock, Azure AI Foundry or the OpenAI Responses API through CODELAYER_CODEX_* environment variables. (source)
  • Tasks can start from GitHub issues, Linear or Jira tickets, and selected events can be sent to Slack. (source)

Architecture and orchestration pattern

Pattern: Pipeline

The current product is a desktop app (macOS), a web and mobile UI, a HumanLayer API and daemons. A daemon, either started by the desktop app or run on a remote host, launches Claude Code or Codex sessions on its machine; the API passes work to connected daemons and streams session events back to every interface. The code in the humanlayer/humanlayer repository (the earlier open-source CodeLayer daemon, UI and CLI, plus the removed SDK) is marked deprecated in its README and is not the source of this app.

Orchestration follows workflow phases. A task picks a workflow; guided ones begin with research questions, move through design and a structure outline split into vertical slices, then implement phase by phase. Skills for each phase run in the main session and start sub-agents for focused jobs such as locating code, analysing it, implementing or reviewing. Some transitions can auto-advance; design and outline handoffs always wait for a person.

State lives in tasks. Each task has a local directory that the daemon syncs to the cloud whenever the agent reads or writes a file there with its file tools; text artifacts are stored in the cloud (up to 10 MB each) and appear in the artifact view for comments. Sessions keep their own messages and settings, while the task keeps them grouped across workstations.

Human in the loop

Checkpoints are built into the workflows: a design discussion keeps each choice open until the user answers, a PRD needs approval of the full product solution, a technical design needs separate approval of system and program design, feedback on a structure outline changes the outline instead of starting implementation, and normal implementation pauses for manual review after its checks pass. Reviewers comment inline on synced artifacts (including guests through public review links since 0.179.0), and agents read those comments in later sessions. Users can also message a running session from the web or mobile UI. The deprecated CLI in the repository offered an MCP permission-prompt tool for Claude Code approvals.

Harnesses it can drive

Protocols

MCP, A2A and AG-UI support for HumanLayer. See the full matrix.
ProtocolSupportNote
MCP Partial evidence
checked 2026-09-30
Only in deprecated code: the repository's hlyr CLI documents an MCP server (humanlayer mcp serve) and a claude_approvals permission-prompt tool for Claude Code. The current app's docs mention MCP only as the agent's own configuration (Claude settings and MCP config loaded from the primary repository, OAuth MCP servers connecting before a session starts); no HumanLayer MCP server is documented.
A2A Unknown
checked 2026-09-30
No mention of A2A in docs.humanlayer.com pages read, the homepage or the repository README; GitHub code search for 'a2a' only matched hashes in generated and lock files.
AG-UI Unknown
checked 2026-09-30
No mention of AG-UI in docs.humanlayer.com pages read, the homepage or the repository; GitHub code search for 'ag-ui' returned nothing, and HumanLayer is not listed in the AG-UI README.

Best for

  • Teams that want research, design and plan documents reviewed and approved before a coding agent writes code. (shortlist)
  • Running Claude Code or Codex sessions on remote or private-network hosts while steering them from a browser or phone. (shortlist)
  • Organisations that need SSO/SAML, audit logs and on-prem or private-VPC deployment, which the Enterprise tier lists. (shortlist)
  • Moving a task between Claude Code and Codex without losing its transcript or worktree.

Not for

  • Anyone who needs source code to inspect or modify: the current app is not open source and the repository's code is deprecated.
  • Linux or Windows users who want a native desktop app; those platforms run sessions through a remote daemon and the browser UI.
  • Larger teams without budget for per-user pricing beyond the small free Starter tier.

Quickstart

brew install --cask humanlayer/humanlayer/humanlayer

Install not yet verified by this site. What this means

# macOS app (needs a HumanLayer account; Claude Code installed and signed in)
brew trust --tap humanlayer/humanlayer
brew install --cask humanlayer/humanlayer/humanlayer
open /Applications/HumanLayer.app      # sign in; the local daemon starts with the app

# CLI for Codex sessions or a remote daemon host
npm install -g @humanlayer/cli@latest
humanlayer login
humanlayer agents auth codex
humanlayer agents --help               # launch commands change between releases

# In the app: Create Task -> Workflow ONESHOT or RPI -> Coding Agent Claude Code or codex
# Inside an RPI session, phases are driven with skills, e.g.:
#   /rpi:create-outline turn the approved design into testable implementation phases
#   /rpi:describe-pr

Common pitfalls

  • The humanlayer/humanlayer repository is a public issue tracker; its README says the code there is deprecated. Install the app from Homebrew or the download link instead of building the repository.
  • Requires a HumanLayer account. The desktop app targets macOS on Apple silicon; Linux, Windows and other hosts use a remote daemon.
  • Claude Code (or Codex) must already be installed and signed in; HumanLayer uses your own subscriptions or API keys.
  • With worktree timing set to Never, the session edits the selected checkout directly, so use a clean branch.
  • The browser app does not yet offer workspace management, an embedded terminal or path auto-complete.
  • Custom Codex endpoints need both CODELAYER_CODEX_BASE_URL and CODELAYER_CODEX_API_KEY; quit the app and reopen it from the same terminal so it inherits the variables.
  • Only files the agent touches with its file tools inside the task directory sync to the cloud.

Official quickstart

Pros

  • Workflow checkpoints keep product and design decisions with the user, and implementation pauses for review between phases. (source)
  • Tasks keep sessions, artifacts and review comments together, so a later session or a teammate can continue from the same context. (source)
  • Works with both Claude Code and Codex and can hand a running task from one to the other. (source)
  • Remote daemons let sessions run next to private infrastructure while the UI stays in the browser or on a phone. (source)
  • Actively released, with versions 0.176.0 to 0.179.0 published between 18 and 29 September 2026. (source)

Cons

  • The GitHub repository only serves public issues now; its README says the code there is deprecated, so the stars and forks reflect the earlier open-source project. (source)
  • The current app is closed source; the homepage FAQ answers 'Is HumanLayer open source?' with 'Not yet'. (source)
  • Paid per user beyond the free Starter tier (up to 3 team members and 200 sessions a month), on top of your own model subscriptions. (source)
  • The browser app lacks workspace management, an embedded terminal and path auto-complete, and the native app is macOS only. (source)
  • The older HumanLayer SDK for human approval of agent tool calls was removed from the repository. (source)

Alternatives

FAQ

Is HumanLayer open source?

The repository carries an Apache License 2.0 notice, but its README says that code is deprecated. The current HumanLayer app is not open source; the homepage FAQ answers 'Not yet'.

What happened to CodeLayer and the HumanLayer SDK?

Both lived in the humanlayer/humanlayer repository. The SDK was removed (see humanlayer.md), and the README now calls the remaining code deprecated and points to the rebuilt product at humanlayer.com. The current docs still use CODELAYER_ in some environment variable names.

Which coding agents does HumanLayer run?

The docs cover Claude Code and Codex, including handing a session between them. The homepage FAQ also lists Copilot and Fireworks.

Does HumanLayer support MCP?

Only in deprecated code. The hlyr CLI in the repository shipped an MCP server and a Claude Code approval tool. The current docs treat MCP as the coding agent's own configuration, which sessions load from the primary repository; they document no HumanLayer MCP server.

How much does HumanLayer cost?

The homepage lists a free Starter tier (up to 3 team members, 200 sessions a month), Pro at $100 per user per month, and a custom-priced Enterprise tier. Model usage runs on your own Claude, Codex or other subscriptions.

Sources

Unknown fields: license: GitHub reports NOASSERTION; the LICENSE file contains only the short Apache License 2.0 notice ('Copyright (c) 2024, humanlayer Authors', pointing to apache.org), not the full license text. It covers the repository's code, which the README marks deprecated; the current HumanLayer app is closed source. languages: Go and TypeScript are the languages of the deprecated repository code (per DEVELOPMENT.md); the current app's implementation language is not documented. latest_release pro-0.20.0 is from December 2025 and belongs to the deprecated code. protocols.a2a and protocols.agui: no mentions in the docs pages, homepage, README or code search.

Something wrong or out of date, or do you maintain HumanLayer and want this page removed? Report a correction or request removal.