wirldocs

Setup prompt

Copy 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.

Help me get started with wirl (https://wirl.dev), where my team's internal tools live. Install the wirl CLI, sign me in, and deploy a starter app as fast as possible. Then tell me the app's address and what it can do.

wirl hosts the apps a coding agent builds for a team: each one gets an address, company sign-in, a database and schedules. The starter is a small team noticeboard that shows what wirl does. Everything you need is below, so you need not read any docs first. Follow the steps in order.

  1. How to work. Show me each command you run and what it prints. If you have wirl tools connected, such as wirl_deploy, don't use them for this setup: use the commands below, since those tools may make the app open to my whole organisation rather than private to me. Don't open a browser to try the app. Never print, read or copy a wirl token, or the file ~/.config/wirl/credentials.json, and never put one in a message, a file or a log. Never type, enter or approve the sign-in code yourself: I approve it in my browser. Leave who can open the app as it is. If you can't run commands here, say so, and tell me to paste this into a coding agent that can (Claude Code, Codex or Cursor), or to run the commands myself in a terminal.

  2. Check Node. Run node --version. wirl needs Node 22.13 or later. If Node is missing or older, tell me, and ask before you install it; use a version manager I already have (nvm, fnm or volta) if there is one. Carry on once node --version shows 22.13 or later.

  3. Sign in. Run npx -y wirl@latest whoami. If it prints a scope line and then my organisations, one per line, I'm signed in already: go to step 4. If it says "Not signed in.", sign me in: npx -y wirl@latest login prints a link and a code, waits while I approve them in my browser, and then saves the sign-in on this computer. Run it where you can read its first lines while it waits (in the background, if your shell tool returns only when a command ends). Show me the link and the code as soon as they appear, then wait until it prints "Signed in". The code expires after 10 minutes: if it does, or the sign-in fails, run npx -y wirl@latest login again and show me the new link and code. Once I'm signed in, if npx -y wirl@latest whoami lists more than one organisation, ask me which, and pass --org <slug> to the apps, pull, init and deploy commands below.

  4. Make the starter. Work in the folder you were started in. If that folder is already a project (it has a package.json or .git), ask me which folder to use before you make anything. Never write outside the folder you were started in unless you say so and I say yes. Then look for a starter an earlier run made:

    • If a folder here whose name ends in -starter has a wirl.json, an earlier run made it: don't make a new app; deploy that folder in step 5.
    • Otherwise run npx -y wirl@latest apps. If it lists an app named starter, or one whose name ends in -starter and begins with my name (the part of my email before the @, which npx -y wirl@latest whoami --json shows), I have a starter already: don't make a new app. Show me its address, and ask me where its folder is, or whether to fetch its files into a new folder here with npx -y wirl@latest pull <app> (<app> is its name); then deploy that folder in step 5.
    • If neither, run npx -y wirl@latest init --starter. It makes a folder named after me, such as dana-starter, with the starter in it, and the app takes the folder's name. Its last line says how to deploy it.

  5. Deploy it. In the starter's folder, run npx -y wirl@latest deploy. It takes about a minute, and prints the app's address and who can open it: a line beginning "Private". If it refuses, show me its sentence. If the sentence says to wait or to try again, do that, once; otherwise ask me what to do.

  6. Set up for later. The starter's folder already has wirl's skill file, .claude/skills/wirl/SKILL.md, which tells a coding agent working there how to use wirl. For another project, npx -y wirl@latest skill in its folder writes the same file, and npx -y wirl@latest skill --print prints it for an agent that keeps its instructions elsewhere. Tell me I can run any of these myself as npx wirl deploy and so on, or install the command once with npm install -g wirl and then run plain wirl deploy.

  7. Tell me what you did, in a few lines:

    • the app's address, as the deploy printed it, and what the app does, in a sentence;
    • that it is private, and who can open it, in the words of the deploy's "Private" line; if the deploy said anything else about who can open it, tell me exactly what it said;
    • the full path of the starter's folder;
    • two or three things I could ask you for next, from "Changes to ask your agent for" in the starter's README.md.