Skip to main content

Setup reports not configured

Use these steps to determine why aitrax setup check reports system as not configured. Work through them in order. Each step states how to tell whether it was the cause.

  • Deployment: SaaS, On-premises

If setup has never been run on this machine at all, run it first — see Set up your workstation. Use these steps when a completed setup has stopped reporting as configured.

1. Check for setup drift after an update​

An update can leave setup complete but one of its surfaces — the entry points described in How setup works — missing.

aitrax setup reconcile

This does nothing unless setup already completed and a surface is missing, so it is safe to run. Check status again. If system now reports as configured, drift was the cause. If not, continue.

2. Confirm the tracker binary is present​

Setup escalates to a larger build that owns setup and token redemption, downloading it if needed — see How setup works. A blocked download leaves setup unable to complete.

aitrax doctor

If the output reports a missing or unavailable binary, see No tracker binary available.

If this doesn't fix it​

Contact support with all of the following:

  • The complete output of aitrax setup check.
  • The complete output of aitrax doctor.
  • The verbatim setup command you ran, with any token removed, and its output.
  • Your operating system, and the output of aitrax version.
  • Your audit log from ~/.codetogether/aitrax.jsonl.