Skip to main content
hc
Submit
toolsSource-backed
OpenHands logo

OpenHands

AI-driven software development platform with a local GUI, CLI, Software Agent SDK, agent sandboxes, terminal/browser tools, and hosted cloud options.

by OpenHands · submitted by oktofeesh1·added 2026-06-03·
CLI
HarnessCLI
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/tools/openhands
Source URLs
https://docs.openhands.dev/, https://github.com/OpenHands/OpenHands, https://openhands.dev/
Brand
OpenHands
Brand domain
openhands.dev
Brand asset source
brandfetch
Safety notes
OpenHands agents can edit files, run terminal commands, browse websites, start servers, and interact with repositories, so each workspace needs a clear permission boundary., The documentation recommends Docker sandboxing for local use; process-based execution is faster but has no container isolation and should be treated as unsafe for sensitive projects., Mounts into the sandbox can be modified by the agent when granted write access, so avoid broad host mounts and review exactly which project files are exposed., Confirmation mode and security analyzers can reduce risk by pausing high-risk actions, but they do not prove that an action is correct, reversible, policy-compliant, or safe to merge., Hosted, cloud, enterprise, and integration workflows add additional access-control, audit, retention, budget, and organization-policy requirements beyond the local open-source project., Benchmark performance, agent planning, context compression, and security analysis are useful signals, but human review is still required before generated changes affect protected branches or production systems.
Privacy notes
OpenHands may process prompts, issue text, source snippets, diffs, terminal output, browser context, logs, traces, uploaded files, repository metadata, and generated patches., Model providers, local model routes, OpenHands Cloud, enterprise deployments, or connected gateways may receive task context depending on the selected configuration., Local GUI, CLI, SDK, and sandbox workflows can save conversation history, workspace state, logs, screenshots, browser artifacts, and server output on the machine or managed workspace., Cloud and enterprise integrations with GitHub, GitLab, Bitbucket, Slack, Jira, and Linear should be reviewed for repository access, user identity, issue data, retention, and audit visibility., Operators should define retention and redaction rules before sharing OpenHands conversations, trajectories, screenshots, generated patches, or benchmark artifacts outside the project team.
Author
OpenHands
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-03

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

1 listed

Install type

Copy & paste

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/5 ready
Account & credentials2Install & runtime1Review & approval2

Safety & privacy surface

Safety & privacy surface

6 safety and 5 privacy notes across 6 risk areas. Review closely: permissions & scopes, network access, third-party handling.

6 areas
  • SafetyPermissions & scopesOpenHands agents can edit files, run terminal commands, browse websites, start servers, and interact with repositories, so each workspace needs a clear permission boundary.
  • SafetyExecution & processesThe documentation recommends Docker sandboxing for local use; process-based execution is faster but has no container isolation and should be treated as unsafe for sensitive projects.
  • SafetyPermissions & scopesMounts into the sandbox can be modified by the agent when granted write access, so avoid broad host mounts and review exactly which project files are exposed.
  • SafetyGeneralConfirmation mode and security analyzers can reduce risk by pausing high-risk actions, but they do not prove that an action is correct, reversible, policy-compliant, or safe to merge.
  • SafetyData retentionHosted, cloud, enterprise, and integration workflows add additional access-control, audit, retention, budget, and organization-policy requirements beyond the local open-source project.
  • SafetyGeneralBenchmark performance, agent planning, context compression, and security analysis are useful signals, but human review is still required before generated changes affect protected branches or production systems.
  • PrivacyNetwork accessOpenHands may process prompts, issue text, source snippets, diffs, terminal output, browser context, logs, traces, uploaded files, repository metadata, and generated patches.
  • PrivacyThird-party handlingModel providers, local model routes, OpenHands Cloud, enterprise deployments, or connected gateways may receive task context depending on the selected configuration.
  • PrivacyData retentionLocal GUI, CLI, SDK, and sandbox workflows can save conversation history, workspace state, logs, screenshots, browser artifacts, and server output on the machine or managed workspace.
  • PrivacyData retentionCloud and enterprise integrations with GitHub, GitLab, Bitbucket, Slack, Jira, and Linear should be reviewed for repository access, user identity, issue data, retention, and audit visibility.
  • PrivacyData retentionOperators should define retention and redaction rules before sharing OpenHands conversations, trajectories, screenshots, generated patches, or benchmark artifacts outside the project team.

Disclosure: editorial

Safety notes

  • OpenHands agents can edit files, run terminal commands, browse websites, start servers, and interact with repositories, so each workspace needs a clear permission boundary.
  • The documentation recommends Docker sandboxing for local use; process-based execution is faster but has no container isolation and should be treated as unsafe for sensitive projects.
  • Mounts into the sandbox can be modified by the agent when granted write access, so avoid broad host mounts and review exactly which project files are exposed.
  • Confirmation mode and security analyzers can reduce risk by pausing high-risk actions, but they do not prove that an action is correct, reversible, policy-compliant, or safe to merge.
  • Hosted, cloud, enterprise, and integration workflows add additional access-control, audit, retention, budget, and organization-policy requirements beyond the local open-source project.
  • Benchmark performance, agent planning, context compression, and security analysis are useful signals, but human review is still required before generated changes affect protected branches or production systems.

