Troubleshooting
Every message below is quoted as FORGE and TIDE show it.
A notice above the Studio canvas
FORGE runs inside the TIDE console, so the Studio is always there; there is no “FORGE is not running” state any more. What can be missing is a capability. The page reads GET /api/forge-studio and shows one notice per missing capability, with the console’s own sentence and a Check again. The canvas stays usable for everything else.
| Notice | Cause | Fix |
|---|---|---|
| GitHub writes are refused | FORGE_OWNER_EMAIL is not set on this console (nobody may), or it does not name you. The sentence says which | Set FORGE_OWNER_EMAIL in the console’s Secret to the comma-separated e-mails (or @domains) allowed to create and change apps, and roll the console. Unset is deliberately nobody, unlike the other admin lists |
| No GitHub App credentials | The console’s GitHub App is not configured | Provide TIDE_GH_APP_ID and TIDE_GH_APP_PRIVATE_KEY to the console (TIDE_GH_APP_* and GITHUB_APP_* are accepted) |
| The planner is unavailable | INFERENCE_REMOTE_URL is unset, or the model router it names does not answer GET /v1/models | Check the model router in inference (DataEx › Agents › Models & inference shows the same endpoint probe) |
The same refusals come back from the RPCs themselves: a GitHub write without the owner list answers PermissionDenied with a sentence naming FORGE_OWNER_EMAIL, and on a console with no sign-in configured every FORGE call is refused, because FORGE acts as a named person.
The chat history shows as unreadable
The chat history comes from FORGE’s chat service in the console itself. An unreadable list shows the reason and a retry. Outside a browser, the console’s gRPC-web channel cannot be built at all, so the list and the Studio are only available in the web console.
core/ci descriptions
“Nothing to verify yet…”
| Description | Cause | Fix |
|---|---|---|
Nothing to verify yet: no .dsl or .herd file and no Go package | A pipeline repository with no pipeline files and no Go package | Write the pipeline. This is a deliberate failure, not a skip |
Nothing to verify yet: <path> does not exist (per lane) | The lane is declared in forge.yaml but its folder is not written yet | Expected for a new lane |
Nothing to verify yet: no .dsl or .herd file and no Go package in <path> | An empty pipeline lane | Add .dsl/.herd files or Go code |
Nothing to verify yet: no go.mod or package.json in <path> | An empty web lane | Add a go.mod or a package.json (in the folder or its web/) |
Nothing to verify yet: no component has code yet (aggregate) | Every lane is empty | As above |
forge.yaml is invalid
core/ci = failure, with no per-lane status. The description is forge.yaml is invalid: <first reason>. Reasons:
the file is empty·not valid YAML: …·more than one YAML documentno version (want version: 1)·version … is not supported (want 1)no lanes·N lanes, more than the 50 TIDE verifieslane N: id "…" must match ^[a-z0-9][a-z0-9-]{0,38}$·lane N: id "…" repeats lane Mlane <id>: kind "…" is not pipeline or web·lane <id>: name is longer than 80 characterslane <id>: path "…" is empty | is absolute | has a trailing / | contains a backslash or NUL | contains a control character | leaves the repository (..) | is not clean (no ./, // or trailing .)lane <id>: path "." is allowed only when there is exactly one lane·lane <id>: path "…" repeats lane M·lane <id>: path "…" is inside lane <id> ("…")forge.yaml is a symlink; it must be a regular file·forge.yaml is not a regular file·forge.yaml is larger than 1 MiB
Failures (the checks ran and said no)
| Description | Where |
|---|---|
N of M pipeline file(s) not valid TOML, first: <file> | pipeline profile or lane |
go vet / build / test -race failed in grpc/ · flutter pub get failed · flutter analyze failed · flutter test failed · flutter build web failed | forge profile |
go build / vet / test failed (or no go.mod at the root) · npm ci failed in web/ (or no web/package.json) · npm run build / lint failed in web/ | web profile |
go build / vet / test failed · pipeline files failed the TOML check | pipeline profile |
go <build|vet|test> failed in <path> · npm <step> failed in <path> · <path>/package.json is not valid JSON · <path> is not a folder · <path> points outside the repository | a forge.yaml lane |
N/M components failed — <id>: <why> | the aggregate |
Open the target_url (the verification run) for the log. The run’s step summary has a per-component table.
Errors (the checks could not run)
| Description | Cause |
|---|---|
TIDE refused or could not read the target (public, not forged, or unreadable) — see the run | The target is public, is neither forge nor tagged forged, or could not be read |
could not check out the commit | Checkout failed |
Go 1.26 is not in the runner toolcache | Runner image problem |
no baked Flutter SDK on the runner (/opt/flutter) | Runner image problem. The workflow deliberately does not download it |
no Node/npm on the runner — the frontend could not be verified (or … the web components could not be verified) | No Node on PATH and none at $HOME/externals/node24/bin |
could not check out … · could not check out TIDE's forgecheck · could not build forgecheck | Token scope or checkout failure |
forgecheck could not read forge.yaml · forgecheck could not read the checkout | forgecheck exited 2 |
verification did not complete (<step>: <outcome>) — cancelled or timed out | Cancelled or timed-out run (45-minute job timeout) |
verification did not complete — cancelled or timed out (per lane) | The lane never recorded a result |
N/M components could not be verified — <id>: <why> | The aggregate over lane errors |
could not aggregate the component results (agg: <outcome>) | The aggregate step did not succeed |
core/ci stays at “queued for TIDE verification”
The sweep claimed the commit and dispatched it, but no run picked it up, or the run died. Nothing to do: a pending status older than 90 minutes is re-dispatched by the next sweep. If the sweep itself fails with N dispatch(es) to … failed — see the warnings, starting the verification failed, and the stale rule retries it.
Commits that are never dispatched: anything in a public repository, fork PRs, archived or disabled repositories, and a repository with no default-branch head yet (an empty repo).
A brief sits in the queue and nothing builds it
The forger is disarmed by default. Its step summary says “Forger is DISARMED” and names who decided (env, console or default). Arm it with the Actions variable TIDE_FORGE_ENABLED=true or the console’s agent control. Outcomes on the issue:
forge:doneand “Forger opened a draft PR: …”forge:failedand “Forger produced nothing for this brief — …”, where the reason is one of: the session never started (the sibling clone or thecoreCLI build failed before it), the session finished but produced no pull request (no changes, or it ran out of turns), or the session exited N. A failed issue is not retried. Re-add theforgelabel to requeue it.