Reference and troubleshooting · How-to guide
Get help
How to reach the people who build ahel, what to include so we can help quickly, and what never to send.
ahel is a small team, and the people who build it answer your mail. There is no ticket system and no live chat. You will usually hear back within a few business days, security reports first.
Before you write
Most setup problems have a fix in Troubleshooting. Check there first, and check the app's status on your Apps page and in Activity.
Where to write
| About | Where |
|---|---|
| Getting started, a bug, a question about your workspace | karl@ahel.ai |
| A security problem you found | karl@ahel.ai, with steps to reproduce if you can |
| Your personal data: a copy, a correction or a deletion | privacy@ahel.ai, answered within 30 days |
The contact page has the same addresses and the company details.
What to include
- Which AI tool you use: Claude, ChatGPT, Cursor, Claude Code, Codex or VS Code.
- Which app, and what you asked your AI to do, in your own words.
- What you saw: the message, the card, or the app's status on your Apps page.
- Roughly when it happened, with your time zone.
- The email address you sign in to ahel with.
If the problem is one call, copy its Link to this run from Activity into your mail. It lets us find that exact call without you pasting its contents.
What never to send
Never send a key, a password, a sign-in code or a token, in mail or in a chat. We do not need them to help you, and a key that was sent anywhere should be replaced in the vendor's settings. If a screenshot shows a key, crop it out first.
Last updated 5 October 2026