human - The Dark Software Factory for Claude Code

You have the idea. Claude builds and ships it.

human is an open-source CLI that runs Claude Code inside a secure devcontainer, wired into your tracker, docs, designs, and analytics. One command takes a ticket from idea to shipped code. You review the outcome, not every diff.

What is a dark software factory?

In manufacturing, a dark factory runs with the lights off — the machines don’t need them. In software, it’s the same idea: AI agents write the code, test it against scenarios they’ve never seen, and ship it. No one reviews diffs line by line.

But the lights aren’t off everywhere. Someone still has to define what to build, feed the factory real context, set the policies, and decide when an outcome is good enough. That work stays human.

That’s what human is. It’s the part of the dark factory where people belong:

• Intent in. Tickets, docs, designs, analytics — the real context Claude needs to build the right thing, not just any thing.
• Policy around the line. Secure devcontainer, credential isolation, outbound allowlists, full audit trail. The factory runs, but only inside the fence you drew.
• Review on outcomes, not diffs. Skills for ideation, planning, execution, and review. You approve what shipped, not every line that led there.

Claude runs the line. You stay on intent. The factory handles the rest.

For the full story — origin, five levels, StrongDM example, critiques — read What is a Dark Software Factory?

Install human on macOS, Linux, or with Go

## Brew
brew install stephanschmidt/tap/human

## mise
mise use -g github:StephanSchmidt/human

## Go
go install github.com/stephanschmidt/human@latest

Secure devcontainer for Claude Code

One command sets up a fully secured devcontainer with daemon, Chrome proxy, firewall, and Claude Code integration.

human init
# Configure services, generate devcontainer.json, install Claude Code skills

human daemon start
devcontainer up --workspace-folder .

How human works with Claude Code

human can be used as a standalone CLI with any Coding agent to easily connect to Jira, Linear, Github and other data sources. It is much more powerful when used with a devcontainer, where it connects to an outside human server (same binary) to connect to those data sources, act as a firewall/proxy and lets Claude Code connect to Chrome from inside the container.

Every connector Claude Code needs, included

The factory is engineered, not improvised.

One install gives your AI agent superpowers across your entire toolchain.

Intent in. Outcomes reviewed. The line runs between.
Stop assembling your stack. Start specifying the work.

Replaces these CLIs

Jira CLI · GitHub CLI · GitLab CLI · Linear CLI · ClickUp CLI · Shortcut CLI · Azure DevOps CLI · Notion CLI · Sentry CLI

human CLI usage examples

# List issues (JSON by default)
human jira issues list --project=KAN                 # Jira
human github issues list --project=octocat/hello-world # GitHub
human gitlab issues list --project=mygroup/myproject   # GitLab
human linear issues list --project=ENG                 # Linear
human azuredevops issues list --project=Human          # Azure DevOps
human shortcut issues list --project=MyProject        # Shortcut
human clickup issues list --project=901234567         # ClickUp

# Get a single issue as markdown
human jira issue get KAN-1

# Create an issue
human linear issue create --project=ENG "Implement feature"

# Add a comment
human jira issue comment add KAN-1 "This is done"

# Notion — search workspace, read pages
human notion search "quarterly report"
human notion page get <page-id>

# Figma — browse files, inspect designs
human figma file get <file-key>
human figma file comments <file-key>
human figma file components <file-key>

# Amplitude — product analytics
human amplitude events list
human amplitude cohorts list

# Sentry — error tracking
human sentry issues list --project=your-project
human sentry issue get 12345

Claude Code skills for the full development lifecycle

AI writes code. But who decides what gets built? human’s built-in skills cover the full lifecycle — from challenging the idea through planning, execution, review, and verification. One command (/human-sprint) runs the entire pipeline.

# Included in human init, or run separately:
human install --agent claude

Run Claude Code in a devcontainer

Works everywhere you code.

AI agents inside devcontainers need access to issue trackers, Notion, Figma, Amplitude, and Sentry — but credentials should stay on the host.

human tui
# Starts daemon, shows dashboard with issues and pipeline state

# All commands work transparently
human jira issues list --project=KAN
human notion search "quarterly report"
human figma file get ABC123

Set HUMAN_DAEMON_ADDR and HUMAN_DAEMON_TOKEN in your devcontainer.json — all commands are forwarded to the host daemon. Token-based auth keeps it secure.

HTTPS Proxy — control what AI agents can reach

The daemon includes a transparent HTTPS proxy that filters outbound traffic by domain using SNI inspection — no certificates, no decryption. Configure an allowlist or blocklist in .humanconfig.yaml to control which external services containers can access.

Want a ready-to-use devcontainer with human, proxy, and Chrome Bridge pre-configured? See treehouse.

Chrome Bridge — browse from inside the container

claude --chrome doesn’t work in containers because Chrome runs on the host. The Chrome Bridge tunnels the connection so your AI agent can browse, inspect, and screenshot — transparently.

human chrome-bridge
# Claude Code can now use --chrome inside the container

Why not just use MCP servers?

You can. It’s like building a web app with raw Go libraries in 2004. Or you could use the framework.

¹ Our measurement with ttok (Jira API vs human JSON, 3 small tickets) shows 95% savings (bigger tickets the overhead is less).

Frequently asked questions