Support

This page covers the ajat support command, how to capture debug logs, how to contact the Climakers support team, and how to submit feature requests.

The support command


ajat support [flags]

Generates a diagnostic bundle for sharing with the support team.

The support command collects system information, effective configuration, diagnostic checks, environment variables, and recent log output into a single file. Jira usernames, API tokens, and other secret-like values in configuration and environment variables are automatically masked, so the bundle is safe to share. Log file contents are included as-is, so review them briefly before sharing if you have custom logging that may capture sensitive data.

Flags

Flag	Short	Default	Description
`--output`	`-o`	stdout	Write bundle to a file instead of stdout
`--log-file`	`-l`	from config	Path to a log file to include in the bundle
`--log-lines`		`50`	Number of recent log lines to include
`--output-dir`		`—`	Output directory to test for write permissions

Bundle contents

The support bundle includes the following sections:

Section	Contents
System	App name, version, Go version, OS/arch, git commit, build date
Configuration	Config file path, Jira domain and type, API token (masked), HTTP retry and timeout settings, log level, log format, log file path
Diagnostics	The same checks as `doctor`: configuration file, Jira credentials, API connectivity, license file, machine ID, version
Environment	Only `AJAT_*` environment variables, with token and secret values redacted. If none are set, the section reports that explicitly
Recent log	The last N lines from the selected log file. If no log file is configured, the section tells you how to enable one

Jira usernames, API tokens, license IDs, and machine IDs are automatically masked in the bundle. Only the first and last few characters are visible, so support can identify a credential without seeing its full value.

Examples


# Print the support bundle to stdout
ajat support
 
# Save the bundle to a file
ajat support --output support-bundle.txt
 
# Include a log file with more context
ajat support --log-file ./ajat.log --log-lines 200

Capturing debug logs first

By default ajat does not write a log file — structured log events are discarded. For failures that need deeper context, re-run the failing command with debug logging and a log file first, then include that log in the bundle:


# 1. Reproduce the issue with debug logging and a log file
ajat --debug --log-file ./ajat.log export --output-dir ./jira-automations-backup
 
# 2. Generate the support bundle with that log attached
ajat support --log-file ./ajat.log --output support-bundle.txt

Special log-file values stdout and stderr send logs to those streams instead of a file. Use --log-format json when you need structured logs for a regulated review trail.

The bundle already includes system info, configuration context, doctor-style checks, environment variables with secrets masked, and recent log lines. It is usually the fastest way to give support enough context without a long email thread.

Why teams use the support command

Collect all diagnostic context in one step when opening a support case
Share configuration and environment details safely without exposing API tokens or credentials
Include debug log output alongside system and configuration information for faster resolution

Escalation order

When something fails, work through these steps in order before escalating. Each step either resolves the issue or gathers the context the next step needs:

ajat doctor — validate configuration, license, credentials, and basic API access.
Troubleshooting — check the common license, auth, rate-limit, report, and logging issues in the product manual before opening a case.
Debug logs — reproduce with ajat --debug --log-file ./ajat.log <command> to capture structured logs of the failure.
Support bundle — run ajat support --log-file ./ajat.log --output support-bundle.txt and attach it when you contact Climakers.

This keeps diagnosis, reproduction, and evidence-gathering tied together instead of sending an under-specified report that needs several rounds of clarification.

Contacting support

For technical support, bug reports, or feature requests, contact us at support@climakers.com.

Never send secrets or sensitive content. Do not share API tokens, passwords, session cookies, license keys, private automation rule content, exported JSON, inventory reports, or any material you are not authorized to disclose. Redact domains, IDs, rule names, webhook URLs, file paths, screenshots, and command arguments when needed.

When to contact support

Installation, activation, or validation fails
doctor reports a configuration, machine, or connectivity problem
A command returns an unexpected error or exits with the wrong behavior
The output is incomplete, malformed, or inconsistent with the documentation
You need help understanding the safest way to run a mutation workflow
A license needs to be moved, reset, or reviewed

What to include in your email

The product name and version, for example ajat v1.0.0
Your operating system and architecture, for example macOS arm64 or Linux amd64
The exact command you ran, with sensitive values removed
The full error message or unexpected behavior you observed
Whether the issue happens every time or only in a specific case
The output of doctor if it is relevant and already redacted
The generated support bundle when available
Any recent change that may matter, such as a new machine, new token, proxy change, or new license activation

Before you email

Run ajat doctor to check your configuration.
Confirm the installed version with ajat version.
Reproduce the issue with the smallest safe command you can share, using --debug --log-file ./ajat.log.
Generate a support bundle with ajat support --log-file ./ajat.log --output support-bundle.txt.
Redact secrets, private URLs, and confidential content.

Example support request


Subject: ajat v1.0.0 - export stalls with repeated 429s on macOS arm64

Product: ajat v1.0.0
Platform: macOS 15, arm64
Command: ajat export --output-dir ./jira-automations-backup --workers 16
Observed issue: export pauses repeatedly on Retry-After and throughput plateaus
Reproducible: yes, on this tenant
Sanitized output: <paste redacted error here>
Recent changes: none
Attachment: support-bundle.txt (generated with ajat support --log-file ./ajat.log)

Feature requests

Use the same support@climakers.com address when you want to request a new capability.

When to send a feature request

The current command set does not cover a real workflow you need
An existing flag or output format blocks automation or governance work
A repeated manual workaround should become a supported product capability
You need compatibility with another platform, system, or operating model

How to request a feature

Use a clear subject line, for example Feature Request: ajat report export summary.
State the product name and version you are using today.
Describe the workflow or governance problem, not only the desired flag or option.
Explain what you do now as a workaround and why it is insufficient.
Include a small sanitized example of the input, output, or command flow when useful.

Response expectations

Climakers support reviews incoming requests and replies as soon as possible. Clear reproduction steps, sanitized command output, and precise product/version details reduce back-and-forth and usually lead to a faster answer.

License for activation, validation, and machine-bound license files.
Q&A for common questions and quick fixes.