Support

The contact

All support runs through one address:

support@agenticonsult.de

Email is the only channel, on purpose — diagnostics, Doctor output, and log excerpts travel well in an email thread, and every report stays traceable from first message to fix.

Before you write

Two minutes of self-service resolves a large share of reports:

1. Open Settings ▸ Doctor and run the checks — most breakage shows up as a named row with a fix action attached.
2. Scan the Troubleshooting clusters for your symptom.
3. Check the FAQ — the recurring questions live there, with honest answers.

If those come up empty, write in. A report that stumps the docs is also a signal the docs need fixing, so it is doubly welcome.

One case skips the ladder: if Doctor's account row says your account is no longer active, that is the single state a reconnect can never repair. Check your billing first, then write in — see what a lapse looks like.

What to include

The more of this a first message carries, the faster the answer:

• The app version — shown in Settings; it is also stamped in config/app_version.json inside your install folder if the app will not start.
• Your operating system and whether this is a fresh install, an update, or a machine that has been running for a while.
• Doctor findings — a screenshot of the Doctor view is the fastest thing you can send, and it is what to reach for first: there is no copy-findings button to press. If you would rather type, one line per non-passing row is plenty — the group, the row label, and the exact detail text (for example: "Daemons · Knowledge Base · not running").
• What happened versus what you expected, and the steps to reproduce it if you can.
• What you already tried — which fix actions, which restarts, which troubleshooting steps.
• Log excerpts where relevant — routine job output lands under documents/routine_logs/ in your install, and knowledge-graph provisioning writes arcadedb/local/_provision.log. A few lines around the error beat a whole file.

For anything security-sensitive, use the same address and say so in the subject line.

What to expect

Command Center is built and supported by a very small operation, and the support promise is calibrated to that honestly:

• Every message is read, and the answer is written by the person who builds the product. There is no support tier to escalate through and no canned response standing in for a real one; if an automatic note confirms your mail arrived, the substantive reply still comes from a person.
• A substantive reply typically arrives within one to two business days. Complex issues may take a follow-up round-trip to pin down; you will get a straight answer about what is wrong, whether it will be fixed, and roughly when.
• Bug reports and feature requests go to the same address. Name the view or page involved, and describe the job you were trying to get done — that context shapes fixes more than any wishlist item does.

What support cannot do: debug your Claude subscription or provider accounts (those relationships are yours — see BYO Claude & keys), or recover content that never existed on your machine. Everything the product itself does is fair game.

Company and legal

Command Center is built and published by agenticonsult, Wuppertal, Germany. The company details, the data-protection notice and the terms of sale live on the main site and apply to this documentation too:

• Legal notice — the operator, address and contact details required under §5 DDG
• Privacy policy — what is processed, on what basis, and for how long
• Terms — the terms of sale for the subscription and the one-time products
• Cookie policy

These pages are also linked in the footer of every page here. The German versions are the operative ones; the English versions are translations provided for convenience.