{"article":{"slug":"open-sourcing-humanlayer","title":"Open sourcing HumanLayer","subtitle":null,"summary":"HumanLayer open-sources its core under Apache 2.0: the desktop and web apps, the daemon that runs Claude Code and Codex sessions, the cloud API and Electric sync proxy, plugins, RPI skills and Linear CLI, and the data model. Self-built copies have no telemetry; cloud users see no change for now.","content_type":"announcement","language":"en","canonical_url":"https://www.hlyr.dev/blog/open-sourcing-humanlayer","author":{"name":"Dex","url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"HumanLayer","url":"https://www.humanlayer.com/","listing_slug":"humanlayer","listing":{"slug":"humanlayer","name":"HumanLayer","listing_type":"company","url":"https://listedstartups.com/companies/humanlayer"}},"topics":[{"name":"AI Agents","slug":"ai-agents","url":"https://listedarticles.com/topics/ai-agents"},{"name":"Open Source","slug":"open-source","url":"https://listedarticles.com/topics/open-source"},{"name":"Developer Tools","slug":"developer-tools","url":"https://listedarticles.com/topics/developer-tools"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":498,"reading_minutes":2,"published_at":"2026-10-23T00:00:00.000Z","added_at":"2026-10-24T05:08:58.899Z","updated_at":"2026-10-24T05:08:58.899Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/open-sourcing-humanlayer","markdown_url":"https://listedarticles.com/articles/open-sourcing-humanlayer.md","example":false,"citation":"Dex, HumanLayer. \"Open sourcing HumanLayer.\" 23 Oct 2026. https://www.hlyr.dev/blog/open-sourcing-humanlayer (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://www.hlyr.dev/blog/open-sourcing-humanlayer"},"body_markdown":"# Open sourcing HumanLayer\n\n*Dex · October 23, 2026*\n\nWe've been saying for a few months now that software factories have to be open and composable. Every team we talk to is building their own out of compute, harnesses, and review flows they already have. The last thing great builders want is a black box sitting in the middle of their SDLC.\n\nWe spent [an hour on AI That Works](https://youtu.be/tGbjIvvYuHE?t=1327) on what the parts look like. David Crawshaw made the sharper version of the case in [Devtools must be open source](https://blog.exe.dev/devtools-must-be-open-source): once your agent can read and patch the source of every tool you use, closed source tools become frustrating because you can't fix them, you can't customize them, and you're kind of at the whims of the team building them.\n\nSo today we're open sourcing HumanLayer core: [github.com/humanlayer/humanlayer](https://github.com/humanlayer/humanlayer)\n\n### what's inside\n\nThis is all the same code HumanLayer Cloud runs:\n\n- the desktop app (Electron, plus a Tauri build) and the underlying web app that powers the UI\n- the daemon that runs Claude Code and Codex sessions on your machines, shipped in the `humanlayer` CLI\n- the cloud API, and the Electric proxy that syncs Postgres out to every client\n- the build sources for the public [humanlayer-pi](https://github.com/humanlayer/humanlayer-pi) and [humanlayer-opencode](https://github.com/humanlayer/humanlayer-opencode) plugins\n- the RPI skills and the Linear CLI\n- the data model: orgs, teams, projects, tasks, sessions, plans and comments, diffs, PRs, and the GitHub / Linear / Jira / Slack integrations\n\nEverything is licensed under Apache 2.0. If you build+run it yourself, there's no telemetry at all. Data is only sent if you set keys/DSNs etc.\n\n### for existing users\n\nIf you're a paid or free user of cloud-hosted HumanLayer, nothing changes for now, you can keep using it as you have been.\n\n### running it yourself\n\nIf you want to run the whole stack yourself, you can probably get it up today using the docker compose file. Launch a coding agent and ask it to\n\n```\n```\nwalk me through getting the devstack up and running\n```\n```\n\nWorth noting that right now there are a lot of third party API keys that could be made optional, but are not yet (i.e. processes will refuse to start without them). This is one of the first things we'll be updating, so you don't have to go get keys for WorkOS, Slack, Linear, etc just to use the app.\n\nI'm grateful that we have contributors lined up who are pretty excited to improve this, and in general to make the self-hosting story great. Issues are open if you want to join them. We're looking forward to supporting flexible deployment options to AWS / IAC / Kubernetes / etc soon.\n\n### what's next\n\nBeing open source brings a whole new set of problems we haven't hit yet, from both a maintainer / triage perspective and from a security perspective (especially given events of this week), but we've spent a ton of time hardening the app, and we're confident this is the right way forward.\n\nMore soon. Look forward to building with y'all.\n\nDex and Kyle\n","body_html":"<h1 id=\"open-sourcing-humanlayer\">Open sourcing HumanLayer</h1>\n<p><em>Dex · October 23, 2026</em></p>\n<p>We&#39;ve been saying for a few months now that software factories have to be open and composable. Every team we talk to is building their own out of compute, harnesses, and review flows they already have. The last thing great builders want is a black box sitting in the middle of their SDLC.</p>\n<p>We spent <a href=\"https://youtu.be/tGbjIvvYuHE?t=1327\" rel=\"nofollow ugc noopener\">an hour on AI That Works</a> on what the parts look like. David Crawshaw made the sharper version of the case in <a href=\"https://blog.exe.dev/devtools-must-be-open-source\" rel=\"nofollow ugc noopener\">Devtools must be open source</a>: once your agent can read and patch the source of every tool you use, closed source tools become frustrating because you can&#39;t fix them, you can&#39;t customize them, and you&#39;re kind of at the whims of the team building them.</p>\n<p>So today we&#39;re open sourcing HumanLayer core: <a href=\"https://github.com/humanlayer/humanlayer\" rel=\"nofollow ugc noopener\">github.com/humanlayer/humanlayer</a></p>\n<h3 id=\"what-s-inside\">what&#39;s inside</h3>\n<p>This is all the same code HumanLayer Cloud runs:</p>\n<ul><li>the desktop app (Electron, plus a Tauri build) and the underlying web app that powers the UI</li><li>the daemon that runs Claude Code and Codex sessions on your machines, shipped in the <code>humanlayer</code> CLI</li><li>the cloud API, and the Electric proxy that syncs Postgres out to every client</li><li>the build sources for the public <a href=\"https://github.com/humanlayer/humanlayer-pi\" rel=\"nofollow ugc noopener\">humanlayer-pi</a> and <a href=\"https://github.com/humanlayer/humanlayer-opencode\" rel=\"nofollow ugc noopener\">humanlayer-opencode</a> plugins</li><li>the RPI skills and the Linear CLI</li><li>the data model: orgs, teams, projects, tasks, sessions, plans and comments, diffs, PRs, and the GitHub / Linear / Jira / Slack integrations</li></ul>\n<p>Everything is licensed under Apache 2.0. If you build+run it yourself, there&#39;s no telemetry at all. Data is only sent if you set keys/DSNs etc.</p>\n<h3 id=\"for-existing-users\">for existing users</h3>\n<p>If you&#39;re a paid or free user of cloud-hosted HumanLayer, nothing changes for now, you can keep using it as you have been.</p>\n<h3 id=\"running-it-yourself\">running it yourself</h3>\n<p>If you want to run the whole stack yourself, you can probably get it up today using the docker compose file. Launch a coding agent and ask it to</p>\n<pre><code></code></pre>\n<p>walk me through getting the devstack up and running</p>\n<pre><code></code></pre>\n<p>Worth noting that right now there are a lot of third party API keys that could be made optional, but are not yet (i.e. processes will refuse to start without them). This is one of the first things we&#39;ll be updating, so you don&#39;t have to go get keys for WorkOS, Slack, Linear, etc just to use the app.</p>\n<p>I&#39;m grateful that we have contributors lined up who are pretty excited to improve this, and in general to make the self-hosting story great. Issues are open if you want to join them. We&#39;re looking forward to supporting flexible deployment options to AWS / IAC / Kubernetes / etc soon.</p>\n<h3 id=\"what-s-next\">what&#39;s next</h3>\n<p>Being open source brings a whole new set of problems we haven&#39;t hit yet, from both a maintainer / triage perspective and from a security perspective (especially given events of this week), but we&#39;ve spent a ton of time hardening the app, and we&#39;re confident this is the right way forward.</p>\n<p>More soon. Look forward to building with y&#39;all.</p>\n<p>Dex and Kyle</p>","headings":[{"level":1,"text":"Open sourcing HumanLayer","id":"open-sourcing-humanlayer"},{"level":3,"text":"what's inside","id":"what-s-inside"},{"level":3,"text":"for existing users","id":"for-existing-users"},{"level":3,"text":"running it yourself","id":"running-it-yourself"},{"level":3,"text":"what's next","id":"what-s-next"}]}}