Add a screen
Let the copilot open a screen of your app, through your own navigation, with one sync.
Your app has a screen users ask for by name: an order, a subscription, a settings page. The screen exists; the copilot should be able to open it.
Let the copilot open the {screen name} screen ({file path}), with {the values it needs, e.g. an order id}.
Type into What changed? under Sync with code, then paste the prompt it gives you. Works in Claude Code, Cursor, Codex, Windsurf, GitHub Copilot and Gemini CLI.
What the agent will do
- Register the screen with
registerRoute, opening it through your app's own router. - Mark every identifying value (an order id, a booking id) as one that must come from an action's result, so the model cannot invent it.
- Declare the screen to the console, so it shows as planned until a build registers it.
How to check it worked
Run a build. The console's Screens page lists it under Registered. On the Test page, ask for it the way a user would ("show me my last order"): the answer ends on a card that opens the screen.
Reference: what it writes
Rendel.registerRoute(
'order_detail',
title: 'Orders › Order',
description: 'One order: its items, delivery and payment.',
params: {'order_id': RendelRouteParam.string(required: true, fromActions: true)},
open: (p) => router.go('/orders/${p['order_id']}'),
);Rendel.registerRoute({
name: "order_detail",
title: "Orders › Order",
description: "One order: its items, delivery and payment.",
params: { order_id: { type: "string", required: true, fromActions: true } },
open: ({ order_id }) => router.push(`/orders/${order_id}`),
});How the sentence becomes one paste: Sync after a change.
Good screens to add
Screens that already have a route or a deep link, and that a user would ask for by name. Skip dialogs, onboarding and sign-in: a screen nobody asks for is noise in the model's choices. An app registers up to 50.
If the copilot answers in words instead
Sharpen the screen's description on the Screens page or in the sentence you give the agent: say when it is the right screen, in your users' words. A screen still listed as Planned means the registerRoute call is not running at startup.
Turning a screen off on the Screens page stops the copilot offering it at once, on every build. How screens work: Screens.
Sync after a change
Your code gained a screen, an API call or a feature. Say what changed in one sentence, paste one prompt, and the agent brings the copilot level with the code.
Connect an endpoint
Let the copilot call one of your API's endpoints, as the signed-in user, with one sync, or with no agent at all.