servotab
Menu

04 / Support

Bring the smallest public-safe evidence.

Use the public issue tracker for reproducible, sanitized reports about method behavior, completeness, documentation, or release packaging.

report / behavior

Describe the mismatch.

Include what you expected, what happened, the relevant Servotab version or commit, and a minimal reproduction when one can be shared safely.

Open a behavior report
report / package

Show the failing package boundary.

Report marketplace discovery, validation, installation, activation, or asset problems with the exact public source ref and sanitized error output.

Open a package report

What to include

Enough context to reproduce. Nothing private by default.

  • Servotab version or commit, if known.
  • Codex surface, operating system, and repository type when relevant.
  • A sanitized version of the original prompt.
  • Expected and observed behavior.
  • Visible method or reference routing, if the client exposes it.
  • Whether the final requested outcome remained complete.
  • The smallest logs, screenshots, or commands needed to support the report.

Public boundary

GitHub Issues are public.

Remove credentials, tokens, private source, personal data, account details, private paths, local notes, and full private Codex transcripts before posting. If the evidence cannot be made public safely, do not put it in an issue.

For a vulnerability or trust-boundary failure that requires private evidence, read the security policy and useGitHub Private Vulnerability Reporting.