Support

This page covers the acp2md support command, how to contact the Climakers support team, and how to submit feature requests.

The support command


acp2md support [flags]

Generates a diagnostic bundle for sharing with the support team.

The support command collects system information, configuration, diagnostic checks, environment variables, and recent log output into a single file. Credentials in configuration and environment variables are automatically masked. 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 log file to include in the bundle
`--log-lines`		`50`	Number of recent log lines to include

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, Confluence 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, Confluence credentials, API connectivity, license file, machine ID, version
Environment	Only `ACP2MD_*` 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

Sample output

Below is the actual output of acp2md support, with sensitive values redacted:


Support Bundle for acp2md
================================

Contact: support@climakers.com

--- System ---
App:                 acp2md
Version:             v1.0.0
Go:                  go1.26.1
OS/Arch:             darwin/arm64
Git Commit:          4d17...ad42
Build Date:          2026-04-03T20:06:22Z

--- Configuration ---
Config File:         /Users/<user>/Library/Application Support/acp2md/config.yaml
Confluence Domain:   <tenant>.atlassian.net
Confluence Type:     cloud
API Token:           AT************************************************************3D
HTTP Max Retries:    7
HTTP Base Timeout:   10ms
HTTP Max Timeout:    100ms
Log Level:           debug
Log Format:          text
Log File:            (not set)

--- Diagnostics ---
  ✅  Configuration file       /Users/<user>/Library/Application Support/acp2md/config.yaml
  ✅  Confluence credentials   <tenant>.atlassian.net (user: <redacted>)
  ✅  Confluence API           connected (258ms)
  ✅  License file             loaded (LO*****61)
  ✅  Machine ID               e2****25
  ✅  Version                  acp2md v1.0.0 (darwin/arm64, built 2026-04-03T20:06:22Z)

--- Environment ---
(no ACP2MD_* environment variables set)

--- Recent Log (last 50 lines) ---
(no log file configured — re-run your command with --debug --log-file app.log)

================================

To get help, email support@climakers.com with subject:
  "acp2md support — <brief description of your issue>"
and include the output above in the email body.

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

Examples


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

Recommended workflow

Reproduce the issue with debug logging first, then generate the bundle:


# 1. Reproduce the issue with debug logging
acp2md page convert by-id 123456 --debug --log-file app.log
 
# 2. Generate the support bundle
acp2md support --log-file app.log --output bundle.txt

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 passwords
Include debug log output alongside system and configuration information for faster resolution

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 customer documents, exported confidential content, or any material you are not authorized to disclose. Redact domains, IDs, page titles, 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 workflow
A license needs to be moved, reset, or reviewed

What to include in your email

The product name and version, for example acp2md 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 acp2md doctor to check your configuration.
Confirm the installed version with acp2md --version.
Generate a support bundle with acp2md support.
Reproduce the issue with the smallest safe command you can share.
Redact secrets, private URLs, and confidential content.

Example support request


Subject: acp2md v1.0.0 - page convert fails on macOS arm64

Product: acp2md v1.0.0
Platform: macOS 15, arm64
Command: acp2md page convert by-id 123456
Observed issue: conversion fails with "unexpected ADF node" error
Reproducible: yes, every time for this specific page
Sanitized output: <paste redacted error here>
Recent changes: none
Attachment: bundle.txt (generated with acp2md support)

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 migration 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: acp2md export summary report.
State the product name and version you are using today.
Describe the workflow or business 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.