Getting help

Three places, in this order:

  1. The documentation, at docs.cahut.cloud: installing, connecting an AI, the concepts, administration, and the reference of every operation and command.
  2. The Discussions, in Q&A: ask there. Other users answer, and the maintainer passes by once a week.
  3. An issue, for a bug you can reproduce, with the bug report form.

There is no support by e-mail or by private message, and no guaranteed response time. Cahut is maintained by one person, in about one slot a week. The only private addresses are security@cahut.cloud for vulnerabilities (SECURITY.md), conduct@cahut.cloud for the code of conduct, and contact@cahut.cloud for the name and partnerships (TRADEMARK.md). None of them does support.

Asking well

Give:

  • the version, from cahut version;
  • the system: AlmaLinux or Ubuntu, and its version;
  • how Cahut was installed: install.sh, a release archive, or make dev on your machine;
  • the AI client you connect with, if it plays a part;
  • what you expected, and what happened;
  • the lines of the Logbook that go with it, from cahut logbook, without any token or password.

What to expect

Every new issue gets an answer within a week: confirmed, needs details, duplicate, out of scope, or accepted and placed in a milestone. That is not a promise of a fix. An issue waiting for details for thirty days is closed, and reopens with a comment. A confirmed bug is never closed for inactivity.

Paid support for organizations may come after version 1.0. It will never come at the expense of the public answers.