humanlayer/humanlayer

This page introduces an external open-source repository. It is not an HDATF product.

What it does

HumanLayer is an execution product for teams managing coding agents across their own machines. Developers submit tasks and messages, and a host daemon runs Claude Code, Codex, OpenCode or Pi sessions while connecting tasks, plans and reviews to the app. The repository contains a web interface, macOS desktop apps, a CLI, a daemon, an API and shared packages. It separately includes an Electric authentication proxy for syncing Postgres data to clients and plugins for connecting existing sessions. Remote use requires host authentication or a short-lived launch token and a running daemon, not merely CLI installation. Launching the daemon does not create a persistent background service, so restart supervision and credential persistence need separate preparation. Source development requires Bun and Docker, with Rust additionally required for the Tauri app. Self-hosting guides are explicitly still in progress, so public source should not be mistaken for a turnkey production installation.

License

Apache-2.0 Permissive, with a patent grant. Commercial use is allowed; keep the notices and state your changes.

More in this category

• makecindy/cindy
  Cindy is an open-source client for an AI agent that works with local files and signed-in apps. Its desktop app uses Electron and its mobile app uses Expo and React Native; the backend is not included in this repository. Users provide tasks and select execution harnesses such as Claude Code or Codex together with models to obtain results. The README describes switching harnesses while retaining workspace, memory, skills and tools, alongside browser and device control and message or schedule inputs. Models require a separate connection through the official service, existing coding-plan authorization, personal API keys or local models. Skip Sign-In permits local agents but neither enables server-backed capabilities nor connects to a self-hosted server. Source development requires Node.js 22.x, pnpm 10.x and Git LFS, and default endpoints point to the official cloud. The plugin marketplace and team skill sharing are marked as in development rather than complete. Official builds disclose usage analytics, so local execution does not mean that no data ever leaves the device.
• liguobao/ds-harness-remote
  DS Harness Remote is a community plugin and client set for accessing an existing DeepSeek Harness host from another computer, a browser or Android. Prompts and authorized interactions reach the original host, which retains workspaces, tools and session execution; installing it does not move the agent into the phone. Setup requires a compatible Harness installation, the host plugin, account sign-in and device authorization, with the project's hosted coordination service used by default. Connections prefer direct paths and can fall back through TURN or an encrypted WebSocket relay without requiring a public listening port on the host. The documented Noise channel and the inspected client transport bind communication to device identities and connection context, but encryption does not hide routing metadata or protect compromised endpoints. Remote terminals are enabled by default and run with host-user privileges independently of agent approvals, so they require separate review. iOS is a beta and some alternative agent adapters are experimental. The encryption document contains an older no-terminal description that conflicts with the current README, so the enabled release's actual permission surface must be checked.
• shaobeichen/dsh-pocket
  DSH Pocket is a plugin for controlling a computer's running DeepSeek Harness web interface from a phone. A QR address and access password open the same session for submitting tasks, viewing output and handling approvals. An HTTP and WebSocket proxy plus mobile-layout adjustments connect the existing interface rather than running a separate model. It requires DeepSeek Harness and Node 22 or newer, and dsh web must restart after plugin installation. Local-network access is separate from public access, which requires explicitly enabling a cloudflared tunnel. A fixed-domain mode needs a Cloudflare account, domain and tunnel configuration. Default and custom passwords have different rotation behavior, and the inspected settings source defaults local access and local authentication to enabled. Remote control reaches the computer's code-execution capabilities, so exposing a company network needs caution, and desktop advanced mode is documented as unsupported.
• bowenliang123/dsh-context
  dsh-context is a plugin for inspecting what context DeepSeek Harness sends to a model. Users managing long conversations or multiple agents provide session records and the host's token-meter projections as its inputs. Dashboards and a context browser show session composition, request-level changes, compaction events and file activity. The Fleet view displays the current agent, its parents and subagents with their relationships and states. Users add the plugin to a compatible DeepSeek Harness web profile and open its tabs or command; it is not a standalone model service. The package specifies Node 22.19-series or 24 and newer, plus host-version compatibility requirements. Category token estimates are distinguished from provider-reported actual values, and displayed costs are estimates. Configured system-prompt prefixes and suffixes can change behavior from the next model step, so it should not be treated solely as read-only statistics.
• Alpha-Dojo/DojoAgents
  DojoAgents is an AI agent framework for personal-investment research and portfolio review. Questions, holdings and market data lead to tool-assisted analysis and dashboard results. Its README describes workflows using US, Hong Kong and mainland Chinese market data and holdings screenshots. It separates the core loop from a financial Harness; the inspected financial factory assembles tool providers, memory, policies and result presenters. Python 3.11 or newer and model API configuration are required, while source frontend builds need Node 18 or newer and npm 9 or newer. Users can start from the distribution package and configure a provider or custom endpoint in the local dashboard. The financial data backend uses SDK or HTTP connections, so installation does not guarantee current or accessible data. The project identifies research and demonstration use, and should not be interpreted as an automated trading product guaranteeing accuracy or returns.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.