51 of 51 criteria have a sourced finding; 47 were also cross-checked by a second agent. Every comparison that includes CodeLayer / HumanLayer links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
The complete current application repository lists macOS Electron/Tauri shells, web clients, a daemon and CLI. It has no native Windows/Linux desktop shell or iOS/Android app. User-host daemons can use other operating systems, and phone browsers can create, watch and message sessions.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
9 atomic answers
Desktop os [partial] The full app inventory explicitly identifies macOS desktop shells; Windows/Linux support is daemon-host access, not a native desktop client. Sources: code-layer:nov07-repo, code-layer:nov07-first.
Mobile apps [unsupported] The complete repository app inventory contains desktop/web components and no native iOS/Android application. Sources: code-layer:nov07-repo.
Browser [supported] A browser on a computer or phone can create, watch and message remote sessions; embedded terminal and workspace configuration remain desktop-only. Sources: code-layer:nov07-remote.
Mobile browser [supported] A browser on a computer or phone can create, watch and message remote sessions; embedded terminal and workspace configuration remain desktop-only. Sources: code-layer:nov07-remote.
Editor extensions [unknown] Not established for editor extensions in the November 7 first-party source pass. Minimum macOS version, native mobile apps, editor extensions and full cross-client approval/review actions were not resolved; no device handoff was tested.
Task actions [partial] Browser/phone session creation and messaging are documented; desktop supports workflow and worktree setup. Complete client-by-client approve/review/resume parity was not tested. Sources: code-layer:nov07-remote, code-layer:nov07-first.
Notifications [supported] Recent release notes document an attention bell for sessions waiting on a user. Notification delivery across clients was not tested. Sources: code-layer:nov07-releases.
Cross device continuity [partial] The same remote-host sessions can be controlled from phone/browser. Cross-device operation is documented, not observed. Sources: code-layer:nov07-remote.
HumanLayer integrates Claude Code, Codex, OpenCode and Pi. The closed schema lists those families and product-specific CodeLayer/Fold paths, with a stricter daemon-launchable subset; other supported terminal sessions can be mirrored. Model gateways do not add another coding harness.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
5 atomic answers
Harnesses [supported] The closed schema covers Claude aliases, Codex, OpenCode, Pi and product-specific CodeLayer/Fold. Cursor, Gemini CLI, Grok, Aider and Antigravity are absent and rejected as undeclared coding agents. Sources: code-layer:gap-harness-schema, code-layer:nov07-repo.
Model providers [supported] Claude and Codex routes include their native services and documented custom gateways, OpenAI Responses, Bedrock and Azure endpoint configuration. Sources: code-layer:nov07-codex, code-layer:nov07-gateway.
Custom adapters [partial] Plugins mirror Claude Code, OpenCode and Pi sessions; the coding-agent schema is a closed list and no general adapter API is documented. Sources: code-layer:b09-readme, code-layer:b09-agent-schema.
Session integration [supported] Daemons launch coding sessions and send events through the API; the UI can watch and message them. Sources: code-layer:nov07-remote.
Mixed harness operation [partial] Separate task sessions can use different agents; Claude/Codex transcript handoff is documented. No mixed-harness operation was observed. Sources: code-layer:nov07-tasks, code-layer:nov07-releases.
The pricing FAQ explicitly permits existing Claude/Codex subscriptions or API keys. Codex sign-in and custom API configuration are separate paths. The FAQ says HumanLayer has no separate per-token bill; provider and compute charges remain the user’s responsibility. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
Subscription plan eligibility, local models and multi-account switching were not resolved.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
7 atomic answers
Agent subscriptions [supported] The pricing FAQ explicitly permits existing Claude/Codex subscriptions or API keys. Codex sign-in and custom API configuration are separate paths. Sources: code-layer:nov07-pricing, code-layer:nov07-codex.
Api accounts [supported] The pricing FAQ explicitly permits existing Claude/Codex subscriptions or API keys. Codex sign-in and custom API configuration are separate paths. Sources: code-layer:nov07-pricing, code-layer:nov07-codex.
Vendor credits [supported] The FAQ says HumanLayer has no separate per-token bill; provider and compute charges remain the user’s responsibility. Sources: code-layer:nov07-pricing.
Local models [unknown] Not established for local models in the November 7 first-party source pass. Subscription plan eligibility, local models and multi-account switching were not resolved.
Account switching [unknown] Not established for account switching in the November 7 first-party source pass. Subscription plan eligibility, local models and multi-account switching were not resolved.
Vendor account requirement [partial] Hosted setup requires a HumanLayer account; self-hosted code exists, but independent account/auth setup was not tested. Sources: code-layer:nov07-first, code-layer:nov07-open-core.
Provider restrictions [supported] Custom Codex endpoints require paired URL/key settings, secure URLs and supported reasoning fields; Bedrock/Azure have specific auth/model rules. Sources: code-layer:nov07-codex.
The tutorial names macOS, an account, signed-in Claude Code and Git, then creates an inline task/session. It is a documented procedure, with no elapsed-time measurement. The tutorial can clone a GitHub repository; GitHub App issue intake is separately documented. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No fresh-install timing or no-Git/local-only-Git/managed-cloud provisioning fixture was run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
7 atomic answers
First task setup [partial] The tutorial names macOS, an account, signed-in Claude Code and Git, then creates an inline task/session. It is a documented procedure, with no elapsed-time measurement. Sources: code-layer:nov07-first.
No git [unknown] Not established for no git in the November 7 first-party source pass. No fresh-install timing or no-Git/local-only-Git/managed-cloud provisioning fixture was run.
Local git without remote [unknown] Not established for local git without remote in the November 7 first-party source pass. No fresh-install timing or no-Git/local-only-Git/managed-cloud provisioning fixture was run.
Prerequisite guidance [partial] The tutorial names macOS, an account, signed-in Claude Code and Git, then creates an inline task/session. It is a documented procedure, with no elapsed-time measurement. Sources: code-layer:nov07-first.
Managed cloud setup [unknown] Not established for managed cloud setup in the November 7 first-party source pass. No fresh-install timing or no-Git/local-only-Git/managed-cloud provisioning fixture was run.
Byo vps onboarding [supported] A dedicated remote guide covers npm installation, device login or launch token and a user-managed systemd service. The user supplies host, checkout and credentials. Sources: code-layer:nov07-remote-setup.
Product CLI/RPC routes create/list tasks and launch/list sessions; automation run uses a checkout and PAT. Full operation parity and API stability were not tested. Interactive login stores host credentials; automations use expiring personal access tokens and separate provider credentials.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No complete SDK/MCP/webhook inventory or API stability commitment was found in the checked docs and CLI source.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Sdk [unknown] Not established for sdk in the November 7 first-party source pass. No complete SDK/MCP/webhook inventory or API stability commitment was found in the checked docs and CLI source.
Mcp server [unknown] Not established for mcp server in the November 7 first-party source pass. No complete SDK/MCP/webhook inventory or API stability commitment was found in the checked docs and CLI source.
Webhooks [unknown] Not established for webhooks in the November 7 first-party source pass. No complete SDK/MCP/webhook inventory or API stability commitment was found in the checked docs and CLI source.
Stability [partial] Docs warn the session launch command can change between CLI releases; no API stability policy found. Sources: code-layer:b09-codex.
The current repository includes Claude Code, OpenCode and Pi session plugins and built-in HumanLayer/RPI skills. Workspace docs load repository skills/instructions across repos. MCP and Claude settings are inherited according to the launch directory, not universally merged by the ADE. No external-tool call was tested. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No authenticated external-tool call was run; inherited harness tools are not product-managed integration proof.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
7 atomic answers
Mcp client [partial] Sessions wait for MCP servers, including OAuth ones, to connect before the agent starts; MCP config comes from the primary repository. Sources: code-layer:b09-rn-mcp, code-layer:b09-wsmodel.
Plugins [supported] The current repository includes Claude Code, OpenCode and Pi session plugins and built-in HumanLayer/RPI skills. Sources: code-layer:nov07-repo.
Custom tools [unknown] Not established for custom tools in the November 7 first-party source pass. No authenticated external-tool call was run; inherited harness tools are not product-managed integration proof.
Instructions import [partial] Workspace docs load repository skills/instructions across repos. MCP and Claude settings are inherited according to the launch directory, not universally merged by the ADE. No external-tool call was tested. Sources: code-layer:nov07-workspace-model.
Authentication [partial] GitHub installation requires an organization admin and repository-scoped contents/issues/PR permissions. This establishes that integration, not every external tool. Sources: code-layer:nov07-github.
Permission scope [partial] GitHub installation requires an organization admin and repository-scoped contents/issues/PR permissions. This establishes that integration, not every external tool. Sources: code-layer:nov07-github.
Integration owner [partial] Workspace docs load repository skills/instructions across repos. MCP and Claude settings are inherited according to the launch directory, not universally merged by the ADE. No external-tool call was tested. Sources: code-layer:nov07-workspace-model.
The current pinned monorepo identifies a shared web UI inside macOS Electron and Tauri shells. This does not measure responsiveness or imply native platform widgets.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No native mobile implementation was identified; desktop framework choice is not a speed measurement.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
4 atomic answers
Desktop implementation [supported] The current pinned monorepo identifies a shared web UI inside macOS Electron and Tauri shells. This does not measure responsiveness or imply native platform widgets. Sources: code-layer:nov07-repo.
Mobile implementation [partial] Phones use the web and mobile UI; the public repo has a Tauri desktop shell and no iOS or Android project. Sources: code-layer:b09-rd, code-layer:b09-native.
Hybrids [supported] The current pinned monorepo identifies a shared web UI inside macOS Electron and Tauri shells. This does not measure responsiveness or imply native platform widgets. Sources: code-layer:nov07-repo.
Implementation evidence [supported] The current pinned monorepo identifies a shared web UI inside macOS Electron and Tauri shells. This does not measure responsiveness or imply native platform widgets. Sources: code-layer:nov07-repo.
Users create inline tasks with a name/slug; CLI examples expose persistent task IDs and optional ticket fields. GitHub issues, Linear issues and Jira Cloud tickets can seed HumanLayer tasks. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Local creation [supported] Users create inline tasks with a name/slug; CLI examples expose persistent task IDs and optional ticket fields. Sources: code-layer:nov07-first, code-layer:nov07-launch-task.
Prompt intake [supported] Users create inline tasks with a name/slug; CLI examples expose persistent task IDs and optional ticket fields. Sources: code-layer:nov07-first, code-layer:nov07-launch-task.
Chat git triggers [partial] GitHub Actions schedules or events can start automation sessions through humanlayer automation run. Sources: code-layer:b09-automation.
Authoritative tracker [partial] The GitHub or Linear issue stays the source; HumanLayer posts artifact links back and syncs Linear status. Sources: code-layer:b09-github, code-layer:b09-linear.
Sync [partial] GitHub imports issue/comments into ticket.md and writes artifact links back. Linear additionally syncs named workflow states. Complete two-way field editing is not established. Sources: code-layer:nov07-github, code-layer:nov07-linear.
Supported edits [partial] GitHub imports issue/comments into ticket.md and writes artifact links back. Linear additionally syncs named workflow states. Complete two-way field editing is not established. Sources: code-layer:nov07-github, code-layer:nov07-linear.
External roundtrips [partial] GitHub imports issue/comments into ticket.md and writes artifact links back. Linear additionally syncs named workflow states. Complete two-way field editing is not established. Sources: code-layer:nov07-github, code-layer:nov07-linear.
Guided workflows save research/design/outline/plan artifacts and allow comments and in-place iteration before implementation. Artifacts drive later phases; attributable revision semantics and in-run tests remain unverified. Task artifacts and files sync across sessions/workstations. Restart durability was not tested.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
7 atomic answers
Plans [partial] Guided workflows save research/design/outline/plan artifacts and allow comments and in-place iteration before implementation. Artifacts drive later phases; attributable revision semantics and in-run tests remain unverified. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Acceptance criteria [partial] Each structure-outline phase names one testable result, its files and its checks. Sources: code-layer:b09-phases.
Editors [partial] Guided workflows save research/design/outline/plan artifacts and allow comments and in-place iteration before implementation. Artifacts drive later phases; attributable revision semantics and in-run tests remain unverified. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Revisions [partial] Guided workflows save research/design/outline/plan artifacts and allow comments and in-place iteration before implementation. Artifacts drive later phases; attributable revision semantics and in-run tests remain unverified. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Implementation links [partial] Guided workflows save research/design/outline/plan artifacts and allow comments and in-place iteration before implementation. Artifacts drive later phases; attributable revision semantics and in-run tests remain unverified. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Amendment [partial] Guided workflows save research/design/outline/plan artifacts and allow comments and in-place iteration before implementation. Artifacts drive later phases; attributable revision semantics and in-run tests remain unverified. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Restart persistence [partial] Task artifacts and files sync across sessions/workstations. Restart durability was not tested. Sources: code-layer:nov07-tasks.
/hl:orchestrate breaks work into tasks; workflow checkpoints hold design and outline handoffs; Linear states can follow phases. Native epics, arbitrary hierarchy and blockers were not established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Native epics, arbitrary hierarchy, blockers and dispatch enforcement were not established; the evolving-scope fixture was not run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Epics [partial] /hl:orchestrate breaks work down and launches tasks in separate worktrees; no native epic entity is documented. Sources: code-layer:b09-rn-orch.
Hierarchy [unknown] Not established for hierarchy in the November 7 first-party source pass. The task/workflow docs and orchestration references did not establish epics, arbitrary hierarchy, blockers or dispatch enforcement; the evolving-scope fixture was not run.
Blockers [unknown] Not established for blockers in the November 7 first-party source pass. The task/workflow docs and orchestration references did not establish epics, arbitrary hierarchy, blockers or dispatch enforcement; the evolving-scope fixture was not run.
Readiness [unknown] Not established for readiness in the November 7 first-party source pass. The task/workflow docs and orchestration references did not establish epics, arbitrary hierarchy, blockers or dispatch enforcement; the evolving-scope fixture was not run.
Enforcement [unknown] Not established for enforcement in the November 7 first-party source pass. The task/workflow docs and orchestration references did not establish epics, arbitrary hierarchy, blockers or dispatch enforcement; the evolving-scope fixture was not run.
State propagation [partial] With Linear auto-advance, issue states follow phase starts and artifacts. Sources: code-layer:b09-linear.
Task to epic [unknown] Not established for task to epic in the November 7 first-party source pass. The task/workflow docs and orchestration references did not establish epics, arbitrary hierarchy, blockers or dispatch enforcement; the evolving-scope fixture was not run.
Identity retention [unknown] Not established for identity retention in the November 7 first-party source pass. The task/workflow docs and orchestration references did not establish epics, arbitrary hierarchy, blockers or dispatch enforcement; the evolving-scope fixture was not run.
Workflow constraints [supported] Design and outline handoffs always wait for the user; normal implementation waits for review after checks. Sources: code-layer:b09-phases, code-layer:b09-wf-guide.
Repository skills/instructions and shared task documents supply context. Task files are distinct from managed cross-task memory or a living product specification. Saved phase artifacts can be iterated and later artifacts take precedence. This is document correction, not verified stale-memory repair. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
10 atomic answers
Instructions [partial] Repository skills/instructions and shared task documents supply context. Task files are distinct from managed cross-task memory or a living product specification. Sources: code-layer:nov07-workspace-model, code-layer:nov07-tasks.
Skills [partial] Repository skills/instructions and shared task documents supply context. Task files are distinct from managed cross-task memory or a living product specification. Sources: code-layer:nov07-workspace-model, code-layer:nov07-tasks.
Project docs [partial] Repository skills/instructions and shared task documents supply context. Task files are distinct from managed cross-task memory or a living product specification. Sources: code-layer:nov07-workspace-model, code-layer:nov07-tasks.
Memory [partial] The automation guide suggests a repository markdown file as agent memory; no managed memory is documented. Sources: code-layer:b09-automation.
Scope [partial] Repository skills/instructions and shared task documents supply context. Task files are distinct from managed cross-task memory or a living product specification. Sources: code-layer:nov07-workspace-model, code-layer:nov07-tasks.
Provenance [partial] Shared-session messages show who sent them. Sources: code-layer:b09-rn-collab.
Correction [partial] Saved phase artifacts can be iterated and later artifacts take precedence. This is document correction, not verified stale-memory repair. Sources: code-layer:nov07-workflows.
Freshness [unknown] Not established for freshness in the November 7 first-party source pass. The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Takeover continuity [partial] Several people/agents can continue a task through separate sessions and synchronized task files. Exact runtime takeover was not tested. Sources: code-layer:nov07-tasks.
Release notes document image attachments in task intake. The requested architecture-conflict scenario was not run.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Repository search/index freshness and the API-conflict retrieval/review fixture were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Code search [partial] codebase-locator, codebase-analyzer and codebase-pattern-finder sub-agents search the code; no index is documented. Sources: code-layer:b09-subagents.
Indexing [unknown] Not established for indexing in the November 7 first-party source pass. Repository search/index freshness and the API-conflict retrieval/review fixture were not tested.
External knowledge [partial] A web-search-researcher sub-agent gathers web sources. Sources: code-layer:b09-subagents.
Multimodal inputs [supported] Release notes document image attachments in task intake. The requested architecture-conflict scenario was not run. Sources: code-layer:nov07-releases.
Access scope [unknown] Not established for access scope in the November 7 first-party source pass. Repository search/index freshness and the API-conflict retrieval/review fixture were not tested.
Api retrieval [unknown] Not established for api retrieval in the November 7 first-party source pass. Repository search/index freshness and the API-conflict retrieval/review fixture were not tested.
Citations [partial] Research questions keep exact source pointers and research records findings from code, tests and named sources. Sources: code-layer:b09-wf-ref, code-layer:b09-phases.
Conflict detection [partial] A fixed precedence rule resolves disagreeing artifacts (later wins); no detection is documented. Sources: code-layer:b09-wf-ref, code-layer:b09-wf-guide.
Review enforcement [partial] Workflow checkpoints require approval of the PRD and of TDD system and program design; these are skill instructions. Sources: code-layer:b09-phases, code-layer:b09-wf-ref.
Inline persistent task containers group multiple independent sessions, so a ticket in an external tracker is optional. A native backlog with issue-state semantics is not established. The recent minimalist UI allows task renaming; full native issue-field editing remains unverified. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Priorities, native task-state operations and search/filter depth were not established by task/docs/CLI references.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Edit [partial] The recent minimalist UI allows task renaming; full native issue-field editing remains unverified. Sources: code-layer:nov07-releases.
Discuss [partial] Task artifacts have shared review comments visible to subsequent agents. This is artifact discussion, not proof of a separate issue discussion thread. Sources: code-layer:nov07-tasks.
Prioritize [unknown] Not established for prioritize in the November 7 first-party source pass. Priorities, labels, assignment edits, idea parking and native task-state operations were not established by task/docs/CLI references.
Search [unknown] Not established for search in the November 7 first-party source pass. Priorities, labels, assignment edits, idea parking and native task-state operations were not established by task/docs/CLI references.
Filter [partial] CLI task listing supports user ownership filtering, task IDs/slugs and archive metadata. Metadata depth and UI search were not exhaustively tested. Sources: code-layer:nov07-list-tasks.
Archive [supported] Archive tasks and sessions; org admins can archive teammates' tasks. Sources: code-layer:b09-rn-tasks.
Reopen [unknown] Not established for reopen in the November 7 first-party source pass. Priorities, labels, assignment edits, idea parking and native task-state operations were not established by task/docs/CLI references.
Project epic views [partial] A phase board (Todo/Draft to In Review) and task table; Projects V2 preview groups tasks by project. Sources: code-layer:b09-kanban, code-layer:b09-rn-tasks.
Idea parking [partial] The task board has a Todo / Draft column for tasks without later phase labels. Sources: code-layer:b09-kanban.
Explicit dispatch [partial] Inline persistent task containers group multiple independent sessions, so a ticket in an external tracker is optional. A native backlog with issue-state semantics is not established. Sources: code-layer:nov07-first, code-layer:nov07-tasks, code-layer:nov07-launch-task.
Task session separation [partial] Inline persistent task containers group multiple independent sessions, so a ticket in an external tracker is optional. A native backlog with issue-state semantics is not established. Sources: code-layer:nov07-first, code-layer:nov07-tasks, code-layer:nov07-launch-task.
Metadata [partial] CLI task listing supports user ownership filtering, task IDs/slugs and archive metadata. Metadata depth and UI search were not exhaustively tested. Sources: code-layer:nov07-list-tasks.
Durable states [unsupported] The built-in CLI reference explicitly says tasks have no status of their own; session statuses do not establish durable native issue-state transitions. Sources: code-layer:nov07-list-tasks.
External tracker requirement [partial] Inline persistent task containers group multiple independent sessions, so a ticket in an external tracker is optional. A native backlog with issue-state semantics is not established. Sources: code-layer:nov07-first, code-layer:nov07-tasks, code-layer:nov07-launch-task.
The bundled orchestration skill calls product CLI task/session routes with the same durable task IDs shown in the application. Shared issue fields, claims and conflict handling are not established. The skill can inspect PRs and manage task artifacts, which provides retained outputs without proving a native blocker/result issue model.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Update [partial] /hl:orchestrate uploads, copies or moves artifacts between tasks. Sources: code-layer:b09-rn-orch.
Claim [unknown] Not established for claim in the November 7 first-party source pass. The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
Assign [unknown] Not established for assign in the November 7 first-party source pass. The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
State changes [unknown] Not established for state changes in the November 7 first-party source pass. The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
Dependencies [unknown] Not established for dependencies in the November 7 first-party source pass. The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
Children [unknown] Not established for children in the November 7 first-party source pass. The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
Results [partial] The skill can inspect PRs and manage task artifacts, which provides retained outputs without proving a native blocker/result issue model. Sources: code-layer:nov07-orchestrate.
Attribution [partial] Shared-session messages show the sender; usage cost goes to the person who ran the session. Sources: code-layer:b09-rn-collab.
Permissions [unknown] Not established for permissions in the November 7 first-party source pass. The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
Conflicts [unknown] Not established for conflicts in the November 7 first-party source pass. The CLI documents task/session access, not verified agent issue claims, dependency edits, shared state transitions or conflict enforcement.
PRD and TDD artifacts persist in task files with approval checkpoints, version comparison and Slack/public-link review; describe-pr compares the diff with the plan. Cross-release requirement tracking is not established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Cross-release requirements and attributable revision rules were not established; no later-task scenario was run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Human edits [partial] Task design/PRD/TDD artifacts support comments and agent iteration and guide implementation. They do not establish persistent requirements across releases or drift detection. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Agent edits [partial] Task design/PRD/TDD artifacts support comments and agent iteration and guide implementation. They do not establish persistent requirements across releases or drift detection. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Revisions [supported] Artifact Viewer V2 compares artifact versions side by side. Sources: code-layer:b09-rn-artifacts.
Approvals [supported] PRD approval of the full solution and separate TDD system and program design approvals are workflow checkpoints. Sources: code-layer:b09-phases, code-layer:b09-wf-ref.
Implementation links [partial] Task design/PRD/TDD artifacts support comments and agent iteration and guide implementation. They do not establish persistent requirements across releases or drift detection. Sources: code-layer:nov07-workflows, code-layer:nov07-skills.
Later retrieval [supported] Task files download to any workstation that runs the task. Sources: code-layer:b09-tasks.
Drift detection [partial] /rpi:describe-pr compares the full branch diff with the plan when writing the PR. Sources: code-layer:b09-wf-ref.
Review integration [supported] Slack automations post PRD, TDD, outline and comment events; public review links take guest comments. Sources: code-layer:b09-slack, code-layer:b09-rn-collab.
The vendor states local daemons run many sessions in parallel; the bundled skill launches separate task worktrees. No concurrent fixture was observed. The CLI status reference distinguishes running, needs approval, usage-limit waits and failed/lost sessions. Task status is separate and absent in that reference.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
5 atomic answers
Concurrent sessions [supported] The vendor states local daemons run many sessions in parallel; the bundled skill launches separate task worktrees. No concurrent fixture was observed. Sources: code-layer:nov07-pricing, code-layer:nov07-orchestrate.
Concurrent tasks [supported] The vendor states local daemons run many sessions in parallel; the bundled skill launches separate task worktrees. No concurrent fixture was observed. Sources: code-layer:nov07-pricing, code-layer:nov07-orchestrate.
Quotas [unknown] Not established for quotas in the November 7 first-party source pass. The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Observed concurrency [unknown] Not established for observed concurrency in the November 7 first-party source pass. The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Status visibility [supported] The CLI status reference distinguishes running, needs approval, usage-limit waits and failed/lost sessions. Task status is separate and absent in that reference. Sources: code-layer:nov07-list-tasks.
Each task picks its coding agent and host; work queued on an offline host waits for its daemon. Task listing can filter by owning user; exclusive ownership is not established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No two-worker claim/duplicate-dispatch fixture or exclusive ownership contract was established.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
7 atomic answers
Human assignment [partial] Task listing can filter by owning user; this does not establish human assignment edits or enforced exclusive ownership. Sources: code-layer:nov07-list-tasks.
Claims [unknown] Not established for claims in the November 7 first-party source pass. No two-worker claim/duplicate-dispatch fixture or exclusive ownership contract was established.
Queues [partial] Work queued on a registered offline host starts when that host's daemon runs again. Sources: code-layer:b09-local.
Routing [supported] The task chooses the host that runs it. Sources: code-layer:b09-local.
Duplicate prevention [unknown] Not established for duplicate prevention in the November 7 first-party source pass. No two-worker claim/duplicate-dispatch fixture or exclusive ownership contract was established.
Ownership enforcement [unknown] Not established for ownership enforcement in the November 7 first-party source pass. No two-worker claim/duplicate-dispatch fixture or exclusive ownership contract was established.
RPI provides named harness-native research/implementation children; a separate bundled orchestration skill launches/inspects product tasks/sessions through the CLI. Harness-specific model/effort rules apply. Recent release notes show nested Claude subagent calls in the stream. No live child-identity fixture was observed. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No live two-reviewer team, cross-harness message exchange, child reopen or follow-up fixture was run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
12 atomic answers
Roles [partial] RPI provides named harness-native research/implementation children; a separate bundled orchestration skill launches/inspects product tasks/sessions through the CLI. Harness-specific model/effort rules apply. Sources: code-layer:nov07-subagents, code-layer:nov07-orchestrate.
Model harness effort [partial] RPI provides named harness-native research/implementation children; a separate bundled orchestration skill launches/inspects product tasks/sessions through the CLI. Harness-specific model/effort rules apply. Sources: code-layer:nov07-subagents, code-layer:nov07-orchestrate.
Messages [unknown] Not established for messages in the November 7 first-party source pass. No live two-reviewer team, cross-harness message exchange, child reopen or follow-up fixture was run.
Results return [partial] Nested subagent prompts, tool calls and text show as their own groups in the parent stream. Sources: code-layer:b09-rn-subagents.
Cross harness [partial] A session can be handed off between Claude Code and Codex on the same task and worktree with the transcript; not cross-harness delegation. Sources: code-layer:b09-rn-collab.
Orchestration owner [partial] RPI provides named harness-native research/implementation children; a separate bundled orchestration skill launches/inspects product tasks/sessions through the CLI. Harness-specific model/effort rules apply. Sources: code-layer:nov07-subagents, code-layer:nov07-orchestrate.
Activation [unknown] Not established for activation in the November 7 first-party source pass. No live two-reviewer team, cross-harness message exchange, child reopen or follow-up fixture was run.
Authentication [unknown] Not established for authentication in the November 7 first-party source pass. No live two-reviewer team, cross-harness message exchange, child reopen or follow-up fixture was run.
Live progress [partial] Recent release notes show nested Claude subagent calls in the stream. No live child-identity fixture was observed. Sources: code-layer:nov07-releases.
Retained results [partial] Task files retain artifacts across related sessions; retrieval of a completed reviewer child was not tested. Sources: code-layer:nov07-tasks.
Followup [partial] Claude and Codex subagents can be continued after they finish, error or are interrupted. Sources: code-layer:b09-rn-subagents.
Invocation [partial] RPI provides named harness-native research/implementation children; a separate bundled orchestration skill launches/inspects product tasks/sessions through the CLI. Harness-specific model/effort rules apply. Sources: code-layer:nov07-subagents, code-layer:nov07-orchestrate.
User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external workflow configuration. This is documented automation integration, not a hosted scheduler. Automation exits with the session result; inactivity or stop controls the daemon shutdown. No automation was executed.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
official-integration
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No product-owned hosted scheduler or retries policy was established; documented recurring runs rely on user-owned CI/cron.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
8 atomic answers
Schedules [partial] User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external workflow configuration. This is documented automation integration, not a hosted scheduler. Sources: code-layer:nov07-automation.
Events [partial] User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external workflow configuration. This is documented automation integration, not a hosted scheduler. Sources: code-layer:nov07-automation.
Recurring tasks [partial] User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external workflow configuration. This is documented automation integration, not a hosted scheduler. Sources: code-layer:nov07-automation.
Completion conditions [supported] Automation exits with the session result; inactivity or stop controls the daemon shutdown. No automation was executed. Sources: code-layer:nov07-automation.
Scheduler location [partial] User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external workflow configuration. This is documented automation integration, not a hosted scheduler. Sources: code-layer:nov07-automation.
Overlaps [partial] User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external workflow configuration. This is documented automation integration, not a hosted scheduler. Sources: code-layer:nov07-automation.
Retries [unknown] Not established for retries in the November 7 first-party source pass. No product-owned hosted scheduler or retries policy was established; documented recurring runs rely on user-owned CI/cron.
Client independence [partial] User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external workflow configuration. This is documented automation integration, not a hosted scheduler. Sources: code-layer:nov07-automation.
Release notes document shared-session queue/interrupt, Pi stop/reply and attention notifications. These controls were documented, not exercised in chat and terminal fixtures. Usage-limit waits can resume after reset. Host loss, failed sessions and approval waits have explicit CLI status labels; their observed consistency is unknown. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
10 atomic answers
Pause [unknown] Not established for pause in the November 7 first-party source pass. The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Stop [partial] Release notes document shared-session queue/interrupt, Pi stop/reply and attention notifications. These controls were documented, not exercised in chat and terminal fixtures. Sources: code-layer:nov07-releases.
Resume [partial] Usage-limit waits can resume after reset. Host loss, failed sessions and approval waits have explicit CLI status labels; their observed consistency is unknown. Sources: code-layer:nov07-releases, code-layer:nov07-list-tasks.
Steer [partial] Release notes document shared-session queue/interrupt, Pi stop/reply and attention notifications. These controls were documented, not exercised in chat and terminal fixtures. Sources: code-layer:nov07-releases.
Notifications [partial] Release notes document shared-session queue/interrupt, Pi stop/reply and attention notifications. These controls were documented, not exercised in chat and terminal fixtures. Sources: code-layer:nov07-releases.
Pending decisions [partial] Release notes document shared-session queue/interrupt, Pi stop/reply and attention notifications. These controls were documented, not exercised in chat and terminal fixtures. Sources: code-layer:nov07-releases.
Escalation [partial] A notification bell lists sessions waiting on you; Slack automations post selected artifact and comment events to a channel. Sources: code-layer:b09-rn-tasks, code-layer:b09-slack.
Visible errors [partial] Usage-limit waits can resume after reset. Host loss, failed sessions and approval waits have explicit CLI status labels; their observed consistency is unknown. Sources: code-layer:nov07-releases, code-layer:nov07-list-tasks.
Chat terminal parity [partial] The browser app has no embedded terminal; the desktop app does. Sources: code-layer:b09-rd.
Retained history [supported] Tasks retain separate sessions and synchronized artifacts. Sources: code-layer:nov07-tasks.
The UI has attention notifications and a task board, with grouped session history and nested subagents under their parent. Advanced Metrics splits token spend or cost by agent, model, stage, person and mode. No configured runtime fixture was run.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The required 12-state fleet/epic fixture was not run; parent/child and dependency navigation remains unknown.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Fleet fixture [unknown] Not established for fleet fixture in the November 7 first-party source pass. The required 12-state fleet/epic fixture was not run; parent/child and dependency navigation remains unknown.
Parent child [partial] Nested subagents appear as groups under their parent in the session stream. Sources: code-layer:b09-rn-subagents.
Dependencies [unknown] Not established for dependencies in the November 7 first-party source pass. The required 12-state fleet/epic fixture was not run; parent/child and dependency navigation remains unknown.
Attention [partial] The UI documents attention notifications and a task board, with tasks grouping session history. No configured runtime fixture was run. Sources: code-layer:nov07-releases, code-layer:nov07-tasks.
History [partial] The UI documents attention notifications and a task board, with tasks grouping session history. No configured runtime fixture was run. Sources: code-layer:nov07-releases, code-layer:nov07-tasks.
Workload [partial] Advanced Metrics splits token spend or cost by agent, model, stage, person or mode. Sources: code-layer:b09-rn-metrics.
Navigation errors [unknown] Not established for navigation errors in the November 7 first-party source pass. The required 12-state fleet/epic fixture was not run; parent/child and dependency navigation remains unknown.
Fixture mode [unknown] Not established for fixture mode in the November 7 first-party source pass. The required 12-state fleet/epic fixture was not run; parent/child and dependency navigation remains unknown.
Oneshot handles small changes; Freeform omits fixed phases, while RPI/PRD provide guided checkpoints. Users choose agent/model/effort and can amend saved artifacts. A documented skill/CLI route supports orchestration; natural-language discovery and two-reviewer usability were not observed.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Growing-epic identity, natural-language discovery and live/post-completion coordinator relationships were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
10 atomic answers
Quick task [partial] Oneshot handles small changes; Freeform omits fixed phases, while RPI/PRD provide guided checkpoints. Users choose agent/model/effort and can amend saved artifacts. Sources: code-layer:nov07-workflows, code-layer:nov07-subagents.
Growing epic [partial] /hl:orchestrate breaks work into tasks in separate worktrees and starts their sessions. Sources: code-layer:b09-rn-orch.
Presets [partial] Oneshot handles small changes; Freeform omits fixed phases, while RPI/PRD provide guided checkpoints. Users choose agent/model/effort and can amend saved artifacts. Sources: code-layer:nov07-workflows, code-layer:nov07-subagents.
Natural language [partial] The new-task box suggests a workflow from the task's size. Sources: code-layer:b09-rn-orch.
Agent configuration [partial] Oneshot handles small changes; Freeform omits fixed phases, while RPI/PRD provide guided checkpoints. Users choose agent/model/effort and can amend saved artifacts. Sources: code-layer:nov07-workflows, code-layer:nov07-subagents.
In run changes [partial] Oneshot handles small changes; Freeform omits fixed phases, while RPI/PRD provide guided checkpoints. Users choose agent/model/effort and can amend saved artifacts. Sources: code-layer:nov07-workflows, code-layer:nov07-subagents.
Live roles [unknown] Not established for live roles in the November 7 first-party source pass. Growing-epic identity, natural-language discovery and live/post-completion coordinator relationships were not tested.
Retained relationships [unknown] Not established for retained relationships in the November 7 first-party source pass. Growing-epic identity, natural-language discovery and live/post-completion coordinator relationships were not tested.
Discoverability [partial] A documented skill/CLI route supports orchestration; natural-language discovery and two-reviewer usability were not observed. Sources: code-layer:nov07-orchestrate.
Auth friction [unknown] Not established for auth friction in the November 7 first-party source pass. Growing-epic identity, natural-language discovery and live/post-completion coordinator relationships were not tested.
Daemons run on the workstation or user-selected VM/server near the code and private services. The user supplies and supervises that compute; a hosted UI does not imply managed agent compute. The pinned README says Cloud runs the same code, its devstack runs the whole stack locally and self-hosting guides are in progress. No self-hosted install was performed. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
12 atomic answers
Local [supported] Daemons run on the workstation or user-selected VM/server near the code and private services. The user supplies and supervises that compute; a hosted UI does not imply managed agent compute. Sources: code-layer:nov07-remote, code-layer:nov07-remote-setup.
Byo remote [supported] Daemons run on the workstation or user-selected VM/server near the code and private services. The user supplies and supervises that compute; a hosted UI does not imply managed agent compute. Sources: code-layer:nov07-remote, code-layer:nov07-remote-setup.
Self hosted [partial] The pinned README says Cloud runs the same code, its devstack runs the whole stack locally and self-hosting guides are in progress. No self-hosted install was performed. Sources: code-layer:nov07-repo.
Managed cloud [unknown] Not established for managed cloud in the November 7 first-party source pass. The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hybrid [supported] Daemons run on the workstation or user-selected VM/server near the code and private services. The user supplies and supervises that compute; a hosted UI does not imply managed agent compute. Sources: code-layer:nov07-remote, code-layer:nov07-remote-setup.
Provisioning [supported] Daemons run on the workstation or user-selected VM/server near the code and private services. The user supplies and supervises that compute; a hosted UI does not imply managed agent compute. Sources: code-layer:nov07-remote, code-layer:nov07-remote-setup.
Payer [supported] Daemons run on the workstation or user-selected VM/server near the code and private services. The user supplies and supervises that compute; a hosted UI does not imply managed agent compute. Sources: code-layer:nov07-remote, code-layer:nov07-remote-setup.
Resources [partial] Compute is whatever host the user provides: workstation, VM or private machine. Sources: code-layer:b09-rd.
Region [unknown] Not established for region in the November 7 first-party source pass. The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Expiry [partial] Automation daemons exit two minutes after last activity and their hosts expire; long-offline hosts can be removed. Sources: code-layer:b09-rn-tasks, code-layer:b09-automation.
Client disconnect [partial] A supervised remote daemon continues independently of the controlling laptop and is accessible from phone/browser. Host shutdown differs from client disconnection. Sources: code-layer:nov07-remote.
Other device continuation [partial] A supervised remote daemon continues independently of the controlling laptop and is accessible from phone/browser. Host shutdown differs from client disconnection. Sources: code-layer:nov07-remote.
Worktree timing allows task-specific branches/worktrees or direct checkout use. Multi-repo tasks create a worktree per repository. No two-change collision fixture was run. The daemon gives agents the file/network access of its OS user. Worktrees separate code and do not prove hostile-code containment.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No container/VM/OS containment option or process/secret isolation was established; documented worktrees do not provide security containment.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Checkout [partial] Worktree timing allows task-specific branches/worktrees or direct checkout use. Multi-repo tasks create a worktree per repository. No two-change collision fixture was run. Sources: code-layer:nov07-workspaces, code-layer:nov07-workspace-model.
Branch [partial] Worktree timing allows task-specific branches/worktrees or direct checkout use. Multi-repo tasks create a worktree per repository. No two-change collision fixture was run. Sources: code-layer:nov07-workspaces, code-layer:nov07-workspace-model.
Worktree [partial] Worktree timing allows task-specific branches/worktrees or direct checkout use. Multi-repo tasks create a worktree per repository. No two-change collision fixture was run. Sources: code-layer:nov07-workspaces, code-layer:nov07-workspace-model.
Container [partial] The docs explain running the daemon in a user-managed container, including persistent credentials and disabling in-app updates. They do not establish container containment as a product isolation boundary or creation of a container per session. Sources: code-layer:src2-cl-container-host.
Vm [partial] A daemon host may be a cloud VM, including disposable or suspended VMs. This is a user-provisioned host, not a VM or microVM the product creates per session. Sources: code-layer:src2-cl-container-host.
Os sandbox [unknown] Not established for os sandbox in the November 7 first-party source pass. No container/VM/OS containment option or process/secret isolation was established; documented worktrees do not provide security containment.
Filesystem [partial] The daemon gives agents the file/network access of its OS user. Worktrees separate code and do not prove hostile-code containment. Sources: code-layer:nov07-remote.
Process [unknown] Not established for process in the November 7 first-party source pass. No container/VM/OS containment option or process/secret isolation was established; documented worktrees do not provide security containment.
Network [partial] The daemon gives agents the file/network access of its OS user. Worktrees separate code and do not prove hostile-code containment. Sources: code-layer:nov07-remote.
Secrets [partial] No secret boundary: default copyGlobs copy .env files into worktrees, agents get the daemon user's access and saved session files are credentials. Sources: code-layer:b09-wsconfig, code-layer:b09-rd.
Code separation [partial] Worktree timing allows task-specific branches/worktrees or direct checkout use. Multi-repo tasks create a worktree per repository. No two-change collision fixture was run. Sources: code-layer:nov07-workspaces, code-layer:nov07-workspace-model.
Security boundary [partial] The daemon gives agents the file/network access of its OS user. Worktrees separate code and do not prove hostile-code containment. Sources: code-layer:nov07-remote.
Remote-host sessions and task files are accessible across clients; exact reload/recovery behavior was not tested. After about two minutes of lost host response running/approval sessions fail; a new message is possible when the host returns. Persisted host ID/auth and Claude history are required for a suspended host.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No crash/restart/replacement or multi-day recovery fixture was run; documented prerequisites do not prove lossless recovery.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
12 atomic answers
Client disconnect [partial] Remote-host sessions and task files are accessible across clients; exact reload/recovery behavior was not tested. Sources: code-layer:nov07-remote, code-layer:nov07-tasks.
Worker crash [partial] After about two minutes of lost host response running/approval sessions fail; a new message is possible when the host returns. Persisted host ID/auth and Claude history are required for a suspended host. Sources: code-layer:nov07-remote.
Service restart [partial] After about two minutes of lost host response running/approval sessions fail; a new message is possible when the host returns. Persisted host ID/auth and Claude history are required for a suspended host. Sources: code-layer:nov07-remote.
Expiry [supported] A waiting session continues after any length of host suspend. Sources: code-layer:b09-rd.
Transcript reload [partial] Remote-host sessions and task files are accessible across clients; exact reload/recovery behavior was not tested. Sources: code-layer:nov07-remote, code-layer:nov07-tasks.
Process reconnect [partial] Sessions bind to a host ID; a host that lost it registers as new and does not pick up old sessions. Sources: code-layer:b09-rd.
Task resume [partial] After about two minutes of lost host response running/approval sessions fail; a new message is possible when the host returns. Persisted host ID/auth and Claude history are required for a suspended host. Sources: code-layer:nov07-remote.
State reconstruction [partial] Persist credentials, host_id and ~/.claude to resume sessions on a new pod. Sources: code-layer:b09-rd.
Context loss [partial] Recreated containers lose credentials unless storage is mounted; Claude resume needs the host's ~/.claude. Sources: code-layer:b09-rd.
Duplicate actions [unknown] Not established for duplicate actions in the November 7 first-party source pass. No crash/restart/replacement or multi-day recovery fixture was run; documented prerequisites do not prove lossless recovery.
Manual repair [partial] After about two minutes of lost host response running/approval sessions fail; a new message is possible when the host returns. Persisted host ID/auth and Claude history are required for a suspended host. Sources: code-layer:nov07-remote.
Multi day continuity [supported] Task history and files continue across agents and workstations. Sources: code-layer:b09-tasks.
Workspace configuration supplies setup commands and copied local files per repo; remote hosts need checkout, tools and provider credentials. User setup remains required. The current CLI launch reference exposes materialization errors and explicit retries. Some copy/setup errors do not block launching, so automatic repair is not established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No clean remote-host service/caching/port collision fixture was run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
10 atomic answers
Dependencies [partial] Workspace configuration supplies setup commands and copied local files per repo; remote hosts need checkout, tools and provider credentials. User setup remains required. Sources: code-layer:nov07-workspaces, code-layer:nov07-remote-setup.
Caches [unknown] Not established for caches in the November 7 first-party source pass. No clean remote-host service/caching/port collision fixture was run.
Snapshots [unknown] Not established for snapshots in the November 7 first-party source pass. No clean remote-host service/caching/port collision fixture was run.
Services [unknown] Not established for services in the November 7 first-party source pass. No clean remote-host service/caching/port collision fixture was run.
Ports [unknown] Not established for ports in the November 7 first-party source pass. No clean remote-host service/caching/port collision fixture was run.
Secrets [partial] Workspace configuration supplies setup commands and copied local files per repo; remote hosts need checkout, tools and provider credentials. User setup remains required. Sources: code-layer:nov07-workspaces, code-layer:nov07-remote-setup.
Duplicate installs [partial] --no-self-update keeps an image-pinned CLI version; no shared dependency cache is documented. Sources: code-layer:b09-rd-guide.
Collisions [unknown] Not established for collisions in the November 7 first-party source pass. No clean remote-host service/caching/port collision fixture was run.
Remote setup [partial] Workspace configuration supplies setup commands and copied local files per repo; remote hosts need checkout, tools and provider credentials. User setup remains required. Sources: code-layer:nov07-workspaces, code-layer:nov07-remote-setup.
Automatic repair [partial] The current CLI launch reference exposes materialization errors and explicit retries. Some copy/setup errors do not block launching, so automatic repair is not established. Sources: code-layer:nov07-launch-task.
Release notes document Claude usage-limit warnings, waiting states and resumption after reset. Other safe-budget and controlled-failure behavior was not tested.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No bounded spend, time, turn, timeout or controlled provider failure fixture was run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
8 atomic answers
Time limits [partial] Automation daemons stop two minutes after last activity by default (--inactivity). Sources: code-layer:b09-automation.
Turn limits [partial] CodeLayer subagents nest at most three levels; no turn limit is documented. Sources: code-layer:b09-rn-subagents.
Token limits [partial] Release notes document Claude usage-limit warnings, waiting states and resumption after reset. Other safe-budget and controlled-failure behavior was not tested. Sources: code-layer:nov07-releases.
Spend limits [unknown] Not established for spend limits in the November 7 first-party source pass. No bounded spend, time, turn, timeout or controlled provider failure fixture was run.
Timeouts [partial] A daemon silent for about two minutes marks running or approval-waiting sessions failed. Sources: code-layer:b09-rd.
Retries [unknown] Not established for retries in the November 7 first-party source pass. No bounded spend, time, turn, timeout or controlled provider failure fixture was run.
Provider failures [partial] Release notes document Claude usage-limit warnings, waiting states and resumption after reset. Other safe-budget and controlled-failure behavior was not tested. Sources: code-layer:nov07-releases.
Enforcement [unknown] Not established for enforcement in the November 7 first-party source pass. No bounded spend, time, turn, timeout or controlled provider failure fixture was run.
The status reference documents approval, provider-limit and failed/lost states, and daemon supervisor logs. Advanced Metrics ranks tasks by token spend or cost and splits usage by agent, model, stage, person and mode; metric exports remain unestablished. No induced-fault or performance test was run.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No induced failure/reconnect/status-consistency or UI timing measurement was performed.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Logs [partial] The status reference names approval, provider-limit and failed/lost states; daemon service logs can be inspected with the documented supervisor. Truthfulness under induced faults was not tested. Sources: code-layer:nov07-list-tasks, code-layer:nov07-remote-setup.
Traces [unknown] Not established for traces in the November 7 first-party source pass. No induced failure/reconnect/status-consistency or UI timing measurement was performed.
Failure reasons [partial] The status reference names approval, provider-limit and failed/lost states; daemon service logs can be inspected with the documented supervisor. Truthfulness under induced faults was not tested. Sources: code-layer:nov07-list-tasks, code-layer:nov07-remote-setup.
Usage export [unknown] Not established for usage export in the November 7 first-party source pass. Release notes describe Advanced Metrics for usage, cost and productivity without naming exports or task, agent or project dimensions.
Task stats [supported] Advanced Metrics ranks every task by token spend or cost. Sources: code-layer:b09-rn-metrics.
Agent stats [partial] Advanced Metrics splits usage by agent, model, stage, person or mode. Sources: code-layer:b09-rn-metrics.
Project stats [unknown] Not established for project stats in the November 7 first-party source pass. Release notes describe Advanced Metrics for usage, cost and productivity without naming exports or task, agent or project dimensions.
Time stats [unknown] Not established for time stats in the November 7 first-party source pass. No induced failure/reconnect/status-consistency or UI timing measurement was performed.
Failure status [partial] The status reference names approval, provider-limit and failed/lost states; daemon service logs can be inspected with the documented supervisor. Truthfulness under induced faults was not tested. Sources: code-layer:nov07-list-tasks, code-layer:nov07-remote-setup.
Approval status [partial] The status reference names approval, provider-limit and failed/lost states; daemon service logs can be inspected with the documented supervisor. Truthfulness under induced faults was not tested. Sources: code-layer:nov07-list-tasks, code-layer:nov07-remote-setup.
Reconnect consistency [unknown] Not established for reconnect consistency in the November 7 first-party source pass. No induced failure/reconnect/status-consistency or UI timing measurement was performed.
Performance method [unknown] Not established for performance method in the November 7 first-party source pass. No induced failure/reconnect/status-consistency or UI timing measurement was performed.
Responsiveness [partial] Vendor-reported: daemon startup on a large org fell from about 4 s to 0.5 s; not measured here. Sources: code-layer:b09-rn-metrics.
Advanced Metrics ranks every task by token spend or cost with six splits including agent and model; per-host Claude limit alerts exist. Provider-billed versus estimated charges and child/epic aggregation are not established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
14 atomic answers
Task cost [supported] Every task is ranked by token spend or cost. Sources: code-layer:b09-rn-metrics.
Session cost [partial] Release notes mention usage/cost metrics and per-host Claude limit alerts; provider-billed versus estimated charges and task/child/epic aggregation are not established. Sources: code-layer:nov07-releases.
Child cost [unknown] Not established for child cost in the November 7 first-party source pass. Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Epic cost [unknown] Not established for epic cost in the November 7 first-party source pass. Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Harness aggregation [partial] Spend can be split by agent and model. Sources: code-layer:b09-rn-metrics.
Billed vs estimated [unknown] Not established for billed vs estimated in the November 7 first-party source pass. Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Tokens [supported] Token spend per task and complete per-session, per-model token counts. Sources: code-layer:b09-rn-metrics.
Subscription allowance [partial] Release notes mention usage/cost metrics and per-host Claude limit alerts; provider-billed versus estimated charges and task/child/epic aggregation are not established. Sources: code-layer:nov07-releases.
Provider reconciliation [unknown] Not established for provider reconciliation in the November 7 first-party source pass. Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Compute cost [unknown] Not established for compute cost in the November 7 first-party source pass. Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Refresh delay [unknown] Not established for refresh delay in the November 7 first-party source pass. Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Alerts [partial] Release notes mention usage/cost metrics and per-host Claude limit alerts; provider-billed versus estimated charges and task/child/epic aggregation are not established. Sources: code-layer:nov07-releases.
Export [unknown] Not established for export in the November 7 first-party source pass. Per-task/child/epic billing reconciliation, exports and refresh delays were not established.
Drilldown [supported] Each task bar splits six ways, including agent, model, stage, person and mode. Sources: code-layer:b09-rn-metrics.
External automation workflows can configure concurrency/no-op guards. These are user-owned CI controls, not a verified shared ADE scheduling policy. An opt-in host-load view shows CPU, memory, load and disk. This does not prove resource-aware dispatch or backpressure.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
12 atomic answers
Concurrency [partial] External automation workflows can configure concurrency/no-op guards. These are user-owned CI controls, not a verified shared ADE scheduling policy. Sources: code-layer:nov07-automation.
Queues [partial] External automation workflows can configure concurrency/no-op guards. These are user-owned CI controls, not a verified shared ADE scheduling policy. Sources: code-layer:nov07-automation.
Cpu ram [partial] An opt-in host-load view shows CPU, memory, load and disk. This does not prove resource-aware dispatch or backpressure. Sources: code-layer:nov07-releases.
Backpressure [unknown] Not established for backpressure in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Host awareness [partial] An opt-in host-load view shows CPU, memory, load and disk. This does not prove resource-aware dispatch or backpressure. Sources: code-layer:nov07-releases.
Check reuse [unknown] Not established for check reuse in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Check deduplication [unknown] Not established for check deduplication in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Bounded tests [unknown] Not established for bounded tests in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Cancellation [unknown] Not established for cancellation in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Fairness [unknown] Not established for fairness in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Recovery [unknown] Not established for recovery in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Shared limits [unknown] Not established for shared limits in the November 7 first-party source pass. No resource-bounded browser test queue was run; host-load display is not enforced scheduling.
Task sharing gives editors session/file access and reviewers document comments. No two-account permission fixture was run. Release notes describe live shared drafts with named cursors/presence and authors on queued messages; the October beta UI includes multiplayer prompting. Input conflicts were not tested. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Two-account ordering/conflict handling and owner-disconnect behavior were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Unestablished atomic questions: conflicts.
11 atomic answers
Visibility [partial] Task sharing gives editors session/file access and reviewers document comments. No two-account permission fixture was run. Sources: code-layer:nov07-tasks.
Discussion [supported] Comments stay on synced task documents and later agents read them. Sources: code-layer:b09-tasks.
Comments [partial] Task sharing gives editors session/file access and reviewers document comments. No two-account permission fixture was run. Sources: code-layer:nov07-tasks.
Presence [partial] Release notes describe live shared drafts with named cursors/presence and authors on queued messages; the October beta UI includes multiplayer prompting. Input conflicts were not tested. Sources: code-layer:nov07-releases.
Coprompting [partial] Release notes describe live shared drafts with named cursors/presence and authors on queued messages; the October beta UI includes multiplayer prompting. Input conflicts were not tested. Sources: code-layer:nov07-releases.
Ordering [partial] In shared sessions the agent knows who wrote each queued message. Sources: code-layer:b09-rn-collab.
Conflicts [unknown] Not established for conflicts in the November 7 first-party source pass. Two-account ordering/conflict handling and owner-disconnect behavior were not tested.
Attribution [partial] Release notes describe live shared drafts with named cursors/presence and authors on queued messages; the October beta UI includes multiplayer prompting. Input conflicts were not tested. Sources: code-layer:nov07-releases.
Permissions [partial] Task sharing gives editors session/file access and reviewers document comments. No two-account permission fixture was run. Sources: code-layer:nov07-tasks.
Plan restrictions [supported] Starter advertises the Pro capabilities for up to three team members and 200 sessions/month. Hosted transition terms constrain future use. Sources: code-layer:nov07-pricing.
Owner online [partial] The host daemon must be online for queued work to run. Sources: code-layer:b09-local.
Official integration guides reserve connection setup to organization admins; task-level edit and review access are documented. Full role matrix and revocation enforcement were not tested. Editors can add sessions and change task files; reviewers can comment on documents. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No unauthorized-access or revocation fixture was run; organization/project roles and provisioning details remain incomplete.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Organization roles [partial] Official integration guides reserve connection setup to organization admins; task-level edit and review access are documented. Full role matrix and revocation enforcement were not tested. Sources: code-layer:nov07-github, code-layer:nov07-tasks.
Task roles [supported] Editors can add sessions and change task files; reviewers can comment on documents. Sources: code-layer:nov07-tasks.
Membership [partial] Official integration guides reserve connection setup to organization admins; task-level edit and review access are documented. Full role matrix and revocation enforcement were not tested. Sources: code-layer:nov07-github, code-layer:nov07-tasks.
Sso [partial] SSO/SAML is listed on the custom Enterprise tier. Configuration and enforcement were not observed. Sources: code-layer:nov07-pricing.
Provisioning [unknown] Not established for provisioning in the November 7 first-party source pass. No unauthorized-access or revocation fixture was run; organization/project roles and provisioning details remain incomplete.
Unauthorized access [unknown] Not established for unauthorized access in the November 7 first-party source pass. No unauthorized-access or revocation fixture was run; organization/project roles and provisioning details remain incomplete.
Revocation [unknown] Not established for revocation in the November 7 first-party source pass. No unauthorized-access or revocation fixture was run; organization/project roles and provisioning details remain incomplete.
Plan scope [partial] SSO/SAML is listed on the custom Enterprise tier. Configuration and enforcement were not observed. Sources: code-layer:nov07-pricing.
The product launch reference lists default, accept_edits, auto and bypass permission modes. Automation runs explicitly bypass prompts. Safe allow/deny/revoke behavior was not tested.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No allow/deny/revoke/temporary-access fixture was run; documented permission modes do not prove enforcement.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Command [unknown] Not established for command in the November 7 first-party source pass. No allow/deny/revoke/temporary-access fixture was run; documented permission modes do not prove enforcement.
Network [unknown] Not established for network in the November 7 first-party source pass. No allow/deny/revoke/temporary-access fixture was run; documented permission modes do not prove enforcement.
Secret [partial] Personal access tokens show once and belong in a secret store. Sources: code-layer:b09-automation.
Delivery [partial] /rpi:describe-pr asks before resolving merge conflicts. Sources: code-layer:b09-rn-orch.
Approver identity [partial] Shared-session teammates can resolve approvals and each message shows its sender. Sources: code-layer:b09-rn-collab.
Allow [unknown] Not established for allow in the November 7 first-party source pass. No allow/deny/revoke/temporary-access fixture was run; documented permission modes do not prove enforcement.
Deny [unknown] Not established for deny in the November 7 first-party source pass. No allow/deny/revoke/temporary-access fixture was run; documented permission modes do not prove enforcement.
Tunnels [unknown] Not established for tunnels in the November 7 first-party source pass. No allow/deny/revoke/temporary-access fixture was run; documented permission modes do not prove enforcement.
Defaults [partial] The product launch reference lists default, accept_edits, auto and bypass permission modes. Automation runs explicitly bypass prompts. Safe allow/deny/revoke behavior was not tested. Sources: code-layer:nov07-launch-session, code-layer:nov07-automation.
Safer modes [partial] The product launch reference lists default, accept_edits, auto and bypass permission modes. Automation runs explicitly bypass prompts. Safe allow/deny/revoke behavior was not tested. Sources: code-layer:nov07-launch-session, code-layer:nov07-automation.
Enforcement [unknown] Not established for enforcement in the November 7 first-party source pass. No allow/deny/revoke/temporary-access fixture was run; documented permission modes do not prove enforcement.
Shared task files/comments remain with related sessions and can be read by later agents. Audit retention and tamper resistance are not established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Approval integrity, export, mutability and retention of an audit history were not established.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Actions [unknown] Not established for actions in the November 7 first-party source pass. Approval integrity, export, mutability and retention of an audit history were not established.
Discussion [partial] Shared task files/comments remain with related sessions and can be read by later agents. Audit retention and tamper resistance are not established. Sources: code-layer:nov07-tasks.
Cross user persistence [partial] Shared task files/comments remain with related sessions and can be read by later agents. Audit retention and tamper resistance are not established. Sources: code-layer:nov07-tasks.
Cross session persistence [partial] Shared task files/comments remain with related sessions and can be read by later agents. Audit retention and tamper resistance are not established. Sources: code-layer:nov07-tasks.
Export [partial] Beta data stays readable and the HumanLayer team helps with export on request; no self-serve export. Sources: code-layer:b09-beta.
Mutability [unknown] Not established for mutability in the November 7 first-party source pass. Approval integrity, export, mutability and retention of an audit history were not established.
Retention [unknown] Not established for retention in the November 7 first-party source pass. Approval integrity, export, mutability and retention of an audit history were not established.
Integrity [unknown] Not established for integrity in the November 7 first-party source pass. Approval integrity, export, mutability and retention of an audit history were not established.
Documented diff review includes changed-file navigation, comments and viewed markers, with artifact comments retained across UI reloads. Review effort, narrow screens and missed-evidence rates were not measured.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No shared review fixture, timing, keyboard/narrow-screen comparison or missed-evidence count was measured.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Pending reviews [partial] The notification bell lists sessions waiting on you. Sources: code-layer:b09-rn-tasks.
Change understanding [partial] Documented diff review includes changed-file navigation, comments and viewed markers, with artifact comments retained across UI reloads. Review effort, narrow screens and missed-evidence rates were not measured. Sources: code-layer:nov07-releases.
Evidence navigation [partial] Documented diff review includes changed-file navigation, comments and viewed markers, with artifact comments retained across UI reloads. Review effort, narrow screens and missed-evidence rates were not measured. Sources: code-layer:nov07-releases.
Comments [partial] Documented diff review includes changed-file navigation, comments and viewed markers, with artifact comments retained across UI reloads. Review effort, narrow screens and missed-evidence rates were not measured. Sources: code-layer:nov07-releases.
Request changes [partial] Feedback goes through artifact comments and /rpi:iterate-* skills. Sources: code-layer:b09-wf-guide.
Shipping guidance [partial] /rpi:describe-pr writes the PR description and an optional walkthrough for large changes. Sources: code-layer:b09-wf-ref.
Effort [unknown] Not established for effort in the November 7 first-party source pass. No shared review fixture, timing, keyboard/narrow-screen comparison or missed-evidence count was measured.
Missed evidence [unknown] Not established for missed evidence in the November 7 first-party source pass. No shared review fixture, timing, keyboard/narrow-screen comparison or missed-evidence count was measured.
Keyboard [partial] Documented diff review includes changed-file navigation, comments and viewed markers, with artifact comments retained across UI reloads. Review effort, narrow screens and missed-evidence rates were not measured. Sources: code-layer:nov07-releases.
Context switching [unknown] Not established for context switching in the November 7 first-party source pass. No shared review fixture, timing, keyboard/narrow-screen comparison or missed-evidence count was measured.
Roles [partial] Public review links give guests view or comment access. Sources: code-layer:b09-rn-collab.
Retained context [partial] Documented diff review includes changed-file navigation, comments and viewed markers, with artifact comments retained across UI reloads. Review effort, narrow screens and missed-evidence rates were not measured. Sources: code-layer:nov07-releases.
Shared task access allows another editor to add sessions and continue task files/history. Ongoing process/ownership transfer after owner disconnect was not tested. Claude/Codex handoff continues on the same task/worktree with transcript per release notes. This is separate from verified human takeover.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No second-person live runtime takeover or ownership transfer fixture was run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
12 atomic answers
Ongoing takeover [partial] Share a running session for a set time or transfer the task to another member. Sources: code-layer:b09-rn-collab.
Same task [partial] Shared task access allows another editor to add sessions and continue task files/history. Ongoing process/ownership transfer after owner disconnect was not tested. Sources: code-layer:nov07-tasks.
Session history [partial] Shared task access allows another editor to add sessions and continue task files/history. Ongoing process/ownership transfer after owner disconnect was not tested. Sources: code-layer:nov07-tasks.
Decisions [supported] The workflow writes current decisions into the artifact before switching sessions. Sources: code-layer:b09-wf-guide.
Artifacts [partial] Shared task access allows another editor to add sessions and continue task files/history. Ongoing process/ownership transfer after owner disconnect was not tested. Sources: code-layer:nov07-tasks.
Permissions [partial] Shared task access allows another editor to add sessions and continue task files/history. Ongoing process/ownership transfer after owner disconnect was not tested. Sources: code-layer:nov07-tasks.
Runtime context [partial] /hl:teleport moves a task to another machine and starts a new session there. Sources: code-layer:b09-rn-orch.
Ownership [supported] Task ownership can be transferred to another member. Sources: code-layer:b09-rn-collab.
Attribution [supported] Shared-session messages show their sender. Sources: code-layer:b09-rn-collab.
Context loss [partial] Claude resume needs the host's ~/.claude; Codex history is stored by HumanLayer. Sources: code-layer:b09-rd.
Harness transfer [partial] Claude/Codex handoff continues on the same task/worktree with transcript per release notes. This is separate from verified human takeover. Sources: code-layer:nov07-releases.
Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping. No cross-task gallery or exact-revision retrieval fixture was run. Workflow PR output can save a description and walkthrough. Retrieval of a full completed reviewer child was not tested.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Exact-revision artifact retrieval, recordings, full child reviewer retrieval and output prompt-leakage checks were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
13 atomic answers
Diffs [partial] Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping. No cross-task gallery or exact-revision retrieval fixture was run. Sources: code-layer:nov07-tasks.
Documents [partial] Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping. No cross-task gallery or exact-revision retrieval fixture was run. Sources: code-layer:nov07-tasks.
Screenshots [partial] Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping. No cross-task gallery or exact-revision retrieval fixture was run. Sources: code-layer:nov07-tasks.
Recordings [unknown] Not established for recordings in the November 7 first-party source pass. Exact-revision artifact retrieval, recordings, full child reviewer retrieval and output prompt-leakage checks were not tested.
Previews [partial] Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping. No cross-task gallery or exact-revision retrieval fixture was run. Sources: code-layer:nov07-tasks.
Test outputs [unknown] Not established for test outputs in the November 7 first-party source pass. Exact-revision artifact retrieval, recordings, full child reviewer retrieval and output prompt-leakage checks were not tested.
Reviewer outputs [partial] Workflow PR output can save a description and walkthrough. Retrieval of a full completed reviewer child was not tested. Sources: code-layer:nov07-skills.
Gallery [partial] The task artifact view lists synced files, including images, PDFs and HTML; no cross-task gallery. Sources: code-layer:b09-tasks.
Task links [partial] Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping. No cross-task gallery or exact-revision retrieval fixture was run. Sources: code-layer:nov07-tasks.
Revision links [partial] Artifact versions compare side by side with deep links to comment threads. Sources: code-layer:b09-rn-artifacts.
Persistence [partial] Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping. No cross-task gallery or exact-revision retrieval fixture was run. Sources: code-layer:nov07-tasks.
Child findings [unknown] Not established for child findings in the November 7 first-party source pass. Exact-revision artifact retrieval, recordings, full child reviewer retrieval and output prompt-leakage checks were not tested.
Prompt leakage [unknown] Not established for prompt leakage in the November 7 first-party source pass. Exact-revision artifact retrieval, recordings, full child reviewer retrieval and output prompt-leakage checks were not tested.
Guided implementation documents checks/manual review between phases; PR follow-up can respond to CI. These are workflow instructions, not verified enforced delivery gates. PR skills compare branch changes with the task plan. Persistent-spec conflict enforcement is not established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No failed-test/spec-conflict fixture or product-enforced delivery gate was demonstrated.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
11 atomic answers
Tests [partial] Guided implementation documents checks/manual review between phases; PR follow-up can respond to CI. These are workflow instructions, not verified enforced delivery gates. Sources: code-layer:nov07-skills, code-layer:nov07-releases.
Lint [partial] Guided implementation documents checks/manual review between phases; PR follow-up can respond to CI. These are workflow instructions, not verified enforced delivery gates. Sources: code-layer:nov07-skills, code-layer:nov07-releases.
Types [partial] Guided implementation documents checks/manual review between phases; PR follow-up can respond to CI. These are workflow instructions, not verified enforced delivery gates. Sources: code-layer:nov07-skills, code-layer:nov07-releases.
Ci [supported] /rpi:describe-pr watches PR checks and fixes failures caused by the PR. Sources: code-layer:b09-rn-orch.
Independent review [partial] Guided implementation documents checks/manual review between phases; PR follow-up can respond to CI. These are workflow instructions, not verified enforced delivery gates. Sources: code-layer:nov07-skills, code-layer:nov07-releases.
Spec checks [partial] PR skills compare branch changes with the task plan. Persistent-spec conflict enforcement is not established. Sources: code-layer:nov07-skills.
Required checks [unknown] Not established for required checks in the November 7 first-party source pass. No failed-test/spec-conflict fixture or product-enforced delivery gate was demonstrated.
Requirement conflicts [partial] PR skills compare branch changes with the task plan. Persistent-spec conflict enforcement is not established. Sources: code-layer:nov07-skills.
Configured policy [partial] Guided implementation documents checks/manual review between phases; PR follow-up can respond to CI. These are workflow instructions, not verified enforced delivery gates. Sources: code-layer:nov07-skills, code-layer:nov07-releases.
Enforced policy [unknown] Not established for enforced policy in the November 7 first-party source pass. No failed-test/spec-conflict fixture or product-enforced delivery gate was demonstrated.
Workspace setup creates task branches/worktrees; implementation skills commit checked phases. No fixture change was delivered. An opt-in GitHub PR tab exposes PR actions/review threads/checks, and PR skills create/update descriptions and follow up on checks.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No end-to-end draft PR, rebase or conflict-resolution fixture was run.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Branches [partial] Workspace setup creates task branches/worktrees; implementation skills commit checked phases. No fixture change was delivered. Sources: code-layer:nov07-workspaces, code-layer:nov07-skills.
Worktrees [partial] Workspace setup creates task branches/worktrees; implementation skills commit checked phases. No fixture change was delivered. Sources: code-layer:nov07-workspaces, code-layer:nov07-skills.
Commits [partial] Workspace setup creates task branches/worktrees; implementation skills commit checked phases. No fixture change was delivered. Sources: code-layer:nov07-workspaces, code-layer:nov07-skills.
Pull requests [partial] An opt-in GitHub PR tab exposes PR actions/review threads/checks, and PR skills create/update descriptions and follow up on checks. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Comments [partial] An opt-in GitHub PR tab exposes PR actions/review threads/checks, and PR skills create/update descriptions and follow up on checks. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Ci response [partial] An opt-in GitHub PR tab exposes PR actions/review threads/checks, and PR skills create/update descriptions and follow up on checks. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Rebase [unknown] Not established for rebase in the November 7 first-party source pass. No end-to-end draft PR, rebase or conflict-resolution fixture was run.
Conflicts [partial] /rpi:describe-pr asks for approval before resolving merge conflicts. Sources: code-layer:b09-rn-orch.
Product state [partial] An opt-in GitHub PR tab exposes PR actions/review threads/checks, and PR skills create/update descriptions and follow up on checks. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
The opt-in GitHub PR tab documents merge and auto-merge actions. Exact-revision authority enforcement, release and deployment were not tested.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Exact-revision approval authority, production deploy and release permissions were not verified.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
6 atomic answers
Approve [partial] The opt-in GitHub PR tab documents merge and auto-merge actions. Exact-revision authority enforcement, release and deployment were not tested. Sources: code-layer:nov07-releases.
Merge [partial] The opt-in GitHub PR tab documents merge and auto-merge actions. Exact-revision authority enforcement, release and deployment were not tested. Sources: code-layer:nov07-releases.
Release [unknown] Not established for release in the November 7 first-party source pass. Exact-revision approval authority, production deploy and release permissions were not verified.
Deploy [unknown] Not established for deploy in the November 7 first-party source pass. Exact-revision approval authority, production deploy and release permissions were not verified.
Exact revision [unknown] Not established for exact revision in the November 7 first-party source pass. Exact-revision approval authority, production deploy and release permissions were not verified.
Authority enforcement [unknown] Not established for authority enforcement in the November 7 first-party source pass. Exact-revision approval authority, production deploy and release permissions were not verified.
Release notes document session/PR links through a commit ledger; task artifacts retain PR descriptions. This does not establish delivery status or rollback.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Build/deployment links, reliable delivery state, rollback and stale-approval invalidation were not established.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
9 atomic answers
Commit links [partial] Release notes document session/PR links through a commit ledger; task artifacts retain PR descriptions. This does not establish delivery status or rollback. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Pr links [partial] Release notes document session/PR links through a commit ledger; task artifacts retain PR descriptions. This does not establish delivery status or rollback. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Build links [unknown] Not established for build links in the November 7 first-party source pass. Build/deployment links, reliable delivery state, rollback and stale-approval invalidation were not established.
Deployment links [unknown] Not established for deployment links in the November 7 first-party source pass. Build/deployment links, reliable delivery state, rollback and stale-approval invalidation were not established.
Delivery status [unknown] Not established for delivery status in the November 7 first-party source pass. Build/deployment links, reliable delivery state, rollback and stale-approval invalidation were not established.
Retained evidence [partial] Release notes document session/PR links through a commit ledger; task artifacts retain PR descriptions. This does not establish delivery status or rollback. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Rollback [unknown] Not established for rollback in the November 7 first-party source pass. Build/deployment links, reliable delivery state, rollback and stale-approval invalidation were not established.
Revert [unknown] Not established for revert in the November 7 first-party source pass. Build/deployment links, reliable delivery state, rollback and stale-approval invalidation were not established.
Stale approval invalidation [unknown] Not established for stale approval invalidation in the November 7 first-party source pass. Build/deployment links, reliable delivery state, rollback and stale-approval invalidation were not established.
Per-task diff/artifact comments, PR controls and workflow next actions exist. A six-task batch review queue, dependency ordering and stale-approval invalidation remain unverified.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
12 atomic answers
Review queue [unknown] Not established for review queue in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Summaries [unknown] Not established for summaries in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Grouping [unknown] Not established for grouping in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Risk size filters [unknown] Not established for risk size filters in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Findings [unknown] Not established for findings in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Artifacts [partial] Per-task diff/artifact comments, PR controls and workflow next actions exist. A six-task batch review queue, dependency ordering and stale-approval invalidation remain unverified. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Request changes [partial] Per-task diff/artifact comments, PR controls and workflow next actions exist. A six-task batch review queue, dependency ordering and stale-approval invalidation remain unverified. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Exact revision approval [unknown] Not established for exact revision approval in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Dependency queues [unknown] Not established for dependency queues in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Next actions [partial] Per-task diff/artifact comments, PR controls and workflow next actions exist. A six-task batch review queue, dependency ordering and stale-approval invalidation remain unverified. Sources: code-layer:nov07-releases, code-layer:nov07-skills.
Stale approval invalidation [unknown] Not established for stale approval invalidation in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
Check deduplication [unknown] Not established for check deduplication in the November 7 first-party source pass. The six-task batch review/merge queue fixture was not run; per-task PR actions do not establish a dependency-aware batch shipping queue.
The current application monorepo at the cited revision is Apache-2.0, with separately licensed vendored MIT folders. It includes desktop/web, daemon, API and sync proxy. The pinned README says HumanLayer Cloud runs this code. Independent production parity and any hosted-only operations were not audited.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-11
The named documentation/source pass did not resolve every atomic question; hands-on persistence and access boundaries were not tested.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
6 atomic answers
Client license [supported] The current application monorepo at the cited revision is Apache-2.0, with separately licensed vendored MIT folders. It includes desktop/web, daemon, API and sync proxy. Sources: code-layer:nov07-repo, code-layer:nov07-license.
Server license [supported] The current application monorepo at the cited revision is Apache-2.0, with separately licensed vendored MIT folders. It includes desktop/web, daemon, API and sync proxy. Sources: code-layer:nov07-repo, code-layer:nov07-license.
Hosted extensions [partial] The pinned README says HumanLayer Cloud runs this code. Independent production parity and any hosted-only operations were not audited. Sources: code-layer:nov07-repo.
Source visibility [supported] The current application monorepo at the cited revision is Apache-2.0, with separately licensed vendored MIT folders. It includes desktop/web, daemon, API and sync proxy. Sources: code-layer:nov07-repo, code-layer:nov07-license.
Source revision [supported] The current application monorepo at the cited revision is Apache-2.0, with separately licensed vendored MIT folders. It includes desktop/web, daemon, API and sync proxy. Sources: code-layer:nov07-repo, code-layer:nov07-license.
Hosted parity [partial] The pinned README says HumanLayer Cloud runs this code. Independent production parity and any hosted-only operations were not audited. Sources: code-layer:nov07-repo.
Current core is open source and can be built and run; 0.202.0 adds a reference self-host copy that HumanLayer calls unsupported, with WorkOS login required. The Factory transition notice offers data-export, migration or self-hosting support and refunds; an actual full history export/import was not tested.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
A complete export/import, formats, account-independent deployment and history portability were not exercised.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Unestablished atomic questions: import.
8 atomic answers
Self hosting [partial] Current core can be built/run locally, but setup requires third-party configuration and self-hosting guides are unfinished. The older SDK is not the basis for this finding. Sources: code-layer:nov07-repo, code-layer:nov07-open-core.
Vendor dependencies [partial] Current core can be built/run locally, but setup requires third-party configuration and self-hosting guides are unfinished. The older SDK is not the basis for this finding. Sources: code-layer:nov07-repo, code-layer:nov07-open-core.
Export [partial] The Factory transition notice offers data-export, migration or self-hosting support and refunds; an actual full history export/import was not tested. Sources: code-layer:factory-transition-20261104.
Import [unknown] Not established for import in the November 7 first-party source pass. A complete export/import, formats, account-independent deployment and history portability were not exercised.
Formats [partial] Task files sync as Markdown, text and JSON(L) text artifacts; images, PDFs and HTML go through object storage. Sources: code-layer:b09-tasks.
Cancellation [partial] The Factory transition notice offers data-export, migration or self-hosting support and refunds; an actual full history export/import was not tested. Sources: code-layer:factory-transition-20261104.
History portability [partial] The Factory transition notice offers data-export, migration or self-hosting support and refunds; an actual full history export/import was not tested. Sources: code-layer:factory-transition-20261104.
Agents execute on user hosts while events/task artifacts sync through HumanLayer APIs/storage; model traffic can use configured provider gateways. Retention, residency and training policies were not audited. Saved daemon login includes a refresh token; host credentials/history volumes require persistence and limited access. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Hosted retention/deletion/training/residency/subprocessor policies and first-run consent were not checked.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
15 atomic answers
Code data [partial] Agents execute on user hosts while events/task artifacts sync through HumanLayer APIs/storage; model traffic can use configured provider gateways. Retention, residency and training policies were not audited. Sources: code-layer:nov07-remote, code-layer:nov07-tasks, code-layer:nov07-gateway.
Prompts [partial] Agents execute on user hosts while events/task artifacts sync through HumanLayer APIs/storage; model traffic can use configured provider gateways. Retention, residency and training policies were not audited. Sources: code-layer:nov07-remote, code-layer:nov07-tasks, code-layer:nov07-gateway.
Credentials [supported] Saved daemon login includes a refresh token; host credentials/history volumes require persistence and limited access. Sources: code-layer:nov07-remote.
Logs [partial] Agents execute on user hosts while events/task artifacts sync through HumanLayer APIs/storage; model traffic can use configured provider gateways. Retention, residency and training policies were not audited. Sources: code-layer:nov07-remote, code-layer:nov07-tasks, code-layer:nov07-gateway.
Artifacts [partial] Agents execute on user hosts while events/task artifacts sync through HumanLayer APIs/storage; model traffic can use configured provider gateways. Retention, residency and training policies were not audited. Sources: code-layer:nov07-remote, code-layer:nov07-tasks, code-layer:nov07-gateway.
Retention [unknown] Not established for retention in the November 7 first-party source pass. Hosted retention/deletion/training/residency/subprocessor policies and first-run consent were not checked.
Deletion [unknown] Not established for deletion in the November 7 first-party source pass. Hosted retention/deletion/training/residency/subprocessor policies and first-run consent were not checked.
Training [unknown] Not established for training in the November 7 first-party source pass. Hosted retention/deletion/training/residency/subprocessor policies and first-run consent were not checked.
Residency [unknown] Not established for residency in the November 7 first-party source pass. Hosted retention/deletion/training/residency/subprocessor policies and first-run consent were not checked.
Subprocessors [unknown] Not established for subprocessors in the November 7 first-party source pass. Hosted retention/deletion/training/residency/subprocessor policies and first-run consent were not checked.
Telemetry disclosure [partial] For builds from the current source, Sentry/PostHog are disabled unless environment keys are set. This establishes self-build controls, not hosted-app defaults or observed first-run consent. Sources: code-layer:nov07-repo.
Telemetry defaults [partial] For builds from the current source, Sentry/PostHog are disabled unless environment keys are set. This establishes self-build controls, not hosted-app defaults or observed first-run consent. Sources: code-layer:nov07-repo.
Telemetry controls [partial] For builds from the current source, Sentry/PostHog are disabled unless environment keys are set. This establishes self-build controls, not hosted-app defaults or observed first-run consent. Sources: code-layer:nov07-repo.
Consent prompt [unknown] Not established for consent prompt in the November 7 first-party source pass. Hosted retention/deletion/training/residency/subprocessor policies and first-run consent were not checked.
Provider separation [partial] Agents execute on user hosts while events/task artifacts sync through HumanLayer APIs/storage; model traffic can use configured provider gateways. Retention, residency and training policies were not audited. Sources: code-layer:nov07-remote, code-layer:nov07-tasks, code-layer:nov07-gateway.
Public pricing lists Pro at USD 100/user/month with unlimited tasks/sessions and BYO agent subscriptions/API keys; Starter is free up to three members and 200 sessions/month. Provider/compute costs remain separate. Agents use user-provided local/remote compute; no universal compute bill is established.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
Seat minima, taxes, overages, credits and complete transition billing terms were not resolved.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
12 atomic answers
Currency [supported] Public pricing lists Pro at USD 100/user/month with unlimited tasks/sessions and BYO agent subscriptions/API keys; Starter is free up to three members and 200 sessions/month. Provider/compute costs remain separate. Sources: code-layer:nov07-pricing.
Interval [supported] Public pricing lists Pro at USD 100/user/month with unlimited tasks/sessions and BYO agent subscriptions/API keys; Starter is free up to three members and 200 sessions/month. Provider/compute costs remain separate. Sources: code-layer:nov07-pricing.
Seats [supported] Public pricing lists Pro at USD 100/user/month with unlimited tasks/sessions and BYO agent subscriptions/API keys; Starter is free up to three members and 200 sessions/month. Provider/compute costs remain separate. Sources: code-layer:nov07-pricing.
Seat minimum [unknown] Not established for seat minimum in the November 7 first-party source pass. Seat minima, taxes, overages, credits and complete transition billing terms were not resolved.
Workspace fees [unknown] Not established for workspace fees in the November 7 first-party source pass. Seat minima, taxes, overages, credits and complete transition billing terms were not resolved.
Included usage [supported] Public pricing lists Pro at USD 100/user/month with unlimited tasks/sessions and BYO agent subscriptions/API keys; Starter is free up to three members and 200 sessions/month. Provider/compute costs remain separate. Sources: code-layer:nov07-pricing.
Credits [unknown] Not established for credits in the November 7 first-party source pass. Seat minima, taxes, overages, credits and complete transition billing terms were not resolved.
Trial [unknown] Not established for trial in the November 7 first-party source pass. Seat minima, taxes, overages, credits and complete transition billing terms were not resolved.
Overages [unknown] Not established for overages in the November 7 first-party source pass. Seat minima, taxes, overages, credits and complete transition billing terms were not resolved.
Taxes [unknown] Not established for taxes in the November 7 first-party source pass. Seat minima, taxes, overages, credits and complete transition billing terms were not resolved.
Model cost [supported] Public pricing lists Pro at USD 100/user/month with unlimited tasks/sessions and BYO agent subscriptions/API keys; Starter is free up to three members and 200 sessions/month. Provider/compute costs remain separate. Sources: code-layer:nov07-pricing.
Compute cost [partial] Agents use user-provided local/remote compute; no universal compute bill is established. Sources: code-layer:nov07-remote.
One or two users can fit the advertised free Starter seat allowance if they remain within 200 sessions/month. Provider subscriptions, workload costs and compute remain unknown; this is not a priced measured workload.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
11 atomic answers
One person [partial] One or two users can fit the advertised free Starter seat allowance if they remain within 200 sessions/month. Provider subscriptions, workload costs and compute remain unknown; this is not a priced measured workload. Sources: code-layer:nov07-pricing.
Two people [partial] One or two users can fit the advertised free Starter seat allowance if they remain within 200 sessions/month. Provider subscriptions, workload costs and compute remain unknown; this is not a priced measured workload. Sources: code-layer:nov07-pricing.
Five people [unknown] Not established for five people in the November 7 first-party source pass. No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Task assumptions [unknown] Not established for task assumptions in the November 7 first-party source pass. No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Concurrency [unknown] Not established for concurrency in the November 7 first-party source pass. No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Tokens [unknown] Not established for tokens in the November 7 first-party source pass. No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Compute hours [unknown] Not established for compute hours in the November 7 first-party source pass. No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Fixed cost [partial] One or two users can fit the advertised free Starter seat allowance if they remain within 200 sessions/month. Provider subscriptions, workload costs and compute remain unknown; this is not a priced measured workload. Sources: code-layer:nov07-pricing.
Variable cost [unknown] Not established for variable cost in the November 7 first-party source pass. No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Included cost [unknown] Not established for included cost in the November 7 first-party source pass. No fixed workload, token count, concurrency or compute-hour fixture was priced for one, two and five users.
Unknown cost [partial] One or two users can fit the advertised free Starter seat allowance if they remain within 200 sessions/month. Provider subscriptions, workload costs and compute remain unknown; this is not a priced measured workload. Sources: code-layer:nov07-pricing.
Official notes reach 0.202.0 on November 14, 2026; production and beta environments both run. Release documentation is not a hands-on reliability result. The November 4 Factory notice sets at least 30 days of transition operation and offers export/migration/self-hosting support. No exact hosted end date is announced.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: docs.humanlayer.com (release notes through 0.202.0, 2026-11-14) and public repository at the 0.202.0 release merge 8e1e3f1 (2026-11-14); release-note items keep their own release versions and earlier f9bd735 citations are retained. · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
No response SLA, status history or formal GA/beta availability guarantee was established.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
8 atomic answers
Release stage [partial] Production and beta environments both run; the minimalist UI is beta and on by default for new devices. Sources: code-layer:b09-beta, code-layer:b09-rn-stage.
Access restrictions [unknown] Not established for access restrictions in the November 7 first-party source pass. No response SLA, status history or formal GA/beta availability guarantee was established.
Support [unknown] Not established for support in the November 7 first-party source pass. No response SLA, status history or formal GA/beta availability guarantee was established.
Response commitments [unknown] Not established for response commitments in the November 7 first-party source pass. No response SLA, status history or formal GA/beta availability guarantee was established.
Release activity [supported] Official notes reach 0.201.0 on November 2, 2026. Release documentation is not a hands-on reliability result. Sources: code-layer:nov07-releases.
Status history [unknown] Not established for status history in the November 7 first-party source pass. No response SLA, status history or formal GA/beta availability guarantee was established.
Deprecation [supported] The November 4 Factory notice sets at least 30 days of transition operation and offers export/migration/self-hosting support. No exact hosted end date is announced. Sources: code-layer:factory-transition-20261104.
Export options [supported] The November 4 Factory notice sets at least 30 days of transition operation and offers export/migration/self-hosting support. No exact hosted end date is announced. Sources: code-layer:factory-transition-20261104.
The vendor homepage asserts SOC 2 Type II and Vanta monitoring. No report, audit period or independent scope verification was accessed in this November 7 pass.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
No ISO certificate or SOC report, service scope, issuer/period or validity record was accessed.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
9 atomic answers
Iso scope [unknown] Not established for iso scope in the November 7 first-party source pass. No ISO certificate or SOC report, service scope, issuer/period or validity record was accessed.
Iso issuer [unknown] Not established for iso issuer in the November 7 first-party source pass. No ISO certificate or SOC report, service scope, issuer/period or validity record was accessed.
Iso validity [unknown] Not established for iso validity in the November 7 first-party source pass. No ISO certificate or SOC report, service scope, issuer/period or validity record was accessed.
Soc2 type [partial] The vendor homepage asserts SOC 2 Type II and Vanta monitoring. No report, audit period or independent scope verification was accessed in this November 7 pass. Sources: code-layer:nov07-pricing.
Soc2 scope [unknown] Not established for soc2 scope in the November 7 first-party source pass. No ISO certificate or SOC report, service scope, issuer/period or validity record was accessed.
Soc2 period [unknown] Not established for soc2 period in the November 7 first-party source pass. No ISO certificate or SOC report, service scope, issuer/period or validity record was accessed.
Report access [partial] The vendor homepage asserts SOC 2 Type II and Vanta monitoring. No report, audit period or independent scope verification was accessed in this November 7 pass. Sources: code-layer:nov07-pricing.
Verification date [partial] The vendor homepage asserts SOC 2 Type II and Vanta monitoring. No report, audit period or independent scope verification was accessed in this November 7 pass. Sources: code-layer:nov07-pricing.
Evidence status [partial] The vendor homepage asserts SOC 2 Type II and Vanta monitoring. No report, audit period or independent scope verification was accessed in this November 7 pass. Sources: code-layer:nov07-pricing.
Starter is an ongoing free plan for up to three members and 200 sessions/month, currently offered during the announced transition. The homepage includes Pro capabilities; model and host costs remain separate. Apache-2.0 self-builds have no application licence charge; compute, model and third-party service costs remain. Self-hosting setup was not executed.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
Card requirement, trial conditions and every free shared scenario were not verified.
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
10 atomic answers
Ongoing free [supported] Starter is an ongoing free plan for up to three members and 200 sessions/month, currently offered during the announced transition. The homepage includes Pro capabilities; model and host costs remain separate. Sources: code-layer:nov07-pricing.
Trial [unknown] Not established for trial in the November 7 first-party source pass. Card requirement, trial conditions and every free shared scenario were not verified.
Credits trial [unknown] Not established for credits trial in the November 7 first-party source pass. Card requirement, trial conditions and every free shared scenario were not verified.
Self host cost [partial] Apache-2.0 self-builds have no application licence charge; compute, model and third-party service costs remain. Self-hosting setup was not executed. Sources: code-layer:nov07-repo, code-layer:nov07-license.
Paid only [unknown] Not established for paid only in the November 7 first-party source pass. Card requirement, trial conditions and every free shared scenario were not verified.
Early access [unknown] Not established for early access in the November 7 first-party source pass. Card requirement, trial conditions and every free shared scenario were not verified.
Free scenarios [supported] Starter is an ongoing free plan for up to three members and 200 sessions/month, currently offered during the announced transition. The homepage includes Pro capabilities; model and host costs remain separate. Sources: code-layer:nov07-pricing.
Card required [unknown] Not established for card required in the November 7 first-party source pass. Card requirement, trial conditions and every free shared scenario were not verified.
Usage caps [supported] Starter is an ongoing free plan for up to three members and 200 sessions/month, currently offered during the announced transition. The homepage includes Pro capabilities; model and host costs remain separate. Sources: code-layer:nov07-pricing.
Paid evaluation [unknown] Not established for paid evaluation in the November 7 first-party source pass. Card requirement, trial conditions and every free shared scenario were not verified.
Pricing is partially specified: per-user monthly Pro price and Starter caps are public; Enterprise is custom, while taxes, overages and minimum commitments are not resolved.
Scope
Surfaces: Current HumanLayer desktop and hosted UI, HumanLayer remote daemon · Version: HumanLayer official docs through 0.201.0 and current source f9bd73534a9fb7099a274f951b698b1297122fd9 checked 2026-11-07; no installed release tested · Plan: Hosted Starter/Pro/Enterprise remain subject to the Factory transition; self-build and integration scopes are stated per answer. · OS: Not specified · Execution modes: local, user-managed-remote · Region: Not specified · Harness: Not specified
Hosted platform is in the announced Factory transition. Open-source continuation is separate from hosted availability. No hands-on scenario was run.
9 atomic answers
Units [partial] Pricing is partially specified: per-user monthly Pro price and Starter caps are public; Enterprise is custom, while taxes, overages and minimum commitments are not resolved. Sources: code-layer:nov07-pricing.
Included limits [partial] Pricing is partially specified: per-user monthly Pro price and Starter caps are public; Enterprise is custom, while taxes, overages and minimum commitments are not resolved. Sources: code-layer:nov07-pricing.
Overages [unknown] Not established for overages in the November 7 first-party source pass. Cancellation terms, overage rates, minimum commitments and compute/model markups remain unresolved.
Compute markup [unknown] Not established for compute markup in the November 7 first-party source pass. Cancellation terms, overage rates, minimum commitments and compute/model markups remain unresolved.
Model markup [unknown] Not established for model markup in the November 7 first-party source pass. Cancellation terms, overage rates, minimum commitments and compute/model markups remain unresolved.
Minimum commitment [unknown] Not established for minimum commitment in the November 7 first-party source pass. Cancellation terms, overage rates, minimum commitments and compute/model markups remain unresolved.
Cancellation [unknown] Not established for cancellation in the November 7 first-party source pass. Cancellation terms, overage rates, minimum commitments and compute/model markups remain unresolved.
Sales only unknowns [partial] Pricing is partially specified: per-user monthly Pro price and Starter caps are public; Enterprise is custom, while taxes, overages and minimum commitments are not resolved. Sources: code-layer:nov07-pricing.
Transparency classification [partial] Pricing is partially specified: per-user monthly Pro price and Starter caps are public; Enterprise is custom, while taxes, overages and minimum commitments are not resolved. Sources: code-layer:nov07-pricing.
The tutorial uses the Apple-silicon macOS app, signed-in Claude Code, Git and an inline task. Oneshot can run directly in a checkout; other host operating systems use remote-daemon instructions. No setup timing was measured.
Kind
documented
Locator
Before you start; installation; task and session creation
Desktop and remote daemons run Claude/Codex on user-selected hosts. The phone/browser can start, watch and message sessions but lacks workspace configuration and embedded terminals. Long-running supervision and persisted host credentials/history are required; running sessions fail after roughly two minutes without a responding host.
Kind
documented
Locator
Hosts; authentication; disposable hosts; process lifecycle; browser limitations; security
automation run creates/reuses a task and runs one Cloud-visible session in a user-supplied CI/cron checkout. It uses a PAT and provider credentials, starts a job-local daemon with permission prompts bypassed, streams events and exits with session result. Scheduling, concurrency and no-op guards belong to the external workflow.
Kind
documented
Locator
How it works; tasks/sessions; personal access token; GitHub Actions
The pinned current application repository includes desktop/web, daemon, CLI and server components and supports Claude Code, Codex, OpenCode and Pi. It identifies Electron/Tauri macOS shells, a local devstack and telemetry controls through unset environment configuration.
The CLI proxies the product RPC contract except metrics and requires scoped filters for conversation-event sync. This supports product-owned API access, not a stability guarantee or an exposed MCP server.
Tasks group separately configured sessions and shared files. Editors add sessions and edit files; reviewers comment. Supported agent file tools sync text, HTML, images and PDFs into the artifact view, including across workstations. This is not a repository backup.
Kind
documented
Locator
Task/session distinction; share and review; task files
The HumanLayer CLI supports Codex browser/device authentication, configurable OpenAI Responses, Bedrock and Azure endpoints, model selection and reasoning effort. Endpoint credentials and model compatibility have explicit restrictions.
Documents user-configured model gateways/proxies; endpoint settings and daemon environment determine the provider route. This is distinct from a universal harness adapter or a verified local-model setup.
The closed coding-agent schema contains Claude aliases, CodeLayer/Fold, Pi, OpenCode and Codex. Only the declared launchable subset is offered by task launchers; absent values are rejected by daemon handlers. Other supported terminal agents can be mirrored. No Cursor, Gemini CLI, Grok, Aider or Antigravity type is present.
HumanLayer runs Claude Code, Codex, OpenCode and Pi; apps/riptide-claude-code-plugin, riptide-opencode-plugin and riptide-pi-extension are plugins that mirror those sessions into HumanLayer. No general adapter API is listed.
The closed coding-agent list is claude, opencode, codelayer, fold, pi, codex and claude-code; daemon launches accept claude, codelayer and fold. Cursor, Gemini CLI, Grok, Aider and Antigravity are absent.
Kind
source-inspected
Locator
CODING_AGENT_VALUES (line 4); LAUNCHABLE_CODING_AGENT_VALUES (line 23); unchanged since f9bd735
Starter advertises up to three members and 200 sessions/month. Pro is USD 100/user/month with BYO subscriptions/API keys; Enterprise lists SSO/SAML and a SOC 2 Type II assertion. The undated open-source FAQ is stale relative to the October 23 announcement; pricing is read in the November 4 transition context.
The vendor identifies the current desktop/web application, daemon/CLI, API and sync proxy as Apache-2.0 core matching Cloud. Self-hosting setup still requires third-party keys; future deployment guides remain plans. Self-build telemetry is disabled unless configured.
The daemon's Claude sign-in spawns the installed Claude Code CLI with `auth login` / `auth status`, so the CLI's own account login (including subscription sign-in) is used; the Codex driver separately runs ChatGPT device sign-in.
Claude sessions locate the user's installed claude executable (configured path or PATH) and pass it to the Agent SDK as pathToClaudeCodeExecutable, so sessions run on the local Claude Code install and its login.
Kind
source-inspected
Locator
apps/riptide-daemon/src/effects/services/claude-sessions/prepare-claude-session.ts lines 172-176 (locateClaudeExecutable; pathToClaudeCodeExecutable at line 384), commit f9bd735
Starter is free for teams of up to three members and 200 sessions/month; Pro is USD 100 per user per month; Enterprise is custom-priced and adds SSO/SAML, audit logs and on-prem/private VPC. FAQ: bring existing Claude/Codex subscriptions or API keys, no separate HumanLayer per-token bill. A free macOS (Apple silicon) download and Homebrew cask are offered.
The CLI installs on the user host. Interactive device login persists credentials; launch tokens authenticate one process. A documented systemd user service or another supervisor keeps the daemon alive. npm daemons can update from the app; Windows updates manually.
Kind
documented
Locator
Install; login or launch token; systemd; daemon updates
Organization admins connect repository-scoped GitHub Apps. Issue details/comments enter ticket.md, and artifact links update one source-issue comment. Failed link updates do not block saving an artifact.
CLI examples create the same task/workspace UUID and launch sessions, including tasks without external tickets. Repository materialization/errors are inspectable; copy/setup command errors need not block launch. Existing-folder execution is allowed explicitly.
CLI examples launch sessions under a task ID, configure host/agent/model and choose default, accept_edits, auto or bypass permissions. Another host uses the pushed task branch; unpushed work stays behind.
Shared and local JSON configure separate worktrees for each repository; setup commands and copied files apply per repository. Skills/instructions load across repositories, while MCP and Claude settings follow the launch directory.
Sessions wait for plugins to install and MCP servers to connect before the agent starts, so OAuth-authenticated MCP tools are available from the first turn.
Kind
documented
Locator
0.122.1 (2026-06-24) OAuth MCP tools ready from the first turn
The host can be any cloud VM, workstation or private machine the user selects. Credentials are lost when a container is recreated unless storage is mounted; treat saved session files as credentials. Sessions bind to a host ID in ~/.humanlayer/riptide/host_id; a host without it registers as new. To resume on a new pod persist credentials, host_id and ~/.claude (Codex history is stored by HumanLayer). A waiting session continues after any length of suspend; if the daemon is silent about two minutes while a session runs or waits for tool approval, the session is marked failed. The browser app at app.humanlayer.com works from a machine or phone but lacks workspace management, an embedded terminal and path auto-complete. Daemons give agents the running user's file and network access; stop the daemon to prevent new sessions.
Kind
documented
Locator
Daemon hosts; Containers; Disposable and suspended hosts; Process life cycle; Browser and native app capabilities; Security model (source apps/docs/explanation/remote-daemons.md at release 0.202.0)
The public repository's native app is a Tauri desktop shell; a bounded search found no iOS or Android project. Phones use the web and mobile UI at app.humanlayer.com.
Kind
source-inspected
Locator
apps/riptide-native (Tauri desktop shell: daemon.rs, pty.rs); repository-wide search for *.xcodeproj and AndroidManifest.xml found none
Linear OAuth imports issues and synchronizes named workflow states and artifact links. The separate Linear CLI can inspect/manage states and update issues; this is external issue management.
Organization admins authorize Jira Cloud. Tasks can start from accessible tickets; reconnect/disconnect and import toggles are documented. It does not establish complete two-way field synchronization.
humanlayer automation run starts an ephemeral daemon in a CI job or script with a personal access token and launches the agent with permission prompts bypassed. PATs get an expiration, are shown once and belong in a secret store. The daemon stays up until two minutes after the last activity by default (--inactivity 2m), or exits when the session is ready (--shutdown-on stop). GitHub Actions schedule or event triggers start runs. The guide suggests a repository markdown file as agent memory included in the prompt.
Kind
documented
Locator
How it works; Create a personal access token; The CLI command (--shutdown-on, --inactivity); Growing into a recurring agent (source apps/docs/guide/automation-sessions.md at 0.202.0)
Linear connection creates tasks from issues, syncs issue status and links artifacts back. With Linear auto-advance, starting an RPI skill moves the issue to that phase's In progress state, writing the artifact moves it to In review, and implementation moves it to in-dev; moving to the next Ready state is manual.
Kind
documented
Locator
Intro; Prepare RPI workflow states (source apps/docs/guide/linear-integration.md at 0.202.0)
Tasks are created from GitHub issues into ticket.md with details, comments and source link. When an agent updates an artifact, HumanLayer adds or updates one comment on the source issue linking the task's current artifacts.
Kind
documented
Locator
Create a task; Use source-issue artifact links (source apps/docs/guide/github-integration.md at 0.202.0)
Oneshot, RPI, PRD-Oriented and Freeform are distinct paths. Users review and amend saved artifacts; later artifacts take precedence. PR creation is a separate skill/action. Freeform has no fixed phases.
RPI skills create and revise task artifacts, split implementation into checked phases and use manual or selected automatic handoffs. PR skills compare the branch diff with the plan, create/update a PR and save a description or optional walkthrough. These are documented agent workflows, not verified delivery enforcement.
Research checks code, tests and named sources and records current behavior. PRD defines problem, success measure and solution; TDD defines system and program design. Each structure-outline phase names one testable result, its files and checks. Later artifacts take priority; current code is the source of truth for current behavior. Checkpoints: design choices stay open until the user answers, a PRD needs approval of the full solution, a TDD needs separate approval of system and program design, outline feedback never starts implementation and normal implementation waits for manual review.
Before switching sessions, write every current decision into the artifact. Design and outline handoffs always wait for the user. Feedback goes through comments or /rpi:iterate-* skills such as /rpi:iterate-implementation. Later artifacts take priority when artifacts disagree.
Kind
documented
Locator
Move to the next phase; Change a plan (source apps/docs/guide/skills-workflows.md at 0.202.0)
0.182.0: /hl:orchestrate breaks down work, launches tasks in separate worktrees, starts sessions, checks task status and PRs, and uploads, copies or moves artifacts between tasks; /hl:teleport moves a task to another machine and starts a new session there; /rpi:describe-pr watches checks, fixes failures caused by the PR and asks for approval before resolving merge conflicts. 0.183.0: the new-task box suggests a workflow based on task size.
Kind
documented
Locator
0.182.0 (2026-10-09) Orchestrate work across tasks, Move a task to another machine, PR follow-up; 0.183.0 (2026-10-14) Pick a workflow by task size
0.160.0: share a running session with teammates for a set time so they can prompt, interrupt and resolve approvals; every message shows who sent it; hand a task to another member. 0.179.0: move a session between Claude Code and Codex on the same task and worktree with the full transcript; view or comment public review links for outside reviewers; in shared sessions the agent knows who wrote each queued message; cost goes to the person who ran the session; an org setting blocks public links.
Kind
documented
Locator
0.160.0 (2026-08-17) Multiplayer Prompting, Transfer task ownership; 0.179.0 (2026-09-29) Hand off to the other agent, Public review links, Better multiplayer prompts, Better usage metrics, Public link setting
Artifact Viewer V2 adds side-by-side version comparison and deep links to comment threads; mobile artifact review supports comment threads; deleted artifacts no longer return as active task files; artifact comments carry Approve and Delete actions.
Research questions keep exact source pointers; research records findings from code, tests and named sources. Worktree setup creates branches and worktrees, copies files and runs setup commands; a setup error blocks completion. /rpi:describe-pr reads the full base diff, compares it with the plan, writes the PR body and saves pr-description.md plus an optional pr-walkthrough.html for large changes. Precedence: plan > structure outline > TDD > PRD > design discussion > research > ticket; live code wins during current-state research.
Kind
documented
Locator
/rpi:create-research-plan; /rpi:create-worktree; /rpi:describe-pr; Artifact roles and precedence; User checkpoints (source apps/docs/reference/skills-workflows.md at 0.202.0)
RPI uses codebase-locator, codebase-analyzer and codebase-pattern-finder sub-agents for code search and a web-search-researcher sub-agent, with listed models and effort.
Kind
documented
Locator
Sub-agent table (source apps/docs/reference/subagent-models.md at 0.202.0)
The CLI lists persistent task IDs/slugs, owner filters and archive metadata. This reference explicitly says a task has no status of its own; draft/running/needs-approval/usage-limit/failed states belong to sessions.
The bundled orchestration reference states that a task has no status of its own; only its sessions carry statuses. Tasks can be listed, paged, filtered by owner and archived.
Desktop releases derive their version at build time and every merge to main ships a new auto-updated version, so the pinned main commit corresponds to shipped builds (GitHub Releases only hold old codelayer pre-releases).
Tasks can be archived from the palette, table or Kanban card and sessions archived in place; org admins can rename or archive teammates' tasks. Projects V2 preview adds a project-first sidebar with enforced sharing settings. A notification bell lists sessions waiting on you. Hosts from automation runs expire on their own and long-offline hosts can be removed without losing history. Sessions carry research, design or implementation labels.
The task board has fixed columns Todo / Draft, Research & Design, Planning, Implementation and In Review; RPI session labels map tasks to columns and unlisted labels fall into Todo / Draft.
Kind
source-inspected
Locator
KANBAN_COLUMN_DEFS and LABEL_TO_COLUMN (lines 9-40)
The built-in orchestration skill uses the HumanLayer CLI to choose hosts, launch tasks and sessions, inspect statuses/PRs and manage task artifacts. This is a product-supplied skill, not evidence of an independently tested cross-harness team.
A task groups related sessions and shared task files with one place for comments; its history continues across agents and workstations. Reviewers comment on synced documents and later agents read the feedback. Task files live in .humanlayer/tasks/<slug>/ and another workstation downloads them when it runs the task. Markdown, text and JSON(L) sync as text artifacts (10 MB limit); images, PDFs and HTML upload through object storage.
Kind
documented
Locator
Share and review a task; Task files have a local and cloud form; Which files sync (source apps/docs/explanation/tasks.md at 0.202.0)
An organization admin creates Slack notification automations that post selected events (design discussion, PRD, TDD or outline created; comment created) for selected owners to one channel.
Kind
documented
Locator
Create an automation; Event types (source apps/docs/guide/slack-integration.md at 0.202.0)
Release 0.149.0 notes that task and session lists were stabilised so rows stop reshuffling while agents run in parallel, i.e. several sessions run at once in the shipped app.
Kind
documented
Locator
apps/docs/release-notes.md lines 675-692 (0.149.0, July 27, 2026, Other Changes), commit f9bd735
You need an online host to run sessions; work queued on a registered offline host cannot start until its daemon runs again. When creating a task you choose the remote host that runs it.
Kind
documented
Locator
Before you turn it off; Choose a remote host (source apps/docs/guide/local-daemon.md at 0.202.0)
The quickstart requires macOS and a HumanLayer account; the app opens a browser sign-in. The task form picks workflow, worktree timing and coding agent per task.
Kind
documented
Locator
Before you start; Sign in; Choose one session path (source apps/docs/tutorials/first-session.md at 0.202.0)
RPI uses named research/implementation subagents with harness-specific model/effort rules. Claude uses fixed model aliases or inherit; Codex children use the parent model with role-specific effort. Experiments control faster research; project/user definitions can differ.
Kind
documented
Locator
Claude Code and Codex tables; Faster Research Subagents; exclusions
Claude and Codex subagents can be continued after they finish, error or are interrupted; CodeLayer subagents delegate at most three levels deep; a Claude Code subagent started by another subagent shows its prompt, tool calls, thinking and text as its own group.
Kind
documented
Locator
0.155.0 (2026-08-12) Subagent resumability; 0.161.0 (2026-08-18) Bounded subagent nesting; 0.181.0 (2026-10-05) Nested subagents in the stream
0.169.0: an Advanced Metrics tab ranks every task by token spend or cost, with six ways to split each bar (agent, model, stage, person or mode). 0.153.0: complete token counts per session and model. 0.183.0: daemon startup on a large org cut from about 4 seconds to half a second (vendor-reported).
Workspace setup uses local Git repositories, branches and one or several task worktrees. A configuration skill proposes shared/local JSON, source refs, setup commands and files to copy. Failed setup can require manual diagnosis.
Kind
documented
Locator
Before you start; Configure with agent; checks; troubleshooting
A daemon host can be a cloud VM, workstation or private-network machine, and the docs explain running the daemon inside a container (credential volume) and on disposable/suspended VMs. The daemon is the host; the docs do not describe HumanLayer creating a container or VM per session.
copyGlobs defaults include .env, .env.local, .env.development.local and .claude/settings.local.json, copied into new worktrees; repositories can only add patterns.
Kind
documented
Locator
copyGlobs (default list) (source apps/docs/reference/workspace-config.md lines 180-211 at 0.202.0)
Daemon launch tokens are short-lived credentials exchanged for credentials that last only for that daemon process. Images that pin the CLI start the daemon with --no-self-update or HUMANLAYER_DISABLE_SELF_UPDATE=1 so the app never installs a different version.
Kind
documented
Locator
Option 2: launch token; Turn off in-app updates (source apps/docs/guide/remote-daemons.md at 0.202.0)
HumanLayer runs two production-grade environments: beta (codelayer.cloud) and production (humanlayer.com). Beta work stays readable; ask the HumanLayer team for export help. Accounts and integrations do not transfer.
Kind
documented
Locator
Intro; Your data on beta; FAQ (unlisted page; source apps/docs/guide/beta-to-prod-migration.md at 0.202.0)
HumanLayer announced it is joining Factory on November 4, 2026. The current platform stays available during a transition of at least 30 days, with data export, Factory migration or open-source self-hosting support and refunds for recent paying customers. No exact hosted shutdown date is stated.
Kind
vendor-claimed
Locator
November 4 announcement; transition period and export/migration/self-hosting paragraph
The minimalist UI moved from alpha to beta and is on by default for new devices. The desktop app, daemon, CLI, web UI, API and plugins are open source at github.com/humanlayer/humanlayer; hosted HumanLayer stays the same. 0.202.0 adds a self-host-humanlayer skill with reference Pulumi stacks.
Kind
documented
Locator
0.183.0 (2026-10-14) Minimalist UI (Beta); 0.201.0 (2026-11-02) HumanLayer core is open source; 0.202.0 (2026-11-14) Self-hosting guide
A reference copy (2026-11-13) of HumanLayer's private Pulumi and GitHub Actions deploy code for self-hosting the cloud on AWS; HumanLayer does not test it outside its accounts and calls it not a supported deploy path. Login requires WorkOS.
Kind
documented
Locator
Intro; 'This is a reference, not a supported deploy path'; required services (WorkOS)