> ## Documentation Index
> Fetch the complete documentation index at: https://hillock.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Hillock Community: Discord, GitHub, and Getting Help

> Join the Hillock Discord and GitHub for real-time help, bug reports, feature requests, and contributing to local AI memory development.

Hillock has an active developer community on Discord and its full source code on GitHub. Whether you are debugging an ingestion pipeline, proposing a new HDC feature, or just getting started with local neuro-symbolic memory, both channels give you direct access to the maintainer and other engineers building with Hillock.

## Community Channels

<CardGroup cols={2}>
  <Card title="Discord" icon="discord" href="https://discord.gg/BGUPNBcVdp">
    Join the **Hillock Developer Community** for real-time discussion, usage help, architecture questions, and feature requests. The fastest way to get an answer.
  </Card>

  <Card title="GitHub" icon="github" href="https://github.com/roandejager/Hillock">
    Browse the source code, open issues, track releases, and participate in long-form discussions about roadmap and design decisions.
  </Card>
</CardGroup>

## Getting Help

Use the right channel for the right kind of question to get a faster response.

**Discord** is the best place for:

* Usage questions ("how do I configure the HDC threshold?")
* Integration help ("connecting Hillock to Open-WebUI")
* Unexpected behavior you're not sure is a bug
* Architecture and design discussions

**GitHub Issues** are the right place for:

* Confirmed bugs with reproducible steps
* Feature requests you want tracked on the roadmap
* Documentation gaps or inaccuracies

When asking for help — on Discord or GitHub — include the following so the community can respond quickly:

| Field | Example |
| - | - |
| Hillock version | `0.8.0` |
| Python version | `3.11.4` |
| Operating system | `Ubuntu 22.04` / `Windows 11` / `macOS 14` |
| Hardware | CPU model, GPU model and VRAM, or CPU-only flag |
| Error message | Full traceback, not just the last line |
| Steps to reproduce | Minimal code or commands that trigger the issue |

## Reporting Bugs

<Steps>
  <Step title="Check existing GitHub Issues">
    Search [open and closed issues](https://github.com/roandejager/Hillock/issues) before filing a new one. Your bug may already be tracked, and the thread may contain a workaround or a fix that is already merged.
  </Step>

  <Step title="Open a new Issue with full context">
    If it is not already reported, [open a new Issue](https://github.com/roandejager/Hillock/issues/new) and include:

    * **Version** — run `pip show hillock` and paste the output
    * **OS and hardware** — CPU/GPU model, available VRAM, whether you are running CPU-only
    * **Error message** — the full Python traceback
    * **Minimal reproduction steps** — the smallest set of commands or code that reliably triggers the issue

    The more precise your report, the faster it gets triaged.
  </Step>

  <Step title="Security issues: DM on Discord instead">
    If you have found a security vulnerability, **do not open a public GitHub Issue**. Responsible disclosure protects everyone. DM the maintainer directly on Discord or email [contact.roandejager@gmail.com](mailto:contact.roandejager@gmail.com) with details.
  </Step>
</Steps>

## Feature Requests

Have an idea for a new capability — a new data connector, an API endpoint, or a change to the HDC encoding scheme? You have two options:

* **GitHub Discussions** — open a [Discussion](https://github.com/roandejager/Hillock/discussions) for longer-form proposals where others can weigh in and the idea can be refined before becoming an issue
* **Discord** — drop a quick pitch for lighter-weight suggestions and to gauge community interest before writing a full proposal

Feature requests tied to the v1.0 roadmap are tracked in [Issue #1: The Path to v1.0](https://github.com/roandejager/Hillock/issues/1).

## Version Info

The current stable release is **v0.8.0**. Check which version you have installed by running:

```bash theme={null}
pip show hillock
```

You'll see output like:

```
Name: hillock
Version: 0.8.0
Summary: A lightweight, 100% local neuro-symbolic memory engine for AI agents
...
```

<Note>
  Always include your version when asking for help on Discord or filing a GitHub Issue. Many questions are version-specific, and skipping this step slows down triage considerably.
</Note>

## Project Status

Hillock is under **active development** at v0.8.0, with the roadmap toward v1.0 tracked publicly on GitHub. The project welcomes contributions from the community.

To keep the project open-source while preserving the option for commercial dual-licensing, all contributors are required to sign a standard **Contributor License Agreement (CLA)** via `cla-assistant.io` when opening a pull request. The CLA grants the project the rights needed to maintain the dual-license model without restricting your own use of your contribution. See `CONTRIBUTING.md` and `CLA.md` in the repository for the full terms before opening your first PR.

Hillock is an independent research project by [Roan de Jager](https://github.com/roandejager), focused on making local, privacy-first AI memory viable on edge hardware. Sponsorship and commercial licensing directly fund continued open-source development.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.