Repository navigation
Troubleshooting
Use this checklist to collect useful diagnostic information while minimizing exposure of private data.
axiom version
python --version
axiom --helpIf multiple Python environments are installed, make sure the shell is invoking the axiom executable you intended. Confirm ~/.local/bin is on PATH when using the user-scoped installer.
axiom doctor
axiom doctor --json
axiom status --jsonReview workspace selection, axiom.yaml parsing, filesystem permissions, free disk space, Python compatibility, and missing imports. The checks are read-only and do not repair the project automatically.
- Start the Control Center using
axiom guifrom the intended project directory. - Try
axiom gui --no-openif you need to copy the local URL yourself. - For a daemon issue, start it separately with
axiom daemon --host 127.0.0.1 --port 0and inspect the printed address and logs. - Capture any request/correlation identifier shown by the GUI or API response.
- Do not expose the daemon beyond loopback unless you have consciously evaluated the network/security consequences.
axiom support-bundle --output ./axiom-support-bundle.zipOpen the ZIP before sharing it. The intended archive is limited to diagnostic/environment JSON and a static readme, but metadata minimization is not the same as a guarantee of anonymity in every context.
Include:
- AXIOM version and operating system;
- Python version and installation method;
- the exact command or Control Center path;
- expected versus actual behavior;
- the smallest safe reproducer;
- sanitized diagnostic check IDs or request ID, when available.
Do not include credentials, API keys, passwords, private dataset rows, proprietary model weights, unredacted logs, or a support bundle you have not inspected.
File the report at GitHub Issues. For potential security vulnerabilities, follow the repository's Security page instead of posting sensitive technical details publicly.