Security boundaries for a single-workspace agent pilot
Know who the API serves
Agents v0.10 is a single-workspace operator application. Administrator, operator and viewer roles restrict actions inside that workspace; they are not customer tenant boundaries or anonymous-widget tokens. Start with named staff on a private network or loopback. Do not copy operator credentials into an embedded customer page.
Provision and protect access
Offline setup creates scrypt-backed credentials and private bootstrap instructions. Protect the operator file, SQLite store, exports and separate backup key with OS permissions. POSIX file modes do not establish Windows ACLs. Restart after account-file changes. Cookies are HttpOnly and SameSite Strict; authenticated mutations require CSRF. SSO, MFA and email password reset are not implemented.
Review data destinations
A configured remote model receives conversation context; explicit visual snapshots can send pixels when enabled. Remote inference requires explicit configuration and your own retention review. Evidence mode avoids model requests, but browser recognition can still send audio outside the machine. Keep credentials server-side and document the actual model and speech paths.
Validate deployment and retention
The strict profile requires an HTTPS origin, loopback proxy trust, operator credentials and SQLite. The proxy must overwrite address headers. Startup checks do not replace host-specific proxy and security acceptance. Published profiles and sessions retain source copies after originals are archived. Inventory transcripts, exports and backups separately, then assess customer isolation and deletion requirements before a wider rollout.
Product and guides
Explore creekX Agents · Quick start · Documentation. Written for v0.10 early access, 23 October 2026.
Frequently asked questions
Where should I start?
Read the separate Agents quick start and evaluate v0.10 in a private local workspace before a customer pilot.