Repository and community

OpenHuman GitHub

OpenHuman's source code, releases, and community live on GitHub. Find the repository, report issues, read the README, and verify your downloads.

OpenHuman GitHub

Practical notes for evaluating a fast-moving open-source AI assistant.

Practical, source-linked OpenHuman guidance

Repository Overview

OpenHuman is an open-source personal AI assistant hosted on GitHub under the GPL-3.0 license. The repository contains the full source code, install scripts, documentation, and issue tracker.

  • Repository: github.com/tinyhumansai/openhuman
  • License: GPL-3.0 閳?free to use, modify, and distribute under the same license.
  • Primary language: TypeScript with Electron for the desktop application.
  • Install scripts: PowerShell for Windows, shell script for macOS and Linux.

Finding the Latest Release

The GitHub releases page is the authoritative source for the latest stable build, changelogs, and checksums.

  • Go to github.com/tinyhumansai/openhuman/releases for the latest version.
  • Each release includes signed binaries for Windows, macOS, and Linux.
  • Pre-release tags indicate beta builds 閳?use stable releases for production use.
  • Download checksums (SHA-256) are published alongside each release for verification.

Reporting Issues

If you encounter bugs, crashes, or unexpected behavior, the GitHub issue tracker is the best place to report them.

  • Search existing issues before filing a new one 閳?many problems are already documented.
  • Include your OS, architecture, app version, and exact error message.
  • Attach relevant log files if the issue involves crashes or connector failures.
  • For security vulnerabilities, check the repository's SECURITY.md for disclosure guidelines.

Reading the README

The GitHub README is the ground truth for install commands, feature lists, and project status. Always verify details there before acting on third-party instructions.

  • README covers install commands for all platforms.
  • Feature list and supported integrations are kept current in the README.
  • Known issues and limitations are documented upfront.
  • Architecture overview helps contributors understand the codebase.