DIN

Docs

Troubleshooting

Start with din doctor: one read-only check of the install, the programs, whether the bin directory is on PATH, the licence, whether the field answers and opens with your token, autostart and the age of the library catalog, each line ok, WARN or FAIL with the command that fixes it. It changes nothing; exit 1 means something FAILed, and din doctor --json gives the same checks to a script. din status has the detail behind each line: it names every program, says whether the field is up and whether your token opens it, and says what to type next (din status --json for a script; exit 0 is usable, 1 is incomplete). Inside Claude Code, /din status does the same for the plugin. din where prints every path and setting and where each came from. Below are the messages you are most likely to meet, what each means and what to do.

Installing

The field

Plans and licences

Dependencies

Still stuck

Write to support@dinctrl.com with din --version, your platform, the exact command and its output, and din status. Never send a field token, an API key or a whole licence key. See Support.