Run Your First Factory

Install a packaged factory from the embedded catalog and run it end to end without writing any configuration.

What It Is

A packaged factory is a complete, published workflow with a canonical name such as @you/goal. You supply the request; the factory supplies the graph, the workers, the review steps, and the argument contract. Fifteen ship with the binary, covering goal pursuit, review loops, parallel fan-out, tournaments, deep research, and text to speech.

Packaged Factory Reference — every shipped factory and its unabridged source

When To Use

Run one right after installing, before writing anything of your own. A packaged run proves the install works, proves the provider is configured, and shows you the shape of a factory run before you have to author one.

Steps Or Workflow

Install a packaged factory into your named factory root, confirm it landed, then run it against a request. @you/goal is the best first choice: it persists progress and keeps working the goal until the executor calls it complete or blocked.

Install a packaged factory from the embedded catalog

you init --package @you/goal

Confirm it landed in the global named factory root

you factory list --dir ~/.you-agent-factory/factories

Run it against a request

you run --named @you/goal "Summarise this repository"

Invocation input reaches the factory three ways: positional text after the command, piped stdin, or a named argument the factory declares. Piping is the easiest way to pass a long request without quoting it.

echo "Summarise this repository" | you run --named @you/goal

Print only the final result instead of streaming progress

you run --named @you/goal --output primary "Summarise this repository"

Watch The Run

A plain run starts no HTTP listener — it executes in batch mode and exits once the work settles. Ask for the embedded dashboard when you want to watch the graph move: the listener binds loopback only, lives exactly as long as the run, and opens the browser once it is ready.

you run --named @you/goal --with-site "Summarise this repository"

Use the server flag without the dashboard when you want the HTTP API available for the lifetime of the run but no browser window. Either way the listener disappears when the run ends.

you run --named @you/goal --with-server "Summarise this repository"

List sessions on that running host

you session list

API — reaching a running factory over HTTP

Try Another Factory

Each packaged factory declares its own arguments, so the same two commands work across the catalog. @you/review produces candidate work and repeats independent review until approval; @you/quorum runs independent assessments in parallel and merges them; @you/spawn plans an exact number of tasks and executes them concurrently.

you init --package @you/review
you run --named @you/review "Draft the release notes"

Every packaged factory publishes its argument names, defaults, and worked examples. Read those before guessing at flags.

Common Pitfalls

A packaged factory still needs a provider to drive its workers. If the run exits almost immediately with no output, the usual cause is that no default provider is configured, not that the factory is broken. Also note the invocation input is required: a named run with no positional text and no piped stdin has nothing to work on.

Next Steps

Once a packaged factory does something close to what you want but not close enough, the next move is to write your own — or to hand the whole catalog to an agent and let it choose.