Getting help
The docs did not solve it. The assistant is confused. Something is genuinely broken. Here is where to go next.
Canonical URL: /docs/help/getting-help
Ask your assistant first
It can often diagnose itself. It has logs, config, and the last error.
"Why isn't my calendar working?"
"Something went wrong with that last action. What happened?"
"Help me debug this skill."
Also useful: Common issues and FAQ.
GitHub issues
Public bugs and install problems go to github.com/Aevum-Project/cadence-assistant/issues. There is no Discord or community forum yet. There is no support inbox yet.
Source: github.com/Aevum-Project/cadence-assistant.
What to include
| Detail | Why it helps |
|---|---|
| What you were doing | Context |
| What went wrong | Error, missing result, unexpected behavior |
| Exact error text | Not a paraphrase |
| Linux distro | AppImage vs apt paths differ |
| Cadence version | Help → About. Bugs get fixed in later packs. |
| Install path | AppImage vs apt install cadence |
| Skills involved | Narrows the area |
| Steps to reproduce | Lets someone recreate it |
Do not paste API keys, tokens, or workspace secrets into a public issue.
Check for updates
Sometimes the fix already shipped.
On the bundled Linux desktop, use
Help → Check for Updates. That is the supported
path. Do not run cadence upgrade (or
cadence upgrade --latest) on the bundled app. Packed
Linux has no npm runtime, so that command fails.
- AppImage. Help → Check for Updates, or download a new AppImage from the home page. Feed: latest-linux.yml.
-
Deb / apt.
sudo apt install --only-upgrade cadence
Install steps: Installation.