Forge bridge
The Forge bridge lets Kanade read configured Forge workspaces, show recent runs,
and start a bounded mission iteration. Browser clients never receive
KANADE_FORGE_BACKEND_AUTH; the daemon proxies the relevant calls.
The bridge surface appears in two places:
/forgelists configured Forge workspaces and recent runs./missions/[slug]shows a Forge runs section for that mission and a guarded launch control.
Launch controls require confirmation because they mutate shared Forge/Kanade work state. A run may create branches, execute agents, and write artifacts under Forge’s control. Kanade’s job is to route the request, show the run state, and bring the result back to the mission record.
Environment contract
Section titled “Environment contract”| Variable | Purpose |
|---|---|
KANADE_FORGE_BACKEND_URL | Forge backend URL, defaulting to the local Forge service. |
KANADE_FORGE_BACKEND_AUTH | Optional backend auth header value, kept server-side. |
KANADE_FORGE_PROJECT | Project slug used for mission bridge requests. |
If Forge is offline, Kanade should keep existing mission data visible and mark launch actions unavailable instead of hiding the bridge.