---
title: "Bisque Use Software Factory"
description: "Code changes, research, and documents, with Foreman chat, workers on your Macs, and linked results in Tasks."
canonical: https://bisque.cloud/docs/factory
---

# Use Software Factory

Code changes, research, and documents, with Foreman chat, workers on your Macs, and linked results in Tasks.

Page: https://bisque.cloud/docs/factory

Software Factory brings Foreman chat, Nemo and Orca workers, and task tracking
together for projects on your Macs. It covers code changes with pull requests
and checks, research and comparisons, and documents you can open and comment on.

Use **Foreman** for the conversation, **Tasks** to follow a piece of work,
and **Factory › Status** to see the computers and workers running it.

## Start with one useful request

[Set up your first task](/docs/factory/first-task) on the Mac that will run Factory.
Then open [Foreman](/foreman) and describe the result you want:

> Read this project's README and compare its setup instructions with the code.
> List three concrete corrections. Don't change files or open a pull request.

You get findings about your project, rather than a code change. When you want
the corrections made, ask Foreman to update the README and check the
instructions. A code request follows the project's review and delivery rules.

For another kind of result:

> Compare the two sign-in options in this design. Give me a document with the
> trade-offs and a recommendation. Don't implement either option.

You get a document to review, not an implemented feature. Tell Foreman which
files or links to read, who the result is for, and what is outside the request.

## Choose the guide for your next step

- [Set up your first task](/docs/factory/first-task): prepare a Mac and send a bounded request.
- [Ask for work and review the result](/docs/factory/tasks): give feedback, answer a
  question, and distinguish a finished document from a released code change.
- [Understand access and computers](/docs/factory/access): know where work runs and
  which permissions you grant.
- [Choose skills for your agents](/docs/factory/skills): install a library, read each
  computer's result, and understand updates.
- [Get work moving again](/docs/factory/troubleshooting): check setup, a waiting job,
  or a result that is missing something.

## Understand who does what

**You** choose the outcome, supply context, and answer decisions that require
your judgment. You also complete provider sign-ins and macOS permission prompts.

**Foreman** is the agent you talk to. It assigns work, carries your corrections
to the task, and follows the task through its remaining steps.

**Nemo workers** handle research, documents, presentations, and small code
changes. **Orca workers** handle larger code changes and work that needs an
interactive coding-agent session. You can name a worker in your request;
otherwise, Foreman chooses for the work.

## Keep the execution Mac available

Factory runs on a Mac you choose. A browser or phone lets you send requests,
answer questions, and inspect results; it does not replace the computer
running Foreman or a worker. Keep that computer awake, connected, and allowed
to run in the background.

Factory pages depend on your account's access and the installed app version.
If a page is missing or setup is incomplete, follow
[Get work moving again](/docs/factory/troubleshooting#open-the-right-account-and-computer).

## Find the other Bisque guides

Factory is separate from installing presentation skills in a coding agent.
The [present skill](/docs/present) turns material your agent can read into a
presentation you can watch and share. The [Artifacts guide](/docs/artifacts)
explains documents and pages, including comments, access, and revisions.
Installing those skills does not set up a Factory execution Mac.
