Support
PlatformSmith is in early access, so these docs are a conversation opener rather than a finished artifact. If a page is wrong, unclear, or missing, that is worth telling us — it is the cheapest feedback we get.
Before you write
Two pages answer most questions faster than we can:
- Troubleshooting — the problems people actually hit.
- Known issues — things that are currently wrong, with workarounds.
What to include
For anything involving a launch or a session, these five things turn a three-message exchange into one:
- The workspace and project.
- The environment, and its type — Docker or Kubernetes.
- What you expected, and what happened instead.
- Where it stopped — the launch phase, or the screen.
- Roughly when, including your timezone.
If the problem is a stuck launch, the phase it stopped at is the single most useful fact. → Troubleshooting a launch
Never paste an API key, a workspace token (pst_…), an install code (psic_…) or a session cookie
into a support message. We never need one, and we will never ask for one.
If you think a credential has leaked, rotate it first, then tell us — and remember that rotating does not affect containers already running, so stop those too.
Security reports
If you find a security issue, please report it privately rather than in a public channel, and give us a chance to fix it before it is discussed anywhere else. Describe the problem and how to reproduce it; you do not need to build a working exploit to be taken seriously.
Feedback on the documentation
Tell us what you were trying to do and where the page left you. "I could not tell whether X applied to me" is more useful than "this page is confusing", and it is usually the same observation.