Get help
Payment or account problems
Section titled “Payment or account problems”Email support@commandchain.ai about payments, your plan, or signing in to your account. A person reads every message. Send it from the email address you sign in with, so support can find your account.
When you are signed in, you can also write from the app: open Contact support from the account menu, or use the link at the bottom of the Plan page. Plans and billing are explained in Plans and billing.
Problems with the app
Section titled “Problems with the app”Check Troubleshooting first. If your problem is not there, open an issue in CommandChain’s public GitHub repository for the CommandChain app. You need a free GitHub account to post.
https://github.com/commandchain-ai/commandchain-runner-dist/issuesWhat to include
Section titled “What to include”- The output of
commandchain-runner version. - Your operating system and its version, and whether the computer is Intel, Apple Silicon, x64 or ARM64.
- The agent you used and its version.
- The time the problem happened, with your time zone.
- The address of the session in your browser, if the problem is in a session.
- A debug log, with secrets removed (see below).
Before you post a log, read it and remove anything you would not share publicly, such as tokens, keys, file paths or project names.
Capture a debug log
Section titled “Capture a debug log”-
Stop the background app on that computer:
Terminal window launchctl kill SIGTERM gui/$(id -u)/ai.commandchain.runnerTerminal window systemctl --user stop commandchain-runnerReplace
<task>withCommandChain-followed by your Windows user name. The restart command thatcommandchain-runner statusprints shows the exact name.Terminal window Disable-ScheduledTask -TaskName '<task>' | Out-Null; Stop-ScheduledTask -TaskName '<task>' -
Run CommandChain in a terminal with debug logging, then reproduce the problem:
Terminal window LOG_LEVEL=debug commandchain-runner sessions-connectTerminal window LOG_LEVEL=debug commandchain-runner sessions-connectTerminal window $env:LOG_LEVEL = 'debug'; commandchain-runner sessions-connect -
Press Ctrl-C to stop it, and copy the output.
-
Run
commandchain-runnerto start the background app again.
If the problem happened in the background app and you cannot reproduce it, attach the end of its log file instead:
- macOS:
~/Library/Logs/commandchain-runner/runner.log - Linux:
~/.local/state/commandchain-runner/runner.log, or$XDG_STATE_HOME/commandchain-runner/runner.logif you setXDG_STATE_HOME - Windows:
%LOCALAPPDATA%\CommandChain\logs\commandchain.log
More about stopping, starting and the log is in Keep the CommandChain app running.