F Forge Project Guide
Docs / Support

Support

Get the fastest path to fixing pairing, sync, connectivity, or runtime problems.

Use this page when Forge or Forge Companion is not behaving as expected. The common failure points are pairing, HealthKit permissions, shared runtime configuration, Tailscale reachability, and local agent setup.

First Checks

These are the fastest checks before you go deeper.

Core runtime

openclaw forge health
curl -I http://127.0.0.1:4317/api/v1/health
curl -I http://127.0.0.1:4317/forge/

Confirm the Forge backend and mounted web app are reachable before debugging agent or companion behavior.

Shared system shape

origin:   http://127.0.0.1
port:     4317
dataRoot: one shared location
userId:   explicit on writes

Most confusing behavior comes from different surfaces pointing at different Forge stores instead of one shared runtime.

Common Issues

Most support requests fall into one of these buckets.

OpenClaw plugin does not load

Re-run the install with --dangerously-force-unsafe-install, then restart the gateway and run openclaw plugins inspect forge-openclaw-plugin --runtime. On OpenClaw 2026.5.4, the plain install is blocked by the scanner because Forge contains local runtime startup helpers; the explicit approval flag is required.

Companion pairs but does not sync

Verify that the iPhone companion and the browser are targeting the same Forge origin and data root, then confirm Apple permissions for HealthKit and local network access.

Tailscale route works for some pages only

Forge should stay mounted through the backend at http://127.0.0.1:4317/forge/. Tailscale should proxy /forge to that backend route, not directly to the Vite dev server.

Agent surfaces disagree with the browser

Check origin, port, and especially dataRoot for OpenClaw, Hermes, Codex, and the browser. If those differ, you are looking at different Forge systems.

Forge Companion diagnostics screen showing connection checks and sync details.
The companion diagnostics view is the right place to inspect pairing, connection, and sync state before escalating a mobile-side issue.

Where To Look Next

Use the page that matches the kind of problem you are trying to solve.

Integrations guide

Best for OpenClaw, Hermes, Codex, shared-runtime setup, and iPhone companion installation questions.

Development guide

Best for local runtime commands, verification steps, and docs/API generation details.

Features guide

Best when the question is whether a behavior is part of the product model or a misunderstanding of the intended UX.

API reference

Best for exact route paths, request shapes, response bodies, and interactive inspection.

Contact

Use direct support when the docs do not cover the failure mode.

Email support

albert.buchard@gmail.com

Include the surface that failed, the exact URL or route, the date, and what you already checked.