acton doctor

Description

Print a diagnostic report for the current Acton environment.

The report is intended to help debug project resolution, manifest parsing, wallet and library overlays, bundled standard-library state, native emulator and Tolk library metadata, logging paths, relevant environment variables, and API reachability from the current machine.

Display Options

--color<when>

Control when to use colored output.

Possible values:

auto, always, never

Default:

auto

Project Options

--manifest-path<path>

Path to the Acton.toml file to use for this invocation.

Use this when running the command outside the project directory or when the manifest lives at a non-default location.

Conflicts with:

--project-root

--project-root<path>

Path to the project root to use for configuration discovery and relative defaults.

Conflicts with:

--manifest-path

Report Sections

acton doctor prints:

version and build metadata
resolved paths for the project, manifest, .acton, cache, wallets, and libraries
Acton.toml existence and parse status
wallet and library overlay load status
bundled stdlib health and version
native emulator/Tolk version metadata, including the TON commit hash and date embedded in the linked libraries
resolved logging directory and debug log path
selected environment variables such as HOME, SHELL, NO_COLOR, and ACTON_DISABLE_AUTO_STDLIB
ACTON_USE_PROXY, which opts Acton CLI HTTP clients into HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and system proxy settings. Acton ignores those proxy settings by default to avoid macOS sandbox proxy autodetection crashes.
API reachability checks for the default TON API backends and verifier backend config endpoint.

Path And Overlay Checks

For each reported path, Acton shows whether it exists, whether it appears writable, and when relevant which resolution source selected it.

Overlay inspection includes:

whether local and global overlay files parse correctly
how many entries they contain
a merged entry count when both layers load successfully

Stdlib Health

The stdlib section reports whether .acton/tolk-stdlib is:

missing
incomplete
healthy
outdated
unknown-version

API Reachability

After the local environment report, acton doctor probes the default remote services Acton commonly uses:

TonCenter v2 and v3 for mainnet and testnet
TonHub v4 for mainnet and testnet
DTON GraphQL
the verifier backend configuration file

The command prints a healthy/total count and per-endpoint status. These checks use short timeouts and are diagnostic only: failed API probes are reported in the output but do not by themselves make acton doctor exit with status 1.

Set DTON_API_KEY to use your own DTON key. For controlled environments, ACTON_DOCTOR_API_TARGETS_JSON can replace the default probe list with a JSON array of targets.

Exit Status

0: The diagnostic report was produced successfully.
1: Environment inspection failed before the report could be completed, for example because path resolution or manifest loading failed unexpectedly.

Examples

Show diagnostics for the current project:
```
acton doctor
```

Inspect another project root explicitly:

acton --project-root ../my-project doctor

Capture environment details before filing a bug:
```
acton doctor
```