root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(FN-4266): complete Step 4 — document headless auto-register

Browse Source 
Ref: Runfusion/Fusion#216
Fusion-Task-Id: FN-4266
Fusion-Task-Lineage: 4105d2eb-f3d8-4297-9b49-bf7e5a2906be
This commit is contained in:
Fusion
2026-05-12 23:25:02 -07:00
committed by gsxdsm
parent 638106e35e
commit ed9827a1bf
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/remote-access.md
View File

@@ -239,6 +239,12 @@ Remote hotkeys:
- `/api/remote-access/auth/login-url`
- `/remote-login?rt=...` public login handoff route
Headless startup now auto-registers the current working directory as a Fusion project when it is not already in the central project registry. On first run you'll see:
- `[serve] Auto-registered project "<name>" at <cwd>`
This removes the old requirement to run `fn init`/`fn project add` first in CI, Docker, cron, and other non-interactive environments. Use `fn serve --no-auto-register` to keep the previous strict behavior.
Parity expectations:
- Remote control/status contracts are the same in dashboard and headless runtime.