Skip to content
Chats and projects

Chats and projects

FORGE is the last category of the Runink TIDE console rail. It has exactly one tab, Studio (forgeStudio). Under the FORGE label, the rail has one row, New chat; the Studio’s header carries a Chats button that opens FORGE’s chat history.

Before you start

  • Use the web console. The studio is a console route that talks to the console’s own gRPC-web endpoint, which only a browser build reaches. Any other build of the console shows “The FORGE studio opens in TIDE’s web console” and does not draw an empty pane.
  • Sign in to TIDE. Every FORGE call needs a TIDE session, even on a console that runs with sign-in disabled. FORGE acts as a named person on GitHub, so it needs a signed-in email. There is no separate FORGE sign-in.
  • Nothing to deploy. FORGE runs inside the TIDE console, so there is no FORGE service, namespace or key to wire. What can be missing is a capability: GitHub writes need FORGE_OWNER_EMAIL to name you, repositories need the console’s GitHub App credentials, and planning needs the model router. The Studio says which, above the canvas. See Troubleshooting.

One chat = one project

A FORGE chat is a project. A project is one repository, and each component is a lane: a folder that is either a RIVER pipeline or a web app. The lanes are declared in forge.yaml at the repository root.

The rail and the Studio header give you:

  1. New chat. This opens the studio on a new, empty chat (?chat=new).
  2. Chats (the button in the Studio header). It opens a list of the recent chats, newest first, each with a title and an age, plus a Show all control. The row tooltip reads “Project <name>” or “Not created yet”, then the lane count when FORGE sent one, then “App made before chats” for a repository FORGE imported as a one-lane chat.

The list is FORGE’s data, kept in FORGE’s own sealed store. The console reads it with runink.ui.chat.v1.ChatService/ListChats over its own gRPC-web endpoint, on your TIDE session.

The list has three distinct states, and each draws differently:

StateWhat you see
Still readingA loading state
FORGE unreadableThe reason, and a retry
Read, no chatsAn empty list. Start with New chat

Open the studio

Choose a chat

Click New chat, or open Chats and click a recent chat. The console hands the studio a new ?chat= value, and the studio opens that chat.

Read the header

Above the canvas, the page header names what FORGE is showing:

  • For a chat that belongs to a project: the chat title, then “Project <name> · one repo, a folder per lane”.
  • For a new chat, or one with no project yet: “Nothing is created until you approve it in the console.”
  • While FORGE has not yet reported which chat it opened: “Opening the chat…”.

The header follows the chat the canvas says it shows.

Work in FORGE

Everything inside the canvas is FORGE. It carries no menu of its own: FORGE’s options live in TIDE’s rail. TIDE’s code states that nothing is created until you approve it in FORGE’s console. How FORGE proposes and applies steps is FORGE’s own behaviour and is not described here.

Rename or delete a project

Both are in the project’s ⋮ menu.

  • Rename the project changes the display name in TIDE only. Once the repository exists it keeps its name, so clones, links and the core/ci statuses keep working; the dialog says so. Before the repository exists, naming the project still sets the repository name. Titles are capped at 120 characters.
  • Delete application (also offered from the recent chats in Chats) first shows what would go, then asks you to type the application’s name exactly. A draft has no repository, so deleting it touches no repository. An approved project’s repository is deleted only when FORGE_OWNER_EMAIL names you and the repository is provably FORGE’s own. Only a session admin may delete another person’s application. Each step is written to the audit chain and shown live.

Deep links

You can link straight to a chat:

/?tab=forgeStudio&chat=<id>
/?tab=forgeStudio&chat=new

A chat id must match FORGE’s shape, c- followed by 16 hex digits or repo-<app name>. Anything else is dropped. The old tab names forgeApps and forgePipelines are retired, and both redirect to forgeStudio.

The studio link itself takes more parameters: ?chat=, ?panel=, the legacy ?app= and ?cmd=. They are listed in the API Reference.

What happens after a brief is filed

FORGE files a brief as a forge-labelled issue in the forged repository. TIDE consumes that queue with the forger:

  • It runs on the schedule 51 3,7,11,23 * * * (four times a day, outside US Eastern business hours) or by workflow_dispatch. It takes the oldest open forge issue in the org, relabels it forge:running, and runs tide session start --repo <owner/name> --issue <n> against it.
  • If a PR comes out, the issue gets forge:done and a comment linking the draft PR. If not, it gets forge:failed and a comment saying why. A failed issue is not retried automatically: re-add the forge label to requeue it.
  • The session verifies at TIDE_SESSION_VERIFY=build. It rises to test only when a live bubblewrap probe passes on the runner, and the comment says which tier ran.
  • The forger never merges, deploys or touches main, and handles one issue per run.
The forger is disarmed by default. The console roster lists it with Enabled: false. To arm it, set the Actions variable TIDE_FORGE_ENABLED=true, or use the forger’s control among the console’s agent controls. A disarmed run reads nothing and writes nothing, and its step summary says “Forger is DISARMED”. See Agent fleet.

Every push to a forged repository is then verified centrally. See Central verification.