Skip to Content

Getting help

If you can’t resolve your issue with the documentation, here’s where to get help.

Which channel

ChannelUse it forWhere
DiscordSetup and configuration questions β€” usually the fastest routeci.computer/ggΒ 
Support pageA question you want the team to answer directlyci.computer/supportΒ 
Companion Hub issuesReproducible bugs and feature requests in Hub, the CLI, and the desktop app. Attach a screenshot when the problem is visiblegithub.com/companionintelligence/Companion-Hub/issuesΒ 
CI-Marketplace issuesProblems with an app catalog entrygithub.com/companionintelligence/CI-Marketplace/issuesΒ 
CI-Docs issuesAnything wrong or missing on this sitegithub.com/companionintelligence/CI-Docs/issuesΒ 
Pull requestYou already know the fixRunning locally

The Companion Hub repository is public, so its issues page loads for anyone and you need only a GitHub account to open an issue. The CI-Marketplace and CI-Docs repositories are private: their links return a 404 unless your GitHub account has been granted access. Discord and the support page work for everyone.

Before you ask

Having these ready makes it much faster for anyone to help you:

cihub doctor
cihub status
cihub version
cihub app logs <container-name>

Include your OS, whether you’re running the desktop app or headless, and the output of cihub doctor and cihub status. From Settings β†’ Logs, Download full logs saves the Hub’s log as ci-hub-logs.log. Don’t post pairing codes, API keys, or the contents of your env file. Since 0.3.0, Hub replaces known secrets in its own log with [REDACTED], but a log from an earlier release can hold some, so read a log before you post it.

Community

Join the Discord to get help from other Companion Hub users and the development team β€” usually the fastest route for setup and configuration questions.

GitHub issues

For reproducible bugs and feature requests, open an issue:

Contributing

If you know how to fix a bug, start with Running locally to contribute the change.

Last updated on