diff --git a/.claude/skills/docs/watermark b/.claude/skills/docs/watermark index 108d4b049..5d44dfced 100644 --- a/.claude/skills/docs/watermark +++ b/.claude/skills/docs/watermark @@ -1 +1 @@ -533785cd4c107cee673825847b1f8fe3d8d14dfe +d2cc37c615894d56ef672d00004ce13ce3b328c2 diff --git a/docs/administration/deploy-server.mdx b/docs/administration/deploy-server.mdx index 2b0db49eb..684ec2832 100644 --- a/docs/administration/deploy-server.mdx +++ b/docs/administration/deploy-server.mdx @@ -34,7 +34,9 @@ This starts the server on a Unix socket at `~/.fabro/fabro.sock` by default. Use ### First run: web install wizard -If `~/.fabro/settings.toml` does not yet exist, `fabro server start` enters **install mode**: it prints an install URL, attempts to open the URL in your default browser, and serves a web wizard that walks you through configuring your server URL, shared object store, LLM provider, and GitHub integration. +If `~/.fabro/settings.toml` does not yet exist, `fabro server start` enters **install mode**: it prints an install URL and a one-time install token, attempts to open the URL in your default browser, and serves a web wizard that walks you through configuring your server URL, shared object store, LLM provider, and GitHub integration. + +When Fabro can construct a direct install URL, the token is embedded in the URL and also printed on its own line for copying. If you open the server root through a reverse proxy or another machine, paste the printed install token when prompted. The `Object store` step offers two wizard-managed modes: @@ -87,6 +89,8 @@ The web UI connects to the API server and provides: - **Runs board** — Monitor all active runs organized by status - **Run detail** — Real-time stage progress, event stream, diffs, and usage stats +- **Files Changed** — Browse changed files with a searchable tree, per-file status, aggregate diff stats, and split or stacked diffs +- **Settings** — Inspect server configuration, enabled integrations, storage, auth, and capacity settings - **Start new run** — Submit workflows from the browser - **Human-in-the-loop** — Answer agent questions through the web interface - **Workflows** — Browse available workflows, view their graphs, and see run history @@ -145,6 +149,12 @@ Or use the `--server` flag: fabro model list --server https://fabro.example.com/api/v1 ``` +For dev-token servers, save the token in the CLI auth store instead of exporting it for every command: + +```bash +fabro auth login --server https://fabro.example.com/api/v1 --dev-token fabro_dev_... +``` + `fabro model list` and `fabro model test` honor `[cli.target]` by default unless you explicitly pass `--storage-dir`. `fabro exec` remains a local agent session and only uses the server when you pass `--server`. See [User Configuration](/reference/user-configuration#cli-target-section) for the full connection options, including client certificates for proxy-terminated HTTPS endpoints. diff --git a/docs/execution/checkpoints.mdx b/docs/execution/checkpoints.mdx index 3eddce7c8..b8c2fe891 100644 --- a/docs/execution/checkpoints.mdx +++ b/docs/execution/checkpoints.mdx @@ -39,6 +39,8 @@ The commit message follows a structured format: The `Fabro-Checkpoint` trailer links each run branch commit to its metadata branch commit, so you can navigate from file changes to the full execution state and back. +Fabro disables Git commit and tag signing for checkpoint commits created inside a sandbox. Your personal or repository-level signing settings can stay enabled, but sandbox bookkeeping does not need access to your signing key. + ### Metadata branch The metadata branch (`fabro/meta/{run_id}`) is an orphan branch that stores structured run data using Git's object storage directly (via `git2`). It is initialized at run start with: