Support

Collect a small, redacted evidence packet when Troubleshooting does not resolve your problem.

Collect diagnostics

Start with the smallest useful set:

coven doctor
coven daemon status

For a session or installation-path problem, add the relevant output:

coven sessions --plain
coven config paths --json

If one recorded session is involved, inspect it without attaching:

coven sessions show <session-id>
coven sessions log <session-id>
coven sessions events <session-id> --limit 100

Replace <session-id> with that session's id. For machine pressure on macOS, add:

coven pc status

Redact before you share

Do not paste any of the following into public issues, chat, or screenshots:

• provider credentials, tokens, cookies, or shell history that contains them;
• full prompt or log content if it includes private code, customer data, or secrets;
• raw session artifacts you do not intend to make public;
• private filesystem paths, repo names, or usernames when a placeholder is enough.

Prefer replacements such as <repo>, <session-id>, <path>, and <redacted>. Review the output before sharing it, including output described as redacted.

Open the right issue

What to include

• the exact command you ran;
• what you expected to happen;
• what happened instead;
• your OS, install route, and whether you use COVEN_HOME;
• the installed Coven version;
• redacted coven doctor output and any session or daemon command output that makes the problem reproducible.

Community routes

• Discord: discord.gg/opencoven
• Troubleshooting page: doctor-first decision tree

For a vulnerability, use a private GitHub Security Advisory or ask the official Discord maintainers for a private security channel. Share vulnerability details only through the private route. An inaccurate documentation claim can use a normal docs issue unless it creates an exploitable condition or exposes sensitive data.