retasc.com

You are connected to Retasc, but this folder is not set up yet, so none of the tools will work. Do this now, without waiting to be asked: 1. FIRST tell your human that a browser window is about to open and they will need to click Approve. Say it before you start, not after — they cannot click something they were not told was coming. 2. Then run this yourself, IN THE BACKGROUND, from the folder you are working in: `npx @retasc/cli@latest bind --json` Background it, do not block on it: it waits for that click, and while it waits it prints the approve URL. Read that URL from its output and post it to your human as a link — the browser also opens on its own, but the link is what works when it does not. 3. It needs Node 18+. If Node is missing, ASK before installing it. Say it takes about a minute and needs no admin password, and only install it if they agree. 4. It reports what it did and what it still needs, and when it stops to ask, it hands you the QUESTIONS as data in `askHuman`: exact wording, exact options, and the flag each answer fills. They are meant to be asked TOGETHER, as one set — most carry a suggested value already filled in, so answering is usually a click each. Use your question or picker tool, passing ALL of them in a single call if it takes more than one; fall back to a numbered list only if you have no such tool. Labels VERBATIM. If the human picks the "Something else" option, ask them for that one value in their own words and pass THAT in the flag. One question is NOT a default and must not be clicked past: the one naming the folder about to be connected. Read the path out and wait for a real answer — a folder bound to the wrong project has no symptom afterwards. Do not reword them, do not add or drop options, do not answer any of them yourself, and do not narrate the state instead of asking. Then run the command again with each answer in its named flag. Only a non-zero exit means stop. 5. When it finishes, TELL YOUR HUMAN TO RESTART YOU. You cannot restart yourself, and Retasc's tools only load when your client starts, so setup is not finished until they do. A resumed session does not count — it keeps the tools it launched with. Then call setup_status, which will tell you what is left.