docs(brand): standardize public naming to LoopForge

Author: Rex

docs-site/blog/index.md

@@ -4,13 +4,13 @@ Practical notes for builders choosing an Agent OS and scaling from local prototy
 
 ## Latest posts
 
-- [What Is LoopForge? (Formerly RexOS)](what-is-loopforge.md)
+- [What Is LoopForge? (Formerly LoopForge)](what-is-loopforge.md)
 - [LoopForge vs OpenFang/OpenClaw (Builder View)](rexos-vs-openfang-openclaw.md)
 - [Editorial Calendar](editorial-calendar.md)
 
 ## Suggested reading order
 
-1. Brand + product fit: [What Is LoopForge? (Formerly RexOS)](what-is-loopforge.md)
+1. Brand + product fit: [What Is LoopForge? (Formerly LoopForge)](what-is-loopforge.md)
 2. First successful run: [New User Walkthrough](../tutorials/new-user-walkthrough.md)
 3. Practical templates: [10 Copy/Paste Tasks](../examples/case-tasks/ten-copy-paste-tasks.md)
 4. Positioning and alternatives: [LoopForge vs OpenFang/OpenClaw (Builder View)](rexos-vs-openfang-openclaw.md)

docs-site/blog/what-is-loopforge.md

@@ -1,6 +1,6 @@
-# What Is LoopForge? (Formerly RexOS)
+# What Is LoopForge? (Formerly LoopForge)
 
-LoopForge is the new public brand of the product previously known as RexOS.
+LoopForge is the new public brand of the product previously known as LoopForge.
 We renamed to make the product easier to remember and easier to spread in builder communities.
 
 ## One-line positioning

docs-site/examples/case-tasks/index.md

@@ -26,5 +26,5 @@ Pick a scenario and run it locally. Each page is designed to be **copy‑paste f
 
 </div>
 
-!!! tip "New to RexOS?"
+!!! tip "New to LoopForge?"
     Start with the [New User Walkthrough](../../tutorials/new-user-walkthrough.md).

docs-site/examples/case-tasks/ten-copy-paste-tasks.md

@@ -14,7 +14,7 @@ mkdir -p my-work
 ## 1) Create a file
 
 ```bash
-loopforge agent run --workspace my-work --prompt "Create notes/hello.md with exactly: Hello RexOS"
+loopforge agent run --workspace my-work --prompt "Create notes/hello.md with exactly: Hello LoopForge"
 ```
 
 ## 2) Repo onboarding in 10 minutes

docs-site/examples/daemon-health.md

@@ -7,4 +7,4 @@ loopforge daemon start --addr 127.0.0.1:8787
 curl http://127.0.0.1:8787/healthz
 ```
 
-Use it for container readiness / supervision, and keep the rest of RexOS logic in the CLI for now.
+Use it for container readiness / supervision, and keep the rest of LoopForge logic in the CLI for now.

docs-site/examples/harness-recipes.md

@@ -1,6 +1,6 @@
 # Harness Recipes (Checkpoints)
 
-Use the harness when you want RexOS to iterate until your verifier passes, while staying rollback-friendly.
+Use the harness when you want LoopForge to iterate until your verifier passes, while staying rollback-friendly.
 
 ## 1) Fix a failing test suite with harness checkpoints
 
@@ -39,7 +39,7 @@ loopforge harness run . --prompt "Continue. Focus on the next failing verifier o
   - `features.json` (checklist)
   - `rexos-progress.md` (append-only progress log)
   - `init.sh` + `init.ps1` (your verifier scripts)
-- When your verifier passes, RexOS makes a **checkpoint git commit**.
+- When your verifier passes, LoopForge makes a **checkpoint git commit**.
 
 !!! tip "Rollback-friendly"
     If a checkpoint is bad, use git normally (e.g. `git reset --hard HEAD~1`) and run `loopforge harness run` again.

docs-site/explanation/concepts.md

@@ -1,17 +1,17 @@
 # Concepts
 
-RexOS is designed for long-running work where “one prompt” isn’t enough.
+LoopForge is designed for long-running work where “one prompt” isn’t enough.
 
 ## Workspace
 
-Most RexOS commands operate on a **workspace directory**:
+Most LoopForge commands operate on a **workspace directory**:
 
 - tools are sandboxed to it (filesystem + shell working directory)
 - the harness stores durable artifacts there
 
 ## Memory (SQLite)
 
-RexOS persists:
+LoopForge persists:
 
 - sessions
 - chat messages
@@ -31,7 +31,7 @@ The agent can call tools such as:
 !!! note "Browser tools prerequisites"
     By default, `browser_*` uses a local Chromium-based browser (Chrome/Chromium/Edge) via **CDP**.
 
-    If RexOS can’t find a browser executable, set `REXOS_BROWSER_CHROME_PATH`.
+    If LoopForge can’t find a browser executable, set `REXOS_BROWSER_CHROME_PATH`.
 
     Optional legacy backend: set `REXOS_BROWSER_BACKEND=playwright` and install Python + Playwright:
 
@@ -42,7 +42,7 @@ The agent can call tools such as:
 
 ## Model routing
 
-RexOS classifies runs into a task kind:
+LoopForge classifies runs into a task kind:
 
 - planning
 - coding

docs-site/explanation/security.md

@@ -1,6 +1,6 @@
 # Security & Sandboxing
 
-RexOS is built around running LLM-driven tool calls with guardrails.
+LoopForge is built around running LLM-driven tool calls with guardrails.
 
 ## Workspace sandbox
 
@@ -28,7 +28,7 @@ For local testing you can explicitly allow private targets with `allow_private=t
 
 ## Browser tools
 