Privacy notes

  • OpenHands may process prompts, issue text, source snippets, diffs, terminal output, browser context, logs, traces, uploaded files, repository metadata, and generated patches.
  • Model providers, local model routes, OpenHands Cloud, enterprise deployments, or connected gateways may receive task context depending on the selected configuration.
  • Local GUI, CLI, SDK, and sandbox workflows can save conversation history, workspace state, logs, screenshots, browser artifacts, and server output on the machine or managed workspace.
  • Cloud and enterprise integrations with GitHub, GitLab, Bitbucket, Slack, Jira, and Linear should be reviewed for repository access, user identity, issue data, retention, and audit visibility.
  • Operators should define retention and redaction rules before sharing OpenHands conversations, trajectories, screenshots, generated patches, or benchmark artifacts outside the project team.

Prerequisites

  • Supported local system, container setup, or managed workspace for running the OpenHands local GUI, CLI, SDK, or hosted workflow.
  • Docker Desktop, Linux container environment, WSL setup, or remote sandbox plan when using the recommended isolated local execution path.
  • Approved model provider, local model, or hosted model route configured with the organization controls, spend limits, and data handling rules required for the target repository.
  • Git provider access, repository permissions, branch strategy, review ownership, and rollback plan before connecting OpenHands to real issues, pull requests, or production codebases.
  • Policy for browser access, terminal use, mounted workspaces, saved conversations, logs, traces, cloud integrations, and any Slack, Jira, Linear, GitHub, GitLab, or Bitbucket connections.

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Pricing
freemium
Disclosure
editorial
Application category
DeveloperApplication
Operating system
macOS, Windows, Linux
Full copyable content
## Editorial notes

OpenHands is useful when Claude-adjacent teams want an open, full-stack software-development agent environment rather than only an editor extension or a small CLI. It combines a local GUI, CLI, Software Agent SDK, agent server, terminal and browser tools, confirmation mode, sandbox providers, repository workflows, and hosted cloud or enterprise options.

This is distinct from existing entries. Claude Code, Aider, Cline, Roo Code, Continue, Cursor, Windsurf, Replit Agent, Devin, and mini-SWE-agent cover narrower coding-assistant, editor, commercial-agent, or minimal CLI workflows. LangGraph, Agno, Pydantic AI, CrewAI, AutoGen, and DSPy cover general agent-framework or language-model programming patterns. OpenHands sits closer to a software-engineering agent platform with a local GUI, SDK, agent server, sandboxing model, browser and terminal surfaces, and optional hosted collaboration workflows.

## Source notes

- The official README describes OpenHands as an AI-driven development project and lists multiple ways to use it: Software Agent SDK, CLI, local GUI, Cloud, and Enterprise.
- The README says the SDK is a composable Python library that powers the other OpenHands surfaces, and that agents can run locally or at larger cloud scale.
- The README says the CLI is a familiar coding-agent interface, while the local GUI provides a REST API and React application for running agents on a laptop.
- The docs introduction describes Agent Canvas, OpenHands Cloud, OpenHands Enterprise, the Software Agent SDK, legacy CLI and local GUI paths, and integrations such as GitHub, GitLab, Bitbucket, Slack, Jira, and Linear.
- The key-features documentation describes chat, changes, embedded VS Code, terminal, app preview, and browser tabs.
- The confirmation-mode documentation describes Confirmation Mode and Security Analyzers, including high-risk action prompts and analyzer-based risk assessment.
- The sandbox documentation defines sandboxes as the place where OpenHands runs commands, edits files, and starts servers; it lists Docker as the recommended local provider, process execution as unsafe but fast, and remote sandboxing for managed setups.
- The SDK documentation describes Python and REST APIs for agents that work with code, including tools for shell commands, file editing, web browsing, MCP integration, and remote agent-server execution.
- The repository license says content outside `enterprise/` is available under MIT, while the enterprise directory has separate licensing.

## Duplicate check

Checked current `content/tools/`, `content/mcp/`, agents, hooks, rules, skills, commands, guides, open pull requests, live issue state, and repository-wide content for `OpenHands`, `Open Hands`, `OpenDevin`, `opendevin`, `all-hands`, `openhands.dev`, `docs.openhands.dev`, `github.com/OpenHands/OpenHands`, `Software Agent SDK`, `Agent Canvas`, and `CodeActAgent`. Existing Claude Code, Aider, Cline, Roo Code, Continue, Cursor, Windsurf, Replit Agent, Devin, mini-SWE-agent, LangGraph, Agno, Pydantic AI, CrewAI, AutoGen, and DSPy entries are adjacent, but no dedicated OpenHands tools entry, OpenHands source URL duplicate, or open duplicate PR was found.

