Support
Talk to the people who build it.
ForgeOS is early and access is limited, so support is a small team rather than a ticket queue. That means a real answer, and it means we do not staff support overnight — there is no round-the-clock response commitment, and we will not pretend otherwise.
Before you write
Two things answer most questions faster than we can.
The status page
If a capability is not connected on your instance, the product will look like it is failing when it is in fact reporting honestly. Check what is connected.
The goal's own history
Open the goal in Mission Control and read Plan → What has happened so far. It records every state change, failure and reason.
Getting a useful first reply
What to include
None of this is required. It is what turns a two-day exchange into one message.
| Include | Why it helps |
|---|---|
| What you expected, and what happened instead | The single most useful sentence. Everything else is secondary to it. |
| The goal, in your words | Lets us reproduce the situation rather than guess at it. |
| The repository and branch shown on the goal | Identifies the work without you needing any internal identifier. |
| The state the goal is in | Blocked, in review and failed each mean a different investigation. |
| What the status page reports | Distinguishes a fault from a capability that is not connected. |
| Roughly when it happened | Narrows the recorded history to the right window. |
Do not send credentials. Not tokens, not keys, not passwords, not a copy of an environment file. Support never needs them, and we will ask you to rotate anything that arrives by email.
Connecting a repository
You connect a repository yourself.
Sign in, open Connections, and connect GitHub. You then pick which repositories ForgeOS may read from your own list — read-only to begin with. Writing and deploying are separate grants you make later, if you decide to. Every other service on the Connections page connects the same way — a sign-in where one ships, otherwise a key or URL you create in your own account — and you can also just ask in chat: “connect Slack”.
Security and procurement
Reporting a vulnerability, or reviewing us.
Found a vulnerability?
Write to security@medina19.com with enough detail to reproduce it. Please give us a chance to fix it before publishing.
Security review or questionnaire
The privacy and terms drafts are published for review but are not in force and have not been reviewed by a lawyer. Ask, and you will get direct answers from a person. What the drafts are for.