YOU

FAQ

Short answers to common you-agent-factory questions that point at the canonical docs and reference pages for install, running factories, authoring, agents, configuration, and recovery.

What Is You-Agent-Factory, And Where Do I Start?

you-agent-factory is the CLI and workflow system that keeps long-running agent work persistent. It installs as one binary named you. Start with the product overview, then install it and run a packaged factory before digging into CLI depth.

How Do I Install You?

Install with the OS-specific script for your machine, confirm you resolves on PATH, then configure the provider that runs your workers. Install carries the full command matrix—this FAQ does not repeat those commands.

How Do I Run A Factory?

Install a packaged factory with you init --package, then run it by name with you run --named and a request. A plain run is batch mode and starts no HTTP listener, so you session list only answers when a run was started with a server or when you server is up.

Which Factories Ship With The Binary?

Fifteen packaged factories ship in the embedded catalog, covering goal pursuit, review loops, quorum and tournament comparison, parallel fan-out, planning, classification, deep research, factory authoring, and text to speech. Each publishes its own arguments, defaults, and worked examples.

Should I Write A Graph Factory Or A JavaScript One?

Write a graph factory when the workflow is a topology work moves through and you want durable per-item state and concurrency for free. Write a JavaScript factory when the workflow is a procedure and you want ordinary control flow. The orchestrator field picks the engine; omitting it means graph.

Where Does Configuration Live?

Per-factory topology lives in factory.json under the factory root; operator defaults such as the worker provider live in ~/.you-agent-factory/config.json. Named factories installed from the catalog live under ~/.you-agent-factory/factories unless you point them elsewhere.

How Do I Make An AI Agent Use YOU?

Tell the agent to run you docs agents and read the output. That topic is the agent orientation and command matrix carried inside the installed binary, so the agent learns the command surface it actually has rather than a copy that can go stale. From there it drives the CLI directly.

How Do MCP Or Cursor Dynamic Workflows Connect?

Hosts spawn you mcp serve so Factory Session tools appear under you.factory_session.* names, and Cursor uses that bridge for its first dynamic-workflow loop. The MCP server communicates over stdio and starts no HTTP or dashboard listener of its own.

Where Are The Exact Commands And Schemas?

On the reference pages, which are projected from the installed @you-agent-factory/api package rather than retyped. The CLI reference carries every published command, flag, and argument; the API reference renders the shipped OpenAPI document; the Events reference carries the full event corpus and stream contracts.

Something Failed—Where Do I Recover?

When install, run, configuration, MCP, or dynamic-workflow steps fail, open Troubleshooting for symptom-scoped recovery that links into the owning canonical docs. Use this FAQ for common how-to questions; use Troubleshooting when you already have a failure symptom.

On this page

What Is You-Agent-Factory, And Where Do I Start?How Do I Install You?How Do I Run A Factory?Which Factories Ship With The Binary?Should I Write A Graph Factory Or A JavaScript One?Where Does Configuration Live?How Do I Make An AI Agent Use YOU?How Do MCP Or Cursor Dynamic Workflows Connect?Where Are The Exact Commands And Schemas?Something Failed—Where Do I Recover?