## Disclosure

Editorial listing. No paid placement or affiliate link is used. OpenHands includes MIT-licensed local/core project code, source-available enterprise code, and hosted commercial options.

About this resource

Editorial notes

OpenHands is useful when Claude-adjacent teams want an open, full-stack software-development agent environment rather than only an editor extension or a small CLI. It combines a local GUI, CLI, Software Agent SDK, agent server, terminal and browser tools, confirmation mode, sandbox providers, repository workflows, and hosted cloud or enterprise options.

This is distinct from existing entries. Claude Code, Aider, Cline, Roo Code, Continue, Cursor, Windsurf, Replit Agent, Devin, and mini-SWE-agent cover narrower coding-assistant, editor, commercial-agent, or minimal CLI workflows. LangGraph, Agno, Pydantic AI, CrewAI, AutoGen, and DSPy cover general agent-framework or language-model programming patterns. OpenHands sits closer to a software-engineering agent platform with a local GUI, SDK, agent server, sandboxing model, browser and terminal surfaces, and optional hosted collaboration workflows.

Source notes

  • The official README describes OpenHands as an AI-driven development project and lists multiple ways to use it: Software Agent SDK, CLI, local GUI, Cloud, and Enterprise.
  • The README says the SDK is a composable Python library that powers the other OpenHands surfaces, and that agents can run locally or at larger cloud scale.
  • The README says the CLI is a familiar coding-agent interface, while the local GUI provides a REST API and React application for running agents on a laptop.
  • The docs introduction describes Agent Canvas, OpenHands Cloud, OpenHands Enterprise, the Software Agent SDK, legacy CLI and local GUI paths, and integrations such as GitHub, GitLab, Bitbucket, Slack, Jira, and Linear.
  • The key-features documentation describes chat, changes, embedded VS Code, terminal, app preview, and browser tabs.
  • The confirmation-mode documentation describes Confirmation Mode and Security Analyzers, including high-risk action prompts and analyzer-based risk assessment.
  • The sandbox documentation defines sandboxes as the place where OpenHands runs commands, edits files, and starts servers; it lists Docker as the recommended local provider, process execution as unsafe but fast, and remote sandboxing for managed setups.
  • The SDK documentation describes Python and REST APIs for agents that work with code, including tools for shell commands, file editing, web browsing, MCP integration, and remote agent-server execution.
  • The repository license says content outside enterprise/ is available under MIT, while the enterprise directory has separate licensing.

Duplicate check

Checked current content/tools/, content/mcp/, agents, hooks, rules, skills, commands, guides, open pull requests, live issue state, and repository-wide content for OpenHands, Open Hands, OpenDevin, opendevin, all-hands, openhands.dev, docs.openhands.dev, github.com/OpenHands/OpenHands, Software Agent SDK, Agent Canvas, and CodeActAgent. Existing Claude Code, Aider, Cline, Roo Code, Continue, Cursor, Windsurf, Replit Agent, Devin, mini-SWE-agent, LangGraph, Agno, Pydantic AI, CrewAI, AutoGen, and DSPy entries are adjacent, but no dedicated OpenHands tools entry, OpenHands source URL duplicate, or open duplicate PR was found.

Disclosure

Editorial listing. No paid placement or affiliate link is used. OpenHands includes MIT-licensed local/core project code, source-available enterprise code, and hosted commercial options.

#coding-agent#developer-tools#open-source

Source citations

Add this badge to your README

