delo run

Get help.

One address, read by the people who build Delo Run. Support comes with every plan.

Where to write.

  • Account and billing

    Write from the address on your account, so the reply can be matched to it.

    support@delorun.com
  • Security reports

    How to report a vulnerability, and what to leave out of testing.

    Security
  • Service status

    Check whether a component is degraded before you write.

    Status
  • The harness itself

    Bugs in DeepSeek Harness go to its GitHub Discussions.

    GitHub

What to include.

  • What you were doing, what you expected, and what happened instead.
  • The chat where it went wrong. Its transcript already holds the commands and their output.
  • If a turn was refused, the sentence Delo Run gave you. Every refusal names its reason.
  • If a Linux machine was involved, whether it was starting, running or just stopped.

What to expect.

A reply from someone who builds Delo Run, often with a question first: reproducing a fault usually needs one more detail.

Faults that lose work, expose another account or make Delo Run unusable come first. Cosmetic problems are fixed in batches.

Current plans come without a service-level agreement or service credits.