How to get help, and what never to post publicly

Which channel answers which question, and the one rule that matters more than the rest.

Written By Dustin

Last updated 30 minutes ago

Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.

Start here

Search this help center and the feedback boards first. Most of what arrives has been answered, and reading the answer is faster than waiting for it.

Where to go

A suspected vulnerabilitysecurity@tovio.dev — never a public board.
A bugThe Bugs & rough edges board at feedback.tovio.dev.
A feature requestThe Feature requests board.
Wrong or missing docsThe Docs & quickstart board.
Privacy or data requestsprivacy@tovio.dev.
Conduct concernsconduct@tovio.dev.

The rule about what you send

Never paste repository contents, file paths, diffs, tokens, keys, session strings, or other people's data — on any channel, public or private. Describe the behaviour and include the error code instead. That code identifies the failure precisely without revealing anything about your repository.

If you cannot describe the problem without pasting one of those things, treat it as security-sensitive and use the security address.

Finding the code to quote

A TOVIO error ends with its stable code in square brackets, usually followed by a link to that code's page. It is the last line of the error block, never the first:

[TVO-PERM-001]  https://tovio.dev/errors/TVO-PERM-001

Quote the bracketed code. The one code with no page is TVO-CORE-000, the generic fallback — seeing it is itself worth reporting, because it means a failure reached you without a specific code of its own. If you are scripting, re-run the command with --json and quote the code field — but read the rest of that JSON before you paste any of it, because its context object legitimately contains your paths and your identity.

Three more things that help and reveal nothing:

  • The exit code the command returned. TOVIO uses one per error class rather than one per code, so the number alone tells a maintainer which subsystem failed even when you can share nothing else. The error catalog on the documentation site lists what each class means.
  • The command shape with your own names removed: tovio land, not the lane name.
  • Whether it reproduces on a fresh throwaway repository. tovio quickstart makes one for you.

What to expect

A person reads everything. TOVIO is pre-release and publishes no response-time commitment — we would rather say that than promise something we cannot hold. Posts are held for review before they appear publicly, which is what keeps an accidental disclosure from becoming permanent.