We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
fix(wiki): make wslc PowerShell scripts ANSI-safe and re-runnable Two problems in the Installation-wslc guide's copy-paste PowerShell: - Replace em/en dashes inside the powershell code fences with ASCII hyphens (two Write-Host strings + two comments). Saved to a .ps1 and read as Windows-1252, the UTF-8 dash bytes were mangling output. - Under $ErrorActionPreference = "Stop", native wslc stderr writes are promoted to terminating errors, so a re-run aborted at `wslc network create` ("already exists"), and `container rm` had the same latent bug. Wrap both idempotent calls in try/catch, and route the `run` calls through an Invoke-Wslc helper that tolerates benign stderr (e.g. first-run pull progress) but still fails on a non-zero exit code. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): add stop-foreman-wslc.ps1 to the wslc page Add a stop script alongside the start/update scripts: stops the three containers by default, with a -Remove switch to also delete them. Uses SilentlyContinue so stopping an already-stopped container doesn't error; data on the C:\foreman bind mounts is preserved either way. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): add update-foreman-wslc.ps1 to the wslc page Add a second optional script that pulls the latest published images and recreates the stack against them by reusing start-foreman-wslc.ps1 (which removes the old containers first). Data on the C:\foreman bind mounts is preserved; note that a newer ff-server may run additive DB migrations on next start. Confirmed `wslc image pull` exists via `wslc image --help`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): wslc page — verified, with real expected-output examples Mark the WSL Containers path as tested end-to-end on the preview and add anonymised sample output at the key checkpoints: network list (bridge driver), sf-mcp /health, the ff-server "Connected to MCP server" log line (cross-container name DNS), and container list. Document two preview gaps found while testing: wslc ignores image HEALTHCHECKs (no health column / no State.Health), so verify via /health curls; and add a cmd-vs-PowerShell shell note (backtick continuation is PowerShell-only). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(wiki): split Installation into Docker and WSL Containers (wslc) pages Turn the single Installation page into a landing/chooser page with two children: Installation-Docker (the existing Docker Compose instructions, migrated) and a new Installation-wslc runbook for running the stack under WSL's native `wslc` container runtime without Docker Desktop. The wslc page translates compose.yaml into individual `wslc run` commands on a shared user-defined network (the ff-server->sf-mcp and ff-client->ff-server hops resolve by container name), uses Windows bind mounts for persistence, and flags the preview features it relies on (network DNS, named volumes, restart) with a host-gateway fallback. Nest both under Installation in the sidebar. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Update wiki for the foreman web app + single-producer game-data pipeline - Reframe Home/Installation around the full Docker Compose stack (web app at :8725, backend :8724, MCP :8723), with the standalone MCP server as a secondary path; MCP-client guides move under their own section. - Fix the published MCP image name: foreman-mcp → foreman-sf-mcp. - Configuration: drop the now-dead SATISFACTORY_DOCS_PATH / SATISFACTORY_GAME_DIR (removed when the runtime stopped parsing en-US.json), add SF_GAME_DATA_PATH and the foreman backend vars (ANTHROPIC/LLM_*, DATABASE_URL, BETTER_AUTH_*). - Game data channels: "use your own data" now means a pre-built sf-game-data.json via the offline extractor + SF_GAME_DATA_PATH, not pointing at a raw install. - Troubleshooting: add the web-app health check; fix the stale "raw install" note.
Troubleshooting: add foreman chat section (429/quota, 401, no key, MCP retry) Document provider-side errors and the self-healing first-message MCP reconnect: 429 quota (prepaid billing, separate from subscriptions), 401/invalid key / provider mismatch, missing key, and the "retry on first use" MCP log. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add OpenAI API key guide; group API-key pages in nav New "Getting an OpenAI API key" page: create a key on the OpenAI platform, then use it via the web app Settings (provider = OpenAI-compatible) or the server's LLM_PROVIDER/LLM_API_KEY, with a note that the same path covers OpenRouter, Azure, and Gemini. Group the Anthropic + OpenAI pages under "API keys" in the sidebar and Home, and cross-link the two. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add Anthropic API key guide; link from sidebar and Home New "Getting an Anthropic API key" page: create a key in the Anthropic Console, then use it via the web app Settings or the server's ANTHROPIC_API_KEY, with cost and safety notes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Bootstrap wiki: Claude Desktop setup + doc hierarchy Add the initial wiki structure (Home, sidebar, Installation, Connecting Clients, Configuration, Game Data Channels, Troubleshooting) with full instructions for connecting the MCP server to Claude Desktop. Other LLM client guides are stubbed for later. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>