Support
Talk to the people who build it.
Ask from your workspace. The reply shows in your workspace’s support thread. Where this ForgeOS can send email you get an email too, and the confirmation you see on sending says which. Every workspace today is on the free plan: usually within 3 business days, best effort. A Pro plan, which does not exist to buy yet, would be within 1 business day. There is no round-the-clock response commitment.
Try these first
The status page
Something not connected can look broken. See what’s connected.
The goal’s history
Open the goal and read what happened so far. Every step and reason is there.
What to send
Use “Report a problem” in your workspace (left menu in the chat). Say what you expected and what happened. It adds the rest for you, with keys removed, and shows you before sending.
Writing another way?
| Include | Why |
|---|---|
| What you expected, and what happened | The most useful line. |
| What you asked for | So we can repeat it. |
| The chat or project name | So we find it. |
| What the chat said last | Each state means a different fix. |
| About when | So we look at the right time. |
Do not send credentials. We never need them.
Connecting GitHub
Sign in, open Connections, connect GitHub, and pick repos. It starts read-only. Writing and deploying are separate yeses.
GitHub says “not available”?
It uses the ForgeOS GitHub app that we register, so there’s nothing for you to set up. If it’s missing, the fault is on our side — tell us (open support). Signing up with GitHub is a separate thing; the sign-up page says if it’s offered.
Security
Found a bug?
Email security@medina19.com with steps. Please let us fix it before you publish.
Security review
The privacy policy and terms are dated 2 September 2026 and have not been reviewed by a lawyer. The terms are a draft awaiting the company’s details. Ask, and a person answers. More.