Show that OpenHands is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/openhands.svg)](https://heyclau.de/entry/tools/openhands)

How it compares

OpenHands side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field
OpenHands logoOpenHands

AI-driven software development platform with a local GUI, CLI, Software Agent SDK, agent sandboxes, terminal/browser tools, and hosted cloud options.

Open dossier
Open SWE

Open-source framework for building internal coding agents that accept tasks via Slack, Linear, or GitHub, execute code changes in isolated cloud sandboxes, and open draft pull requests automatically.

Open dossier
Agent Island logoAgent Island

Open-source status companion for Claude Code and Codex with live local session state, your-turn alerts, usage views, and native macOS and Windows applications.

Open dossier
Cline logoCline

Open-source autonomous coding agent extension for planning, editing, running commands, and using tools from VS Code.

Open dossier
Next stepsDiffers
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1JPette1783tristan666666—
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety · Privacy ·
BrandOpenHands logoOpenHands—Agent Island logoAgent IslandCline logoCline
Categorytoolstoolstoolstools
SourceSource-backedSource-backedSource-backedSource-backed
AuthorOpenHandsLangChainTristan TangCline
Added2026-06-032026-06-052026-07-152026-04-27
Platforms
CLI
CLI
CodexCLI
CLI
Harness
CLI
CLI
CodexCLI
CLI
Source repo————
Safety notes✓OpenHands agents can edit files, run terminal commands, browse websites, start servers, and interact with repositories, so each workspace needs a clear permission boundary. The documentation recommends Docker sandboxing for local use; process-based execution is faster but has no container isolation and should be treated as unsafe for sensitive projects. Mounts into the sandbox can be modified by the agent when granted write access, so avoid broad host mounts and review exactly which project files are exposed. Confirmation mode and security analyzers can reduce risk by pausing high-risk actions, but they do not prove that an action is correct, reversible, policy-compliant, or safe to merge. Hosted, cloud, enterprise, and integration workflows add additional access-control, audit, retention, budget, and organization-policy requirements beyond the local open-source project. Benchmark performance, agent planning, context compression, and security analysis are useful signals, but human review is still required before generated changes affect protected branches or production systems.✓Each task runs in an isolated cloud Linux sandbox (Modal, Daytona, Runloop, or LangSmith) to prevent production impact. The agent executes shell commands, file operations, web fetches, and HTTP requests inside the sandbox without confirmation prompts — review sandbox provider permissions before deployment. GitHub operations are performed through a GH_TOKEN proxy; scope token permissions to the minimum required repositories. Subagent orchestration can spawn parallel child agents — set appropriate step limits and monitor LangSmith traces to prevent runaway execution. AGENTS.md or CLAUDE.md at the repository root is injected into the system prompt; review this file to control agent behavior and conventions.✓Agent Island reads local Claude Code and Codex session files to determine session state; review the requested filesystem access before use. The macOS release is ad-hoc signed rather than Apple-notarized, so first launch requires right-clicking the app and choosing Open. Windows packages are distributed through GitHub Releases, Scoop, and winget; verify the release source before installation.— missing
Privacy notes✓OpenHands may process prompts, issue text, source snippets, diffs, terminal output, browser context, logs, traces, uploaded files, repository metadata, and generated patches. Model providers, local model routes, OpenHands Cloud, enterprise deployments, or connected gateways may receive task context depending on the selected configuration. Local GUI, CLI, SDK, and sandbox workflows can save conversation history, workspace state, logs, screenshots, browser artifacts, and server output on the machine or managed workspace. Cloud and enterprise integrations with GitHub, GitLab, Bitbucket, Slack, Jira, and Linear should be reviewed for repository access, user identity, issue data, retention, and audit visibility. Operators should define retention and redaction rules before sharing OpenHands conversations, trajectories, screenshots, generated patches, or benchmark artifacts outside the project team.✓Repository code, Linear issue history, and Slack thread history are sent to the configured model provider API. Sandbox providers (Modal, Daytona, Runloop, LangSmith) process task execution data according to their own privacy policies. LangSmith tracing, when enabled, logs full agent traces including tool inputs and outputs — configure retention and access controls in your LangSmith organization. GitHub OAuth tokens and model API keys should be stored as secrets and never committed to the repository.✓Session monitoring is local and the project states that the app has no Agent Island account and no product telemetry. Usage views may call provider usage APIs with existing local credentials; those requests remain subject to the provider's privacy terms. Local transcript files and provider credentials can contain sensitive data and should not be included in public screenshots, issues, or logs.— missing
Prerequisites
  • Supported local system, container setup, or managed workspace for running the OpenHands local GUI, CLI, SDK, or hosted workflow.
  • Docker Desktop, Linux container environment, WSL setup, or remote sandbox plan when using the recommended isolated local execution path.
  • Approved model provider, local model, or hosted model route configured with the organization controls, spend limits, and data handling rules required for the target repository.
  • Git provider access, repository permissions, branch strategy, review ownership, and rollback plan before connecting OpenHands to real issues, pull requests, or production codebases.
  • GitHub account with OAuth access for repository operations.
  • A model API key (Anthropic, OpenAI, or compatible provider).
  • A LangSmith API key when using LangSmith as the sandbox provider.
  • Slack workspace, Linear workspace, or GitHub repository access for the desired trigger integrations.
  • macOS 13 or later, or Windows 10 or later.
  • A local Claude Code or Codex installation with session data available to the current user.
— none listed
Install——
brew install tristan666666/tap/agentisland
—
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Adding Plugin Install Hints to Developer CLIs

Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Agent Skills in Claude Agent SDK Applications

Use Agent Skills in the Claude Agent SDK: filesystem discovery via settingSources, the skills option to enable or filter, and tool access.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Building In-Process MCP Tools with the Claude Agent SDK

Define in-process MCP tools for the Claude Agent SDK with createSdkMcpServer and the tool helper, then wire them into query.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JPette1783

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.