Skip to main content

​
Diagnose CLI state

fjall doctor takes no arguments and has no subcommands.

​
What Happens

Every in-process CDK synth that runs without an explicit output directory leaves one cdk.out* directory behind in $TMPDIR. Those directories accumulate and can reach several gigabytes on a machine that synthesises often. fjall doctor scans $TMPDIR for directories whose name starts with cdk.out, keeps the ones last modified more than 24 hours ago, and totals their size on disk.

​
Default run (read-only)

The default run deletes nothing. With nothing stale to report:
With stale directories present:

​
Clean-up run

--clean-cdk-tmpdir deletes the directories it finds:
Directories that cannot be removed are counted in the summary rather than failing the command:
When nothing matches the age threshold, the command prints No stale cdk.out* temp dirs found. and exits.
Removal is permanent and recursive. Run --dry-run first if you want to see the list before anything is deleted.

​
Dry-run behaviour

--dry-run applies only alongside --clean-cdk-tmpdir. It prints the count and total size, then exits without deleting:
Add -v, --verbose to list each directory:
-v, --verbose affects the dry-run listing only. The other paths print their summary regardless.

​
Age threshold

--max-age-hours <n> overrides the 24-hour threshold used by --clean-cdk-tmpdir. The read-only diagnostic pass always uses 24 hours, so --max-age-hours on its own changes nothing.

​
Agent mode

fjall doctor is a human-only surface with no machine-readable output. Passing --agent, --fields, --budget or --full returns a validation error and the command does not run. Agent mode detected from the environment does not trigger that refusal, so a bare fjall doctor behaves the same inside an agent session as it does in a terminal.

​
Options

​
Next Steps

fjall validate

Check an application’s infrastructure, including a local CloudFormation synth with --deep --synth.

fjall drift

Detect and repair differences between your definitions and deployed AWS resources.

fjall deploy

Deploy an application to AWS once local state is clean.

fjall login

Sign in to Fjall and store credentials in ~/.fjall/auth.json (or $FJALL_CONFIG_DIR/auth.json).