Docs
How to build an app for wirl, deploy it, give it the keys it needs without putting them in the code, and decide who can open it.
Start
For agents: sign in and deployHow a coding agent signs in to wirl, deploys a first app, and what to do when wirl refuses a request.Setup promptCopy everything below into your coding agent (Claude Code, Codex, Cursor or another) and press enter: it installs wirl, signs you in and deploys a starter app.
Build
The contractA wirl app is a static folder, or a static folder plus one backend module.wirl.json and the CLIEverything wirl.json can declare, and every command the wirl CLI has.Connections, keys and tokensA connection is a key or token plus the hosts it may be sent to.SchedulesA schedule is a cron job wirl fires into your app on your behalf.FlowsA flow is work that outlives one request: waiting for a person, trying again tomorrow, a long loop.Public pathsEvery other request to an app requires signing in with Google, and the person's identity arrives as x-wirl-user-id and the rest.PreviewsA preview is a build of your app put up at its own address, open to the same people the app is, before anything goes live.
Run
Sharing and who can open whatA new app's starting visibility depends on the organisation it is deployed to.LogsEverything your server prints with console.log, console.info, console.warn, console.error and console.debug, and every uncaught exception, for every request:…What wirl does not do yetWhat wirl cannot do today, so you find out here and not at your first deploy.