YOU

Security / Trust Boundaries

Current you-agent-factory trust boundaries for the local factory service, operator surfaces, and sensitive artifacts—not a compliance certification claim.

How To Use

The local factory service binds on the operator machine by default. Session and API traffic use the default local host and port http://localhost:7437 unless you override host or port. When the service was started via you or you run without quiet mode, the operator dashboard is available at http://localhost:7437/dashboard/ui on that same host and port. Treat that bind and dashboard URL as an operator-accessible local surface, not a multi-tenant public product edge. Autonomous agents must submit work only through the CLI—you submit for one item, you submit batch for a FACTORY_REQUEST_BATCH against a running factory, and you run --work only as part of local startup. Dashboard submit and POST /factory-sessions/{session_id}/work remain operator paths; autonomous agents must not treat them as parallel control ingress. Replay artifacts are sensitive because they can contain prompts, payloads, stdout, stderr, and diagnostic metadata. Retention is operator-owned: the product does not delete old recordings automatically, and operators manage what stays in the home directory or CI workspace. Config and operator-default diagnostics name the config path and sources (file, env, flag, or unset) without printing unrelated environment values or credentials. Model Context Protocol (MCP) serve is stdio-bounded: you mcp serve runs as a host-spawned stdio child process, and HTTP or SSE MCP transport is unsupported on that path.

Limits And Assumptions

Current you-agent-factory trust boundaries for the local operator service stay at the behaviors below. It is not a penetration-test report, not a compliance certification, and not an enterprise hardening program. Current behavior does not invent default TLS, multi-tenant authentication, or single sign-on (SSO) on the local service bind. The product does not claim automatic secret redaction across prompts, payloads, logs, or replay artifacts, and it does not automatically delete old replay recordings. Broader remote hardening, multi-tenant auth, and transport expansion remain roadmap or out of scope unless a shipped surface documents them. The product does not rebuild or harden the factory dashboard UI; the dashboard remains the local operator surface served by the running factory host.

Tags

On this page

How To UseLimits And AssumptionsTags