November 2026 status archive, page 23 of 26
Shutdown notices, recent changes and all monthly archives
These events link to today's eligible findings, not historical before-and-after claims.
Cited events
10 ADEs
ralph-claude-codeinitial research30 findings · 9 sources
Findings today
- Ralph for Claude Code supplies terminal CLI commands and a tmux status monitor on documented macOS/Linux…
- The shipped loop runs Claude Code; multi-provider abstraction is still listed as in progress.
- Docker execution accepts ANTHROPIC_API_KEY or a scoped copy of existing Claude CLI credentials.
- Install once, enable or import a project, review .ralph files and run ralph --monitor.
- The product CLI inspects state, manages queues, imports work and controls loop settings.
- Ralph has no MCP, plugin or tool layer; it passes an allowed-tools list to Claude Code and imports PRDs.
- A local PRD file can be added to the persistent queue without a GitHub issue.
- fix_plan.md holds prioritized checkbox tasks while specs holds detailed requirements.
- depends on, blocked by and requires references inside issue bodies become queue dependencies.
- PROMPT.md, AGENT.md and specs/ supply project requirements and build guidance.
- A persistent queue of tasks with priority, dependencies and state exists, and fix_plan.md holds task checklists; it…
- An agent can call ralph-queue commands like any shell user; there are no agent-specific issue APIs or attributed writes.
- A serial queue orders ready items by priority; there is no assignment, routing or ownership model.
- Ralph checks completion inside a manually started loop; the product has no schedule or external-event intake that…
- Ctrl+C interrupts the monitor; loop termination and session reset are separately documented.
- The loop and default Claude execution run on the current host.
- Ralph offers optional Docker execution and an E2B Linux-VM sandbox.
- E2B expiry can recreate the sandbox and upload project files again.
- E2B bootstraps Claude CLI on the default template or accepts a prebuilt custom template.
- Claude invocation timeouts are configurable from 1 to 120 minutes.
- The monitor shows local logs, loop count, API-call usage and queue totals from JSON state.
- Cost visibility is limited to hourly call and token counts and an E2B sandbox hourly estimate.
- The queue is sequential on one branch, not a documented parallel fleet scheduler.
- Tool permissions are an allow list passed to Claude Code from repository configuration; no product approval flow exists.
- Local queue state, logs and the last 50 session transitions persist on disk.
- Queue processing commits one commit per issue on the current branch.
- --backup creates Git backup branches and --rollback restores a selected backup.
- The distributed shell application source is MIT licensed.
- The loop, queue and monitor run locally from the public source distribution.
- README reports active development at v0.11.5 with newer pinned-source changes described as unreleased.
Sources
Open the ralph-claude-code page
ralph-orchestratorinitial researchresearch correctionfreshness recheck27 findings · 9 sources
Findings today
- Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration.
- Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
- Backend setup supports native Claude login and provider API credentials.
- Install Ralph and a supported agent CLI, initialize a backend, then plan or run.
- Ralph provides its CLI and a stdio MCP server scoped to one workspace.
- Runtime tasks can be added, listed and inspected through product commands.
- Interactive planning writes requirements, design and implementation-plan Markdown under .ralph/specs.
- Persistent Markdown memory is shared across parallel loops; tools can search, add and delete entries.
- Ralph owns persistent runtime task records with ready, close and fail operations; a full issue backlog workflow is…
- Runtime task commands are exposed to agents as tools.
- Planning creates persistent requirements and design files; approval and drift gates remain unestablished.
- Additional concurrent loops run in separate Git worktrees.
- The shipped Hatless Ralph coordinator delegates work through named hat events, receives their event results and can…
- Loops can be stopped/resumed; Telegram questions block until answered and proactive messages steer a run.
- Five built-in workflows and direct prompts are documented.
- Ralph normally invokes installed agent CLIs on the current host.
- Ralph separates parallel loop checkouts with Git worktrees and runs native host CLI processes; it provides no…
- Existing loop state can be continued and suspended loops resumed; no crash recovery experiment was run.
- Current configuration bounds iterations and total runtime, with adapter inactivity timeouts and per-hat activation caps.
- Loop logs and event history expose operational state and JSONL export.
- Planning documents and branch diffs can be retained, and publish-review writes a Markdown handoff.
- Backpressure workflows request test, lint and typecheck evidence; instruction examples do not prove that an external…
- Ralph integrates worktree diff, branch publish/rebase and merge operations; publish-review writes a Markdown handoff…
- Optional auto-merge uses merger, resolver and tester hats.
- Ralph application source is MIT licensed.
- The core Ralph CLI and local web stack can run on user-controlled hardware.
- The latest listed release is 2.10.1, published June 23; current README labels the browser dashboard alpha.
Sources
Open the ralph-orchestrator page
Ralph TUIinitial researchfreshness recheck31 findings · 6 sources
Findings today
- Ralph TUI is a native terminal CLI/TUI with documented macOS, Linux and Windows installation and remote terminal…
- Release v0.12.0 names Claude Code, OpenCode, Factory Droid, Cursor CLI, Gemini CLI, Codex and Kiro CLI, plus a…
- Install with Bun, run setup, create a PRD and start from prd.json or a Beads epic.
- Product-owned CLI supports run, resume, status, logs, configuration, tracker conversion and remote management.
- Agent/tracker plugins and installable PRD/task skills extend the orchestrator.
- Terminal interface uses OpenTUI/React and Bun; no Electron desktop client was established.
- Intake supports local prd.json and external Beads, plus conversion into tracker formats.
- Interactive AI-assisted PRD creation and progress files retain plan/context between iterations.
- One graph spans selected epics and blocks dependent work on incomplete external dependencies.
- Product progress file retains cross-iteration context and custom skills/templates can be selected.
- Optional parallel worker pool executes independent tasks simultaneously in worktrees.
- Scheduler selects highest-priority ready tasks and dispatches them from a dependency graph.
- Ralph TUI has a deterministic parallel worker engine and provider-subagent tracing, without a product-supplied agent…
- Keyboard and remote actions pause, resume, interrupt or cancel execution, with persisted logs.
- Multi-epic sessions show source scopes and shared workers in a single scheduler UI; no fleet usability fixture was run.
- Agent/model selection, custom templates and task-tracker plugins configure execution.
- Run engine on the local machine or a user-controlled VPS/CI host and control it from another TUI.
- Ralph TUI uses Git worktrees for parallel file separation and optional bubblewrap/macOS sandbox-exec process policies.
- Sessions can be resumed and remote connections use bounded reconnect retries.
- Iteration limit bounds loop count; preflight timeout bounds setup checks, not all runtime/tool effects.
- Dashboard displays agent/model, tracker, branch, sandbox and remote status; log files retain iteration output.
- Worker pool and dependency grouping bound concurrency; OS sandbox explicitly does not enforce CPU/RAM/process limits.
- Remote tokens and opt-in sandbox paths/network constrain access; no enterprise approval workflow established.
- Remote actions are logged to a local audit.log; immutable retention is unestablished.
- PRD/progress and per-iteration logs persist on disk.
- Ralph TUI integrates worktree merging, conflict handling and optional commits, then prints a manual gh pr create…
- Orchestrator merge queue brings completed worker branches back sequentially.
- Backup tags are created before each merge for rollback safety.
- Ralph TUI application source uses MIT license.
- Core CLI/TUI engine and authenticated listener run on user-controlled machines.
- Latest listed release v0.12.0 was published May 13, 2026; current default-branch documentation may include later…
Sources
Open the Ralph TUI page
ralphexinitial researchresearch correctionfreshness recheck30 findings · 6 sources
Findings today
- Ralphex is a primary native CLI on Linux/macOS and best-effort Windows source builds, with an optional responsive…
- Claude Code and Codex have first-class executors, several named agents have shipped wrappers, and the first-party…
- Provider authentication is inherited from agent CLIs; Claude headless subscription use has a separate billing warning.
- Run from a Git repository with a plan and installed coding agent.
- CLI configures plan creation, execution, review, worktrees and dashboard.
- Custom prompts, review agents and provider configuration extend the workflow.
- Markdown plans are authoritative local execution input.
- Plans retain validation commands, tasks and checkbox progress; paused work can be amended.
- Plan tasks execute sequentially with configurable multi-phase reviews.
- Repository guidance and review prompts can be configured per project.
- Parallel review agents and independent worktree plan runs are documented.
- Ralphex owns deterministic task/review phases and ships reviewer prompts, but delegation uses Claude Task or Codex…
- Unix signal controls pause/abort execution; notifications are optional.
- Dashboard watches multiple plan progress files without a verified epic-management fixture.
- Modes and per-phase model settings are configurable; workflow changes are mostly configuration-driven.
- Ralphex runs installed agent processes on the operator machine or Docker host.
- Ralphex offers Git worktrees and a Docker wrapper.
- Plan progress and interrupted worktrees survive, but context is intentionally fresh per task.
- Iteration, review-patience, timeout and rate-limit controls are documented.
- Timestamped logs and dashboard expose progress; this is not a tested state-consistency result.
- Default Claude invocation bypasses permission prompts; safer host isolation is optional.
- Plan, commits, progress logs and reviewer output are retained.
- Default pipeline requests validation and multiple review phases; tasks-only and optional stages limit enforcement.
- Ralphex creates branches/worktrees and commits, and its optional finalize prompt rebases/organizes commits.
- Finalize is optional customizable agent automation, not a tested delivery authority boundary.
- Completed plans and commits persist; success has a documented archive caveat.
- Repository source is MIT licensed.
- Core standalone CLI requires no product cloud service.
- Public release and issues exist, with explicit best-effort Windows support.
- Open-source binary and source allow evaluation with user-provided agents/compute.
Sources
Open the ralphex page
Replitinitial researchresearch correction41 findings · 44 sources
Findings today
- Replit offers browser and phone-browser access, native iOS/Android clients, and native desktop apps on Mac, Windows…
- The documented development experience runs Replit Agent with selectable modes/models.
- Replit plan credits pay for Agent.
- Start a project by describing an idea in plain language, or bring it in from GitHub, Figma or uploaded files, in the…
- A main-thread prompt can create titled tasks with descriptions and plans, or users can start a planning thread.
- Agent proposes detailed plans and definitions of done; users inspect View plan, accept tasks or request a revised…
- Agent identifies prerequisite tasks and queues dependent work until the prerequisite is applied.
- Each background task inherits the project context and receives its own Agent and project copy.
- Projects can begin from GitHub, Figma or uploaded files; this establishes input channels, not verified architecture…
- Native tasks have Drafts, Active, Ready and Done states, a board, separate threads and explicit acceptance.
- Agent can split a request into tasks and put them on the human-visible task board.
- Core supports one active background task, Pro up to ten and Enterprise up to sixty-four.
- Agent schedules independent tasks when capacity exists and holds dependent tasks until prerequisites are applied.
- Replit Agent decomposes a request into background Agent tasks with separate threads and returns work logs, tests and…
- Paid-plan chat Routines repeat hourly, daily or weekly without a new request.
- Cancel stops building and discards its work.
- A project board displays Drafts, Active, Ready and Done tasks alongside task conversations.
- Users start with ordinary chat, refine plans and let Agent create task lists before approving work.
- Replit provides managed cloud development, and the current desktop page also offers local Agent code/build execution…
- Replit repository development sandboxes explicitly use microVMs.
- Files, history and running app are preserved in the cloud for a later visit.
- Agent sets up the project and infrastructure.
- Core and Pro Routines have per-run budgets checked after each step; an in-progress step can complete beyond the budget.
- Finished tasks expose a work log, test results and preview; active threads and board cards show task status.
- Agent billing is effort-based and uses plan credits shared with cloud services.
- Plan-based task limits cause additional background tasks to queue until slots are available.
- Invited teammates work on one project through separate Agent threads and shared task boards.
- Personal workspaces have an admin and project guests; team workspaces add members with access to all workspace projects.
- Humans approve plans before background execution and apply or dismiss finished changes before they affect the main…
- Replit displays code diffs in its Changes pane, alongside local changes or linked PRs, in addition to task logs,…
- Task review retains a work log, test results and a live preview in the task flow.
- With App Testing enabled, Agent periodically tests apps it builds in an actual browser and fixes issues it finds.
- The repository contribution workflow creates branches, commits/pushes code and opens draft GitHub PRs or GitLab MRs,…
- Users publish to a live URL from the Project Editor.
- Agent creates checkpoints that users can roll back to when a change is wrong.
- Replit imports/exports project artifacts and offers Enterprise deployment options, but even Full BYOC explicitly…
- Pro users can opt out of Model Improvement in Personalization settings, and Replit states it does not train on…
- Replit supplies recurring Core/Pro plans and metered Agent/cloud credits.
- The November 6 changelog documents Agent-assisted support investigation and Pro ticket submission.
- Starter offers recurring daily Agent credits capped monthly and monthly cloud credits, with one published app whose…
- Agent uses effort-based paid pricing with plan credits; actual charges depend on request complexity and cloud services.
Sources
Open the Replit page
scioninitial researchresearch correctionfreshness recheck32 findings · 12 sources
Findings today
- Scion provides native macOS/Linux CLI and Windows Hub-client CLI distributions, Workstation/hosted browser UI and…
- Named harnesses include Claude Code, Codex, OpenCode and Antigravity; credential guide explicitly includes Gemini CLI.
- Workstation injects user native harness login files or API keys; hosted broker credentials must be explicit.
- Onboarding detects container runtime, identity and images; init links project to Hub.
- Product CLI and Hub JSON APIs expose agent/project lifecycle and messaging with scoped authentication.
- Templates, versioned Skill Bank, lifecycle hooks, MCP configuration and A2A bridge extend integrations.
- Hub owns projects and agent tasks/summaries, but companion issue trackers remain separate tools.
- Templates, versioned skills and shared directories provide team context; specialized memory systems are companions.
- Agents run concurrently on local or remote infrastructure with per-broker admission limits.
- Agents can delegate through CLI and operate under recorded parent/creator authority.
- Scion provides agent creation, readable descendants, messaging and completion/attention visibility through product…
- Hub-owned cron schedules start recurring agents/messages with timezone-aware timing and recorded authority.
- Users message agents and inspect logs, stop/resume sessions and receive attention notifications.
- Web/CLI list and inspect agent fleet with phase, lineage and status.
- Users define roles and collaboration in instructions/skills rather than a fixed orchestration graph.
- Scion supports local Workstation or user-operated durable hosted Hub/brokers on VM, Kubernetes or Cloud Run.
- Scion has container and Git worktree/clone separation.
- Agents can stop/resume; hosted durability differs between single-node SQLite and replicated Postgres.
- Runtime onboarding, container images and credential provisioning prepare execution environments.
- Hub refuses starts on unresolved credentials and enforces per-broker running-agent admission; provider usage/spend…
- Hub exposes phase/activity, logs, session metrics and system health.
- Hub limits running agents per broker, with reservations reconciled at startup/hourly.
- Feature-flagged native chat allows humans and agents in shared project threads, with a default agent and…
- Hosted users have admin/member/viewer roles and project role bindings, with revocation/suspension and…
- Scoped agent tokens, role bindings and narrowing access constraints govern Hub operations; this is not proof of…
- Access-boundary mutations retain transaction-bound audit history; deletion removes boundary history, so immutable…
- Experimental artifact review supports retained marks and versioned review outputs.
- Experimental default-off artifact service stores versioned files/folders on Hub and exposes CLI/web access and review.
- Scion core application/platform source uses Apache-2.0.
- The core Hub, clients and brokers run on user infrastructure in Workstation or hosted mode.
- Scion supports explicit hosted credentials and optional workstation credential injection.
- Current nightly November 8 and preview releases document pre-1.0 actively evolving platform.
Sources
Open the scion page
Supacodeinitial researchfreshness recheck22 findings · 5 sources
Findings today
- Supacode ships a native macOS 26+ application and its local CLI.
- Supacode runs coding CLIs in real terminal panes and ships presence/skill integrations including Claude Code, Codex,…
- Local plain folders and Git repositories are supported; source builds need macOS/Xcode/mise and submodules.
- Product CLI and deeplinks address repos, worktrees, tabs and surfaces; session IDs are exported.
- Native macOS client uses libghostty with The Composable Architecture and zmx.
- Several coding agents run side by side, with one worktree/terminal per task.
- Agent presence badges, attention notifications and worktree hoisting expose need for input; terminal input provides…
- Worktrees can be created by UI, CLI or deeplink, and named repo/global scripts run in dedicated tabs.
- Local execution and beta SSH-host execution are documented.
- Supacode separates tasks with Git worktrees and terminal sessions.
- zmx sessions are independent of app lifecycle, retain scrollback and reconnect after relaunch.
- Per-repo setup/archive scripts and named custom scripts are supported; environment repair unestablished.
- Presence and live branch/file/PR state help track work.
- Supacode retains terminal output and Git/PR state.
- Worktree management and GitHub PR actions show PR state, checks and merge readiness; site explicitly says open PRs.
- GitHub integration exposes PR merge actions and configurable merge strategy.
- Supacode application source uses FSL-1.1-ALv2.
- Core native application and local/remote zmx run on user hardware; commercial activation is required beyond trial…
- One-time USD 99 Basic, USD 129 Standard or USD 79 per Team seat, minimum three.
- Latest listed release v0.11.7 was published November 7; security support targets latest release.
- Five local worktree creations are trial access; existing worktrees/terminals stay usable and SSH worktree creation…
- Public lifetime-license prices, seat counts, trial quota and update renewals are stated.
Sources
Open the Supacode page
Traycerinitial researchresearch correctionfreshness recheck38 findings · 17 sources
Findings today
- Traycer Desktop ships macOS/Windows/Linux clients, native iOS/Android companions and a product CLI.
- Traycer documents multiple coding agents and model switching with shared context.
- Existing coding-agent subscriptions are supported; optional Traycer inference has separate billing.
- Install Desktop, sign in, prepare the Host and select agents.
- Traycer has task, agent, worktree and host commands with scoped agent access.
- Traycer manages MCP configuration per provider; availability differs by provider.
- Tasks are local work containers associated with one or more folders.
- Built-in skills create durable brief, technical-plan and ticket artifacts.
- Ticket breakdown and execute describe dependencies and batched work through skills.
- Tasks retain planning artifacts and support built-in planning and review skills.
- Traycer retains Tasks independently of their multiple agents and provides organization in History.
- Requirements revision is a documented skill, but persistent product-wide conformance is untested.
- Parallel agent work is documented, with visible status in Agent Office.
- Agents can claim named roles when the optional Agent roles setting is enabled.
- Traycer-owned agent commands support cross-harness delegation, transcripts and replies.
- Traycer documents an external host-cron recipe that creates nightly Tasks with idempotency keys.
- Agent Office supplies lineage, messages and state views; the 12-task fixture was not run.
- Optional skills and per-agent configuration support different workflow sizes.
- Agent execution can use the local host or a user-provisioned remote host.
- Separate Git worktrees are documented; this source does not establish a security boundary.
- Transcript durability is documented separately from availability.
- Worktree setup/teardown scripts support dependency setup with visible failure cards.
- Tasks, artifacts and shared chats are visible to collaborators, but shared prompting is explicitly restricted.
- Task Owner/Editor and team Admin/Member roles are documented; SSO/SAML is unavailable.
- Agent creation exposes permission modes with full_access as the default.
- Review skills retain findings and a walkthrough, while artifacts support discussion.
- Specs, tickets, reviews and walkthroughs are durable Task artifacts.
- Execution/review skills propose verification; the source explicitly denies automatic enforcement.
- Traycer integrates worktrees and PR state; feedback can be sent to the associated agent.
- PR rows link Tasks/chats to commits and delivery state; rollback was not tested.
- PR stacks and review summaries support browsing several changes, without a tested shipping queue.
- Repository source is MIT licensed; hosted parity is not established.
- Hosts run on user machines, but account, relay and cloud-sync services remain vendor dependencies.
- Traycer discloses product analytics and separate provider requests.
- Free product access is separate from inference and paid team-wide sharing.
- Desktop release and first-party support channels are public; SLA was not established.
- Recurring Free includes own agents, sync, remote hosts and mobile; whole-team sharing requires Sync.
- Public plans separate product access and optional inference credits.
Sources
Open the Traycer page
v0initial researchresearch correction37 findings · 39 sources
Findings today
- v0 provides a browser chat, tool cards, live previews and browser-use screenshots.
- The v0 sandbox includes a supported Claude Code wrapper invoked with claude.
- v0 credits pay for generation and platform fees.
- A GitHub import creates a chat on a selected base branch; the first generated change creates a working branch and…
- The v0 API creates chats and apps, sends messages, embeds authenticated previews and deploys to Vercel.
- Users can connect preset or custom MCP servers to give v0 additional external tools during generation.
- The beta Slack bot accepts @v0 prompts, reads the thread and creates a code branch and pull request.
- The Plan Mode instruction asks v0 to outline an approach, steps and risks and request approval before implementing.
- Reusable named instructions are saved to the account, available across chats and projects and applied until unchecked.
- v0 searches the web with linked sources and uses a browser to inspect previews or external sites, supplying…
- Users can stop the agent, see tool execution cards and follow automatic continuation through multi-step work.
- Natural-language requests select web search, browser use, integrations or terminal execution; action progress is…
- VM-backed chats run project files, Node.js preview servers and shell commands in Vercel Sandbox virtual machines.
- Each VM-backed chat has separate files, processes and environment variables; sandbox ownership follows the chat…
- The chat filesystem persists between sessions.
- Sandboxes include Node.js and pnpm, npm, yarn and bun; a framework-aware dev server starts on the appropriate port…
- A sandbox has an absolute twenty-four-hour maximum and receives automatic active-use extensions within that cap.
- Chat shows progress indicators, tool execution cards, browser screenshots and source links; deployment Fix with v0…
- The dashboard groups credit consumption by chat or project.
- Team members can receive Can Edit access to a chat and generate changes; shared chat history is included on Plus,…
- Plus members have Builder access.
- Sandbox terminal execution has Ask, Auto and Full permission modes; actual deny and revoke enforcement was not tested.
- Save commits tracked manual file changes and Discard restores the latest commit; generated message versions retain a…
- A message Diff tab displays version changes; users can select diff lines and attach comments to the next prompt.
- Chats can be transferred between personal and team scopes, bringing the full prior history into the team-owned chat.
- Browser-use screenshots and preview context appear in chat along with tool output.
- The GitHub Publish flow respects required checks, reviews, draft state and branch protections; blocked merges remain…
- v0 automatically commits and pushes to a chat working branch, creates PRs, displays CI and offers fixes for CI or…
- Publish creates or reuses a pull request, merges to its base branch and waits for production deployment, subject to…
- Users can view and restore previous generated versions.
- The code viewer can copy or download files, including pending edits.
- Enterprise customers can opt out of content use for model training, and Enterprise data is processed on separate…
- Plus costs USD 30 per user monthly and Business USD 100, with USD 30 monthly credits each.
- The October 19 changelog announces the shipped Slack integration.
- The vendor asserts that v0 is included in Vercel SOC 2 Type 2 attestation covering Security, Confidentiality and…
- New Free signups receive a one-time USD 5 allowance which does not renew; existing Free users retain a USD 5 monthly…
- The public plan table gives monthly prices, included credits and credit expiry.
Sources
Open the v0 page
Wakuinitial researchresearch correctionfreshness recheck23 findings · 5 sources
Findings today
Sources
Open the Waku page
10 ADEs
Orchestrator.incresearch correctionfreshness recheck3 findings · 24 sources
Ampfreshness recheckresearch correction51 findings · 19 sources
Findings today
- Amp offers Mac (macOS 26+, Apple silicon), Windows (10 1809+ or 11, x64 and Arm) and native Linux desktop apps…
- Amp supplies its own coding-agent harness across clients and builds prompts and tools around the selected model;…
- The pricing guide supports linking ChatGPT and Claude subscriptions.
- The quickstart permits a project without a Git repository.
- A public External API v2 covers workspace thread data, members, projects and repository search, groups,…
- Local commands and remote MCP servers are supported.
- Docs call the Mac, Windows and Linux apps native; Windows installs through App Installer for x64 and Arm.
- GitHub webhooks can continue threads or spawn Orbs from issues and pull requests.
- Thread artifacts can hold plans and checklists, persisted with the thread.
- A Space groups threads under an optional goal and project (since Nov 6, 2026); it is not a structured epic record.
- Amp loads AGENTS.md in the current directory, parents and relevant subtrees, plus personal and system guidance.
- Finder returns file paths and line ranges; answers are not documented as citing sources.
- Threads archive, unarchive and snooze; a separate issue entity is not documented in the checked pages.
- Space cards show each thread’s live status and whether it needs someone.
- Artifacts can retain a plan or requirements document with a thread; a dedicated executable requirements schema is…
- The Orb guide describes several independent tasks running at once, each with its own environment.
- @Amp in a public Slack channel linked to a workspace-shared Space starts work there.
- Task executes delegated work and Read Thread summarizes threads.
- Amp saves one schedule per thread; it can run once or repeat, with pause, resume and delete controls.
- A snoozed thread surfaces and notifies when it needs an approval or answer.
- Unread dots, taskbar or launcher counts, and tray dots for waiting threads; apps notify when a thread is ready.
- The model selector sets each thread's model, effort and speed, replacing the Dial removed on 2026-11-12; plugins can…
- The CLI can run Amp on the user's own machine.
- Runner worktree creation also creates a named branch.
- Docker-backed Orb services restart when a portal is reopened after wake; terminal and desktop process state is not…
- Install shared dependencies in .agents/setup.
- Setup stops after 20 minutes; a failed or timed-out setup does not publish a refreshed snapshot.
- A Space chart counts the last 30 days of threads as Shipped, Archived or Open (Done where commits cannot be seen).
- A thread's dollar indicator opens detailed usage; this is documented, not reconciled against invoices.
- After a burst of twenty metered Orb starts per user, later starts queue at one every five minutes.
- Workspace members can chat with each other in the thread.
- Member and Admin roles are documented; Admin manages membership, billing, settings and policies and can view private…
- Multiplayer starts with a seven-day duration, can end early and expires automatically.
- Enterprise admins can access authentication event audit logs; comprehensive application audit logs remain internal.
- The Changes pane offers all changes, uncommitted changes or a selected commit.
- Colleagues use the same thread and Orb or shared runner while multiplayer is active; disconnect takeover was not tested.
- The thread's Changes view shows the diff, alongside files, services and conversation.
- Default Ship asks the agent to run the full test suite.
- Push to Branch ships to a feature branch instead of the base branch.
- Default Ship writes directly to the base branch after rebasing; PR approval and merge-policy enforcement are not…
- The thread records linked PRs when the PR description includes its thread URL or ID.
- TypeSafe's Jev model suggests the next action in a thread; no review queue is documented.
- Amp access is covered by the limited, revocable service license in its custom terms.
- Amp explicitly says it does not offer self-hosted deployments of its control plane.
- Local code snippets and context can be sent to Amp Server and model providers.
- Public tiers are Hobby free, Megawatt $20/month, Gigawatt $200/month, Teams at no additional workspace charge and…
- Orbs cost $0.08-$2.13 per hour by size, billed per minute and only while running; Megawatt includes 45,000 orb minutes.
- Dated releases include Android (Oct 27), Artifacts (Nov 2), Service Accounts (Nov 3), GitLab (Nov 5), Spaces (Nov 6)…
- Amp publicly states SOC 2 Type II certification; the underlying report was not inspected.
- The Hobby tier is recurring free; model usage and hosted compute may still cost money.
- Agent usage is billed in credits and Orb compute by the minute.
Sources
Open the Amp page
Google Antigravityfreshness recheckresearch correction20 findings · 59 sources
Findings today
- Desktop on macOS 12+ with Apple Silicon or Intel, Windows 10 64-bit+, Linux and Googlebook; CLI and IDE extensions.
- One Antigravity harness with plan-dependent Gemini, Claude and GPT-OSS models.
- Free, Google AI Pro/Ultra subscriptions, AI credits and Gemini Enterprise licenses are documented; API keys work in…
- Teamwork breaks a brief into milestones and parallel tracks; user-visible epics, blockers and readiness are not…
- Custom subagents and Teamwork roles support messaging, result return, live progress and follow-up; cross-harness…
- Quick tasks, plan mode, Teamwork for large work and natural-language custom agents are documented; run-time role…
- Local execution, browser Remote Control of user hosts, and Google-managed Remote Agents, whose rollout to Google AI…
- Sessions can be resumed, the Remote Control web UI tries to reconnect after network drops, and the headless Remote…
- Headless print mode defaults to unlimited time with an optional --print-timeout.
- Conversation histories persist across sessions and Teamwork records logs; export and integrity guarantees are not…
- Diffs, plans, walkthroughs, diagrams, screenshots and browser recordings are produced as artifacts.
- Agents run tests, hooks can run linters and block stops, and Teamwork adds reviewer gates; configured CI gates are…
- Free plan $0/month; Business Standard/Plus from $30 USD per seat per month for eligible Gemini Enterprise customers,…
- App v2.34.0 (Nov 20, 2026), CLI v1.5.12 (Nov 19) and SDK v0.1.24 (Nov 16) are labelled Latest.
- Individual plan is $0/month with basic weekly rate limits and unlimited Tab completions; Pro and Ultra add limits…
- Pricing units are per seat per month or consumption; included limits are qualitative; subscription options require…
- Teamwork captures requirements in a request artifact and maintains milestone plans and progress, with prompt…
- Enterprise SSO, Workforce Identity Federation and BYOID are documented; licenses are assigned by the organization's…
- Command, MCP, URL and file approvals with allow/ask/deny rules and presets exist; approver identity and revocation…
- Desktop threads can be imported into the CLI; 2.0 v2.19.1 can export rendered Markdown in artifacts as PDF; SDK…
Sources
Open the Google Antigravity page
Augment Codefreshness recheckresearch correction49 findings · 21 sources
Findings today
- Cosmos explicitly has no separate iOS or Android app.
- Augment supplies the Auggie/Cosmos coding agent with a selectable model catalog.
- The CLI setup requires an Augment account login.
- Install the prerelease npm package on Node 20+, open the project and run auggie auth login; setup timing was not tested.
- Auggie --print executes one instruction and exits; --mode stream or json controls programmatic output.
- Expert Capabilities bundle tools or MCP servers.
- Triggers include GitHub PRs, Linear status changes, Slack messages and custom webhooks.
- IDE Tasklist retains sequential steps and can be moved into a new chat.
- Agents generate nested subtasks beneath an initial task.
- Reusable agent-skills packages are stored in Files and provide specialized instructions.
- The project is indexed automatically on starting Auggie in its directory; freshness behavior was not tested.
- Humans create IDE Tasklist tasks using Add Task; the agent can also generate them.
- The agent can generate a task list and nested subtasks.
- Project Builder drafts a design document and ticket breakdown; persistence and revision enforcement of a…
- Auggie subagents run in parallel with independent context.
- Cosmos routes tickets to worker Experts and documents Slack-thread or ticket claiming.
- Project Builder coordinates PR Author implementation workers.
- Cron is a documented Cosmos trigger source.
- The IDE Tasklist red square interrupts the current task.
- Cosmos shows a run’s worker tree in the session sidebar and records trigger runs in Run History, including recent…
- Project Builder handles a large feature through design, architecture, tickets and coordinated implementation.
- Auggie CLI executes beside local code with Node 20+ on macOS, Linux or Windows WSL.
- Each isolated daemon session gets a separate Git worktree for every configured repository.
- Environments pause when inactive and run at most 24 hours at a time.
- Cosmos environment documentation describes base or custom images, snapshots after cloning and authorized secret…
- A Cosmos Environment runs up to 24 hours at a time.
- Interactive mode shows tool calls/results; print mode emits a final response and Request ID unless JSON output is…
- The Outcome Analytics release says session costs remain visible only to admins; invoice reconciliation was not tested.
- Cosmos daemons cap concurrent sessions with maxAgents, default 100, and pools route by daemon load.
- Shared sessions are visible to the organization; private sessions only to the owner unless explicitly shared.
- Administrator and Member have separate membership, billing and plan permissions.
- The vendor says consequential actions pause for human approval; exact authority enforcement was not tested.
- A conversation is saved indefinitely, including when an automation archives it.
- Tasks and Changes views show diffs for each completed task.
- Cosmos preserves the conversation and artifacts for authorized viewers, and Organization Files pass outputs between…
- Files are stored in a virtual filesystem, with organization-shared and user-private visibility.
- Cosmos includes an automated PR-review expert; exact-revision approval and enforced delivery gates were not established.
- PR Author creates the implementation branch.
- Cosmos agents do not perform the final merge.
- PRs opened through the Cosmos GitHub tool attach to the session automatically and are searchable.
- Cosmos documents per-PR review summaries, findings, repair and evidence, plus policy-based risk routing.
- The main Augment/Auggie/Cosmos platform is governed by vendor-authored professional/enterprise service terms.
- Cosmos daemons execute on user infrastructure while depending on Augment services.
- All paid plans exclude AI training on customer data according to the pricing FAQ; retention and telemetry require…
- Public plans are USD monthly.
- Auggie 1.x is prerelease; stable 0.x is separately available.
- The vendor asserts SOC 2 Type II on the pricing page; report period, scope and independent verification were not…
- The complete public plan list has paid Standard, Business and Enterprise plus trial access, without a recurring free…
- Usage is measured in dollars across models, Context Engine and compute.
Sources
Open the Augment Code page
Capyresearch correctionfreshness recheck10 findings · 28 sources
Findings today
Sources
Open the Capy page
Claude Codefreshness recheckresearch correction51 findings · 125 sources
Findings today
- Claude Code has CLI, Desktop, IDE, browser and mobile clients.
- Claude Code embeds its own harness and runs Claude models only.
- Pro, Max, Ultra, Team and Enterprise include Claude Code.
- Programmable access is strong on the CLI: claude -p with JSON output, Python/TypeScript Agent SDK, claude mcp serve…
- Ordinary TaskUpdate changes task dependencies.
- TaskCreate, TaskGet, TaskList and TaskUpdate manage session checklists.
- Agent teams (experimental) document lead assignment and file-locked task claiming; outside teams, assignment is the…
- Delegation is inspectable through subagents (own model, effort, tools), agent teams, cross-session messaging and…
- Cloud scheduled tasks, formerly routines, support schedule/API/GitHub triggers independently of the laptop.
- Agent view (research preview) is a terminal fleet screen that groups background sessions under Needs input, Ready…
- Quick tasks are one prompt away; larger efforts use subagents, agent teams, projects (cloud beta) or dynamic…
- Claude Code runs locally by default; cloud sessions run on Anthropic VMs (4 vCPU, 16 GB, 30 GB) with no separate…
- Limits include print-mode --max-turns and --max-budget-usd (client-side estimate), subagent maxTurns, tool timeouts,…
- Cost views: /usage session cost (client-side estimate at list price unless an administrator's managed modelPricing…
- Review is available through /diff, Desktop diff view with inline comments, local /code-review, and managed GitHub PR…
- Pro $20/month or $200/year; Max $100/month; Ultra $200/month.
- Fixed subscription examples: one Pro $20/month or $200/year; two Team Standard seats $50/month or $480/year; five…
- GitHub releases run to v2.1.322 (Nov 10, 2026, marked Latest).
- Free excludes Claude Code; all paid plans include it.
- Public seat prices, plan multiples and separate API rates are stated.
- CLI onboarding is one install command plus browser login, and works in any directory.
- No native issue tracker was found in the documentation, changelog or repository checked; work arrives by prompt,…
- Isolation options: git worktrees per session, an OS-level sandbox for shell commands (macOS/Linux/WSL2, off by…
- Cloud environments offer setup scripts, a filesystem-snapshot cache, network access levels and pre-installed…
- Compute-aware scheduling is limited: Remote Control and self-hosted runners cap concurrency, Bash commands have…
- Verification is policy you configure: hooks run commands and can block actions or task completion (exit code 2),…
- Prompts and outputs go to Anthropic (or the chosen provider) over TLS 1.2+; consumer plans train on data only when…
- Claude Code is an MCP client (http, sse, stdio, websocket) with OAuth and scoped config, supports…
- The mobile app is a client for cloud or Remote Control sessions, and IDE extensions wrap or bundle the CLI engine.
- Plan mode proposes a plan before edits and plans can be saved into the repository; /goal tracks a completion condition.
- Persistent instructions and memory are documented: CLAUDE.md at managed/user/project/local scope, AGENTS.md reading,…
- Code understanding relies on agentic search (grep, glob, file reads) plus optional LSP code-intelligence plugins and…
- Living product specifications were not found as a native feature; instructions files and plans in the repository are…
- Parallel work is supported locally (multiple terminals, worktrees, subagents, agent view background sessions, Remote…
- In the CLI a human can interrupt, stop, queue steering messages and resume sessions; background sessions show Needs…
- Sessions persist as local transcripts and resume; cloud sessions restore history after VM reclamation but lose…
- Operational statistics are available via /usage, /insights, OpenTelemetry metrics, logs and traces (beta), and the…
- Live multi-human collaboration is limited.
- Roles and access are managed at the Claude account level: Owners and admins configure cloud environments and…
- Approvals are per-user permission prompts governed by permission modes plus allow/ask/deny rules, hooks and…
- History comes from local session transcripts, checkpoints, OpenTelemetry events and, on Enterprise, audit logs.
- Takeover is mostly same-user: teleport and Remote Control move a session between one person own devices; colleagues…
- Outputs include diffs (/diff, Desktop diff view), live Artifact pages published to claude.ai, Desktop app preview,…
- The CLI supports git workflows: it can create commits and pull requests on request, run in isolated worktrees, link…
- Merge and deployment authority is delegated to git/CLI permissions: Bash allow, ask or deny rules can gate push and…
- Completion evidence is session links to PRs and OTel commit/PR counts; rollback is via /rewind checkpoints on local…
- High-volume shipping features are limited: agent view summaries, /batch splitting a change into worktree subagents,…
- Claude Code is proprietary: the public repository LICENSE.md states "© Anthropic PBC.
- The installed Claude Code CLI can run its full agent loop, tools and context management on user-controlled…
- Claude Code documentation points to the Anthropic Trust Center for compliance artifacts.
- Claude Code has persistent native task checklists with optional cross-session lists and experimental team…
Sources
Open the Claude Code page
Claude Squadinitial researchresearch correctionfreshness recheck30 findings · 7 sources
Clinefreshness recheckresearch correction46 findings · 18 sources
Findings today
- Cline supplies Desktop, IDE, CLI/SDK, Kanban and Cloud Agents clients.
- The Cline SDK has native Claude Code and Codex CLI adapters and an OpenCode runtime; optional provider packages are…
- Cline supports Claude Pro/Max subscription access via an installed authenticated Claude CLI provider.
- Kanban requires Node 18+, a Git repository root and npx kanban; it starts a local browser server.
- The CLI is documented for scripting and CI/CD.
- Cline supports connecting MCP servers for external tools and data.
- The pinned technical README describes Cline Desktop as a Tauri shell with Bun sidecar and Next.js UI; no…
- Users add task cards manually or through sidebar chat.
- The IDE extension offers Plan mode, persistent task history and checkpoint restoration.
- Linked cards form chains; the next task starts after the prior card completes and is moved to trash.
- Memory Bank uses project Markdown files for requirements, architecture, technical context and progress.
- Cline explicitly says it does not index or embed repository contents; it reads files on demand.
- The Kanban board stores manually created cards before play is pressed.
- The sidebar agent can create and link human-visible cards; API permission/conflict behavior remains unknown.
- Memory Bank projectbrief.md stores requirements and goals in the repository.
- Desktop supports multiple independent agent sessions in parallel.
- Kanban cards select their running CLI agent.
- One coordinator delegates subtasks to specialist teammates.
- Desktop has one-time and recurring Schedule entries with prompt, provider, model, workspace and optional timeout;…
- Documented client-specific controls include cancellation, resumption, follow-ups and retained task history.
- Cards show latest agent message or tool call; a twelve-state fleet fixture was not run.
- Users can describe a recurring task in chat to create a schedule.
- Desktop runs sessions on local hardware.
- Each Cloud Agent session receives its own repository copy.
- Cloud sandboxes pause after 15 minutes of inactivity.
- Gitignored dependencies such as node_modules are symlinked from the main repository; writes affect the shared target.
- CLI --timeout sets a task duration in seconds; zero means no timeout.
- --json streams timestamped agent events and a final run_result.
- Session cost includes subagent costs.
- At most ten Cloud Agent sessions run concurrently.
- Enterprise documents Member, Admin and Owner with organization-scoped permissions.
- Team task-board, mailbox and mission-log state is stored in teams.db and restored when the session resumes.
- Inline diff comments go back to the agent as feedback.
- Imported conversation context can continue in Cline; this does not establish preservation of the original runtime or…
- Card details expose the TUI and cumulative or message-range diffs.
- Cloud Agents use a cline/ branch per task.
- Commit sends a dynamic prompt to merge worktree changes to the base branch; a prompt is not proof of an enforced…
- The cloud sidebar reports working, done or awaiting-input session states; this alone is not merge evidence.
- The repository LICENSE at a459f1d04dea030833b558be645011ab739c463b is Apache-2.0; hosted components and separate…
- The open-source Cline core and its tools run locally or on user-controlled remote hosts with a chosen inference…
- Cline/ClinePass inference telemetry can contain prompts and responses; other providers do not send prompt contents…
- The overview lists ClinePass at $9.99/month for selected open coding models, checked 7 November 2026; exact caps…
- Documented cost components include ClinePass model access at $9.99/month, pay-as-you-go credits or BYOK and custom…
- Cline Kanban is a research preview with experimental capabilities; this does not classify the stable IDE extension…
- The open-source extension and CLI are free for individual developers.
- The open-source version has no subscription or seat fee.
Sources
Open the Cline page
cmuxresearch correctionfreshness recheck44 findings · 8 sources
Findings today
- cmux supports local terminals, user-owned SSH hosts and paid early-access persistent Cloud Linux machines.
- cmux can run locally; session snapshots export/import as JSON, while production server components have separate…
- cmux offers stable and nightly builds, public issue support and early-access Cloud.
- cmux runs terminal coding agents including Claude Code, Codex, OpenCode, Gemini CLI, Cursor Agent, Aider, Grok and…
- cmux supplies reusable skills for workspace, browser and CLI automation.
- cmux documents reusable agent skills.
- cmux restores app snapshots and native agent session IDs, while arbitrary process checkpointing is explicitly excluded.
- cmux restricts automatic execution of imported resume commands.
- cmux exposes browser previews and screenshots and also supplies a typed Git diff viewer for proposed changes, with…
- cmux documents local snapshot and hook-state files and strips sensitive resume environment keys.
- Mac terminal, iOS TestFlight and Linux Browser nightly are distinct clients.
- cmux runs agent CLIs unmodified in its terminal, so each agent's own sign-in, including a subscription login, applies.
- Mac setup uses DMG or Homebrew and the user supplies agent CLIs.
- CLI and socket operations automate workspaces, panes and browser actions.
- The Mac terminal is implemented with Swift/AppKit and libghostty.
- Prompt intake only: the cmux CLI can start an agent on a Cloud machine with a one-shot prompt (cmux vm agent), and…
- Multimodal input only: images pasted into Cloud terminals upload to the machine for Claude Code and Codex, and files…
- cmux persists per-workspace task checklists.
- cmux documents parallel CLI sessions in split terminal workspaces.
- Machine routing only: cmux vm run picks a Cloud machine for a directory and remembers it for 14 days.
- The documented claude-teams command displays Claude-owned team orchestration.
- cmux automation rules match coding-agent and workspace events and execute configured shell/RPC actions without a…
- Notifications identify panes needing attention.
- The sidebar exposes per-workspace context; the fleet fixture was not run.
- The macOS app starts agents quickly in a workspace or through cmux vm agent, keeps layouts and commands as cmux.json…
- Cloud machines use microVMs as their security boundary, not containers on a shared kernel.
- SSH browser panes use remote-network routing.
- Cloud machines cap short commands (cmux vm exec: 30 s default, 5 min maximum) and refuse requests over the plan's…
- Workspace metadata shows branch, PR state, ports and latest notification.
- CodeRouter reports 30-day tokens and an API-equivalent value per Cloud machine, broken down inside a machine by day,…
- Cloud machines draw from a plan-wide vCPU/RAM pool (Team adds 20 vCPU and 40 GB per seat) and over-pool requests are…
- Team members can open the team's shared Cloud machines at the same time, and published machine URLs can be personal,…
- Enterprise documents SSO/SAML.
- The Enterprise plan listing names audit logs for terminal, network and browser activity, while Cloud machines have…
- Attention navigation and embedded browser context are documented.
- On Cloud machines, terminals and processes live in the machine's daemon, keep running when the owner's laptop…
- cmux vm run returns the remote command's exit code, so a test command's result is visible to a script, but cmux…
- The sidebar shows linked GitHub PR metadata.
- The macOS sidebar shows a workspace's linked pull request number and status.
- Client code is GPL-3.0-or-later; named server directories use BUSL-1.1.
- Free macOS app (local agents use your own API keys); paid Cloud VM plans are Plus $15/mo, Pro $50/mo ($480/yr), Max…
- Scenario costs follow flat plan prices on the live pricing page: the macOS app is free with your own model keys, one…
- The Mac terminal is advertised as free; compute and agent costs are separate.
- Self-serve prices are published per account (monthly or yearly) or per Team seat, with machine counts, vCPU/RAM…
Sources
Open the cmux page
CodeLayer / HumanLayerproduct changefreshness recheckresearch correction51 findings · 26 sources
Findings today
- The complete current application repository lists macOS Electron/Tauri shells, web clients, a daemon and CLI.
- HumanLayer integrates Claude Code, Codex, OpenCode and Pi.
- The pricing FAQ explicitly permits existing Claude/Codex subscriptions or API keys.
- The tutorial names macOS, an account, signed-in Claude Code and Git, then creates an inline task/session.
- Product CLI/RPC routes create/list tasks and launch/list sessions; automation run uses a checkout and PAT.
- The current repository includes Claude Code, OpenCode and Pi session plugins and built-in HumanLayer/RPI skills.
- The current pinned monorepo identifies a shared web UI inside macOS Electron and Tauri shells.
- Users create inline tasks with a name/slug; CLI examples expose persistent task IDs and optional ticket fields.
- Guided workflows save research/design/outline/plan artifacts and allow comments and in-place iteration before…
- /hl:orchestrate breaks work into tasks; workflow checkpoints hold design and outline handoffs; Linear states can…
- Repository skills/instructions and shared task documents supply context.
- Release notes document image attachments in task intake.
- Inline persistent task containers group multiple independent sessions, so a ticket in an external tracker is optional.
- The bundled orchestration skill calls product CLI task/session routes with the same durable task IDs shown in the…
- PRD and TDD artifacts persist in task files with approval checkpoints, version comparison and Slack/public-link…
- The vendor states local daemons run many sessions in parallel; the bundled skill launches separate task worktrees.
- Each task picks its coding agent and host; work queued on an offline host waits for its daemon.
- RPI provides named harness-native research/implementation children; a separate bundled orchestration skill…
- User-run CI/cron can invoke automation run with a PAT; schedules, concurrency groups and no-op guards are external…
- Release notes document shared-session queue/interrupt, Pi stop/reply and attention notifications.
- The UI has attention notifications and a task board, with grouped session history and nested subagents under their…
- Oneshot handles small changes; Freeform omits fixed phases, while RPI/PRD provide guided checkpoints.
- Daemons run on the workstation or user-selected VM/server near the code and private services.
- Worktree timing allows task-specific branches/worktrees or direct checkout use.
- Remote-host sessions and task files are accessible across clients; exact reload/recovery behavior was not tested.
- Workspace configuration supplies setup commands and copied local files per repo; remote hosts need checkout, tools…
- Release notes document Claude usage-limit warnings, waiting states and resumption after reset.
- The status reference documents approval, provider-limit and failed/lost states, and daemon supervisor logs.
- Advanced Metrics ranks every task by token spend or cost with six splits including agent and model; per-host Claude…
- External automation workflows can configure concurrency/no-op guards.
- Task sharing gives editors session/file access and reviewers document comments.
- Official integration guides reserve connection setup to organization admins; task-level edit and review access are…
- The product launch reference lists default, accept_edits, auto and bypass permission modes.
- Shared task files/comments remain with related sessions and can be read by later agents.
- Documented diff review includes changed-file navigation, comments and viewed markers, with artifact comments…
- Shared task access allows another editor to add sessions and continue task files/history.
- Task files sync into an artifact view, including text, HTML, images and PDFs, with task/session grouping.
- Guided implementation documents checks/manual review between phases; PR follow-up can respond to CI.
- Workspace setup creates task branches/worktrees; implementation skills commit checked phases.
- The opt-in GitHub PR tab documents merge and auto-merge actions.
- Release notes document session/PR links through a commit ledger; task artifacts retain PR descriptions.
- Per-task diff/artifact comments, PR controls and workflow next actions exist.
- The current application monorepo at the cited revision is Apache-2.0, with separately licensed vendored MIT folders.
- Current core is open source and can be built and run; 0.202.0 adds a reference self-host copy that HumanLayer calls…
- Agents execute on user hosts while events/task artifacts sync through HumanLayer APIs/storage; model traffic can use…
- Public pricing lists Pro at USD 100/user/month with unlimited tasks/sessions and BYO agent subscriptions/API keys;…
- One or two users can fit the advertised free Starter seat allowance if they remain within 200 sessions/month.
- Official notes reach 0.202.0 on November 14, 2026; production and beta environments both run.
- The vendor homepage asserts SOC 2 Type II and Vanta monitoring.
- Starter is an ongoing free plan for up to three members and 200 sessions/month, currently offered during the…
- Pricing is partially specified: per-user monthly Pro price and Starter caps are public; Enterprise is custom, while…
Sources
Open the CodeLayer / HumanLayer page
Archived event links
Something wrong or missing?