Configuration

human is configured via a .humanconfig.yaml file in your project root. Run human init to create one interactively.

Example

tracker: jira
jira:
  url: https://yourcompany.atlassian.net
  project: KAN
  token_env: JIRA_API_TOKEN
  email: you@example.com

Tracker options

Each tracker has its own configuration block. See the individual connector pages for details.

Credentials

1Password (recommended)

Add a vault section and use 1pw:// references directly in your config:

vault:
  provider: 1password
  account: my-account    # 1Password account name (top-left in app sidebar)

jiras:
  - name: work
    url: https://yourcompany.atlassian.net
    user: you@example.com
    key: 1pw://Development/Jira API Key/token

The 1Password desktop app must be installed and running. It will prompt for biometric or master password authentication. Enable “Integrate with other apps” in 1Password Settings > Developer.

Environment variables

API tokens can also be set via environment variables:

export JIRA_API_TOKEN="your-token-here"

Skills configuration

Skills are installed to your Claude Code configuration via:

human install --agent claude

This writes skill definitions to your project’s .claude/ directory.

Policies

Control what agents can do with declarative rules. See Policies for details.