Handbook

Examples — Lenses / Studio integration

Checklist:

Updated

Step Detail
Studio env LENSES_FLEET_URL + LENSES_FLEET_TOKEN (Settings → Fleet)
Evidence POST /v1/admin/test-fleet only via workspace server (never raw browser)
Proof Matching rows under /admin/ Recent jobs + meta.sqlite_path consistency

Deep narrative → Learn 101 — Admin & Studio.

Purpose

Checklist for wiring Forge Lenses / Studio to Fleet (LENSES_FLEET_*) and validating via test-fleet.

Prerequisites

Studio build that supports Fleet settings; workspace server reachable.

Copy-paste steps

Configure env in Studio, run POST /v1/admin/test-fleet from the workspace context (not ad-hoc browser fetch without token handling).

Expected output

/admin/ recent jobs list aligns with meta.sqlite_path on the Fleet host.

Error handling

Treat 401 as token/binding mismatch; re-check LENSES_FLEET_URL (no stray slash) and firewall rules.

Security notes

Never expose admin tokens to untrusted browser extensions; use Studio-managed storage.

Validation status