-RexOS can run a headless browser via **CDP** by default (no Python), and can also use a legacy Playwright bridge backend.
+LoopForge can run a headless browser via **CDP** by default (no Python), and can also use a legacy Playwright bridge backend.
 
 - `browser_navigate` / `browser_click` / `browser_type` / `browser_press_key` / `browser_wait_for` / `browser_read_page` / `browser_screenshot` / `browser_close`
 
@@ -40,4 +40,4 @@ Security notes:
 
 ## Future: approvals
 
-RexOS has the structure to add “approval hooks” for higher-risk actions (network writes, destructive commands, etc.). This is intentionally conservative by default.
+LoopForge has the structure to add “approval hooks” for higher-risk actions (network writes, destructive commands, etc.). This is intentionally conservative by default.

docs-site/how-to/browser-automation.md

@@ -6,22 +6,22 @@ For copy-paste recipes, see: [Browser Use Cases](browser-use-cases.md).
 
 ## Default backend: CDP (no Python)
 
-RexOS launches a local Chromium-based browser (Chrome / Chromium / Edge) and drives it via **Chrome DevTools Protocol (CDP)**.
+LoopForge launches a local Chromium-based browser (Chrome / Chromium / Edge) and drives it via **Chrome DevTools Protocol (CDP)**.
 
 ### Prerequisites
 
 - Install a Chromium-based browser (Chrome/Chromium/Edge).
-- If RexOS can’t find it, set `REXOS_BROWSER_CHROME_PATH` to the browser executable path.
+- If LoopForge can’t find it, set `REXOS_BROWSER_CHROME_PATH` to the browser executable path.
 
 ### Remote CDP (optional)
 
-If you already have a browser running with a remote debugging port (or you run one in Docker), point RexOS at it:
+If you already have a browser running with a remote debugging port (or you run one in Docker), point LoopForge at it:
 
 ```bash
 export REXOS_BROWSER_CDP_HTTP="http://127.0.0.1:9222"
 ```
 
-By default, RexOS only allows **loopback** CDP endpoints. To attach to a non-loopback CDP URL, you must explicitly opt in:
+By default, LoopForge only allows **loopback** CDP endpoints. To attach to a non-loopback CDP URL, you must explicitly opt in:
 
 ```bash
 export REXOS_BROWSER_CDP_ALLOW_REMOTE=1
@@ -37,7 +37,7 @@ Then follow: [GUI Smoke Check](browser-use-cases/gui-smoke-check.md).
 
 ## Headless vs GUI
 
-By default, RexOS launches the browser in **headless** mode.
+By default, LoopForge launches the browser in **headless** mode.
 
 To show the browser window (local debugging / demos), set `headless=false` on the first `browser_navigate` call:
 
@@ -105,7 +105,7 @@ If a CSS selector fails, `browser_click` will try a **best-effort visible-text f
 Use this as a starting point for agent prompts:
 
 ```text
-You may use RexOS browser tools (browser_navigate/back/scroll/click/type/press_key/wait/wait_for/read_page/run_js/screenshot/close).
+You may use LoopForge browser tools (browser_navigate/back/scroll/click/type/press_key/wait/wait_for/read_page/run_js/screenshot/close).
 
 Rules:
 - Always call browser_read_page after navigate/click/type/press_key to verify page state before the next step.

docs-site/how-to/browser-use-cases.md

@@ -7,7 +7,7 @@ See also: [Browser Automation (CDP)](browser-automation.md).
 ## Prerequisites (default: CDP)
 
 - Install a Chromium-based browser (Chrome/Chromium/Edge).
-- If RexOS can’t find it, set `REXOS_BROWSER_CHROME_PATH`.
+- If LoopForge can’t find it, set `REXOS_BROWSER_CHROME_PATH`.
 
 Optional: use the Playwright backend (legacy) by setting `REXOS_BROWSER_BACKEND=playwright` and following the install steps in [Browser Automation](browser-automation.md).