02

HOM Code / Help

Start well. Keep your work.

Help with installation, agent identity, updates and recovery.

HOM Code for Mac

The current release is 3.16.2 for Apple silicon Macs running macOS 14 or later. Download it from the HOM Code page and consult the release details before updating.

First installation

Download HOM Code from its product page. Copy the app to Applications, eject the disk image and open HOM Code. This community release is not Apple-notarized. If macOS cannot verify its developer, first confirm that your download came from HOM and matches the published checksum. If you trust that copy, use System Settings, Privacy & Security, then Open Anyway and confirm Open. See Apple's per-app installation guidance. If macOS reports damage or malware, stop and contact HOM; do not bypass that warning.

First onboarding prepares the embedded runtime and private PostgreSQL installation, then presents the passphrase and agent-enrollment flow. Keep your passphrase private. A model provider is configured separately; it is not required to create your native identity.

Open the HOM logo menu and choose Model settings to connect a provider. ChatGPT account login and the model catalog use the provider's normal authorization flow. Later agent enrollment uses the existing agent-management flow without repeating Genesis. Reopening an enrolled installation should reuse it.

When something needs attention

Use Recheck setup on the recovery screen. It checks or resumes the same installation. If it cannot proceed, keep the displayed error and time and contact HOM.

An interrupted operation may already have completed. Let the app reconcile it before retrying. Do not delete a database, reset a profile, re-enroll or use Clear All Data to repair an uncertain operation. A pending save is not evidence that a memory has been retained.

Updates and removing the app

The first release uses manual updates. Install only a version whose release information confirms compatibility with your current installation. Quit normally, replace the application bundle and reopen. Keep the existing profile, native installation and identities.

Removing an app bundle is separate from removing native services, operational data or retained memories. Ordinary quit does not uninstall the native user service. Contact HOM before deleting retained data or removing native services. Installing an older app does not automatically reverse changes to its database.

What the app retains

The app keeps your settings, provider connections and working chat history. The embedded HOM-AIMOS runtime owns cognitive retention and its native identity, authorization, origin and cryptographic evidence. Your original media files stay with the app; the native system retains their accepted references, hashes and origin.

Model providers receive the context needed for inference. Tools and plugins can access files or external services within their configured permissions. Native private signing custody stays with the app/backend owners. Verified hashes and provenance do not independently establish the factual truth of a stored statement.

Report an issue

Contact hello@hom.autos with the app version, macOS version, Mac chip, local time and time zone, the steps you took and the visible error.

Export Logs in the Help menu creates a local diagnostic archive. Inspect it before sharing: it can still contain conversation text, project information and private paths despite redaction. Never send passphrases, private signing keys, API keys, OAuth tokens, complete identity envelopes or a native database. Do not attach raw logs to a public issue.

For a security concern, contact HOM without exploit details or sensitive data and request a private reporting route.

Source and attribution

HOM Code builds on open-source foundations: Apache-2.0 for the retained application source and AGPL-3.0-or-later for the embedded AIMOS-authored source. Third-party components retain their own license terms and attribution.

Get the matching HOM Code source