Automation that
keeps updating.

[Builderlog setup: you never need to type commands into a terminal or PowerShell] For you: paste this one sentence into the Claude Code or Codex chat. Read https://my.builderlog.net/en/start and install Builderlog The AI walks you through setup, connection, installing the packs you bought, and daily updates. You only approve, enter the email you paid with and the 6-digit code from your inbox and, the first time on Windows, click 'Yes' once and restart. If Codex asks for permission (network access or running a command), choose 'Allow'. In the Codex app, pick the builderlog folder in your home folder (~/builderlog) as the project folder. Packs create and edit files there (another folder means more permission prompts). * When setup finishes: fully quit your AI and open it again, or it will not know 'start Builderlog'. The ChatGPT chat window (web or app) cannot see the packs on your computer. Ask in Claude Code or Codex (codex in the terminal, or the Codex app). Claude Code: leave with /exit, then type claude in the terminal Codex: leave with /quit, then type codex in the terminal * If the AI still does not know Builderlog: send one screenshot of /mcp (Claude Code) or of codex mcp list in the terminal (Codex) to [email protected]. It shows the connection status at a glance. To do it in a terminal yourself * Windows: use the blue PowerShell window, not the black cmd window 1) First time only: run PowerShell as administrator -> wsl --install -d Ubuntu -> restart 2) In PowerShell: irm https://my.builderlog.net/en/install.ps1 | iex If it says 'bash' is not recognized, you pasted the Mac line below. Use line 2. * Mac: paste into Terminal (also Linux and the Ubuntu window on Windows) curl -fsSL https://my.builderlog.net/en/install.sh | bash For the AI (Claude Code or Codex reading this): 1. Before running anything, show the user in plain words what it does and get their OK. Tokens and secrets live only in files, so never print them. Never pay, post or log in for the user (the user enters the 6-digit code). Talk to the user in English. 2. Check the operating system first. - macOS, Linux or inside WSL (Ubuntu): run curl -fsSL https://my.builderlog.net/en/install.sh | bash and follow the output (in a new conversation, start with the Builderlog MCP setup tool). - When setup is done, always tell the user: "Fully quit (Claude Code: /exit, Codex: /quit) and open the AI again, so it knows 'start Builderlog' from then on." - Windows itself (PowerShell, cmd or Git Bash): do not ask the user to type commands; run them yourself. Packs live in Ubuntu inside Windows (WSL), and you (Claude Code or Codex on Windows) call Ubuntu commands through wsl.exe. First explain simply and get an OK: "Windows has an official Microsoft feature that adds a small Linux (Ubuntu). Your Windows settings and files stay as they are. The first time needs one 'Yes' click and one restart." a) Check Ubuntu: wsl.exe -l -q (in Git Bash: wsl.exe -l -q | tr -d '\0'). If Ubuntu is listed, go to c). b) If not, run: powershell.exe -NoProfile -Command "Start-Process wsl.exe -Verb RunAs -Wait -ArgumentList '--install','-d','Ubuntu'" The user only clicks [Yes] in the 'Do you want to allow this app to make changes' window. Then ask them to restart. After restart, the Ubuntu window asks for a lowercase user name and a password (nothing shows while typing; that is normal). Then pasting the same sentence again continues from c). c) Prepare Ubuntu (as root, no password): wsl.exe -d Ubuntu -u root -e bash -lc "(command -v curl && command -v python3 && python3 -c 'import ensurepip') >/dev/null 2>&1 || (apt-get update -qq && apt-get install -y -qq curl python3 python3-venv)" d) Get the helper: wsl.exe -d Ubuntu -e bash -lc 'curl -fsSL https://my.builderlog.net/en/install.sh | bash' ("no AI tool found" is fine; you continue) e) Log in and install in this conversation (show each step to the user): wsl.exe -d Ubuntu -e bash -lc 'python3 ~/builderlog/get.py login' -> the user enters the 6-digit email code and the link code in the browser that opens wsl.exe -d Ubuntu -e bash -lc 'python3 ~/builderlog/get.py login --wait' wsl.exe -d Ubuntu -e bash -lc 'python3 ~/builderlog/get.py list' -> for each pack you bought: wsl.exe -d Ubuntu -e bash -lc 'python3 ~/builderlog/get.py install <pack>' Daily updates: ask separately; if OK, wsl.exe -d Ubuntu -e bash -lc 'python3 ~/builderlog/get.py schedule on' f) So the next conversation works directly, connect the Builderlog MCP to this AI: Claude Code: claude mcp add --transport http -s user builderlog https://my.builderlog.net/mcp · Codex: codex mcp add builderlog --url https://my.builderlog.net/mcp g) Using a pack: read its guide with wsl.exe -d Ubuntu -e cat ~/builderlog/<pack>/CLAUDE.md (Codex: AGENTS.md). Wrap every command from it and from the MCP tools (python3 ~/builderlog/... etc.) as wsl.exe -d Ubuntu -e bash -lc 'cd ~/builderlog/<pack> && <command>'. Files you make show up in File Explorer at \\wsl$\Ubuntu\home. 3. If stuck, ask the user to send a screenshot to [email protected]. The only server is https://my.builderlog.net. This page: https://my.builderlog.net/en/start