Help

Support

treg is operated by Superdesign Early access

The short version

Email us: jason@superdesign.dev — for anything at all, including account, billing and security.
Bugs and feature requests: open an issue on GitHub. It is usually the fastest route, and the discussion stays public and searchable.
Security problems: email rather than filing a public issue, so it can be fixed before it is described in the open.
Response time: we aim for two working days. treg is in early access and there is no formal service-level agreement.

01Before you write in

Most questions are answered faster by one of these:

The interactive tutorial — what treg is, and the whole loop end to end.
treg --help, and treg <command> --help for any command.
/llms.txt — the file to point a coding agent at, so it can work out the rest itself.

02Common things

I cannot sign in. treg has three doors: GitHub, Google, and a one-time code sent to your email. If a code does not arrive, check spam for mail from no-reply@treg.superdesign.dev. Signing in for the first time creates the account — there is no separate registration.

A call was refused for funds. Catalog endpoints that treg serves on its own key are metered against your team's prepaid balance. Run treg balance to see it, and treg topup to add more. A new team starts with $1.00 free, and there is a default ceiling of $5 per team per day so a runaway agent cannot spend without limit.

I want my API keys removed. Deleting a tool or a secret in the dashboard removes the stored credential. To delete an entire team and everything in it, use treg org delete <slug>. If you would rather we did it, email us from the address on the account.

Something is charging more than I expected. Every metered call is recorded with what it cost. treg balance shows the ledger. If a price looks wrong, tell us the endpoint id and we will check it against the provider's own rate — the catalog's prices are read from provider rate cards and from what we observe being charged, and both can drift.

Is my data used for anything else? No. Credentials are encrypted at rest and used only to make the calls you or your team ask for. The privacy policy is the full answer.

03Reporting a security issue

Email jason@superdesign.dev with the details and how to reproduce it. Please do not open a public issue first. We will confirm we received it, tell you what we found, and credit you when the fix ships if you would like us to.

04Self-hosted installations

treg is open source, and you can run your own registry with curl -fsSL https://treg.superdesign.dev/selfhost.sh | sh. We are happy to help through GitHub issues, but we have no access to your deployment and cannot see its data — so please include logs and versions rather than asking us to look.

05Contact

Superdesign
Email: jason@superdesign.dev
Issues: github.com/superdesigndev/treg/issues
Service: treg.superdesign.dev