Use Bisque for Mac to choose the computer and repository where Factory will work. Start with a read-only request so you can check the connection before asking for a code change.
Prepare the Mac and project
You need a Bisque account with Factory access, a local Git repository, and the provider accounts for the agents you plan to use. Code work also needs GitHub access to the repository and the tools your project uses for checks.
- Download Bisque for Mac on the Mac that will run Factory, open it, and sign in to your Bisque account.
- Open Factory › Status. If Factory is not set up, choose Set Up on This Mac….
- Complete the setup window's sign-in and repository checks. Choose the local repository that Foreman will work in. Follow the fixes shown for missing tools, GitHub access, Orca, and coding-agent sign-in.
- Connect the provider for Foreman and the workers you will use. Signing in to Bisque does not sign you in to a model provider. If you choose Test, setup sends a real model request; provider usage or charges can apply.
- In Factory › Status, turn on Run in the background. If macOS asks, allow Bisque in System Settings › General › Login Items.
- Resolve any remaining items in Needs you. On the coordinating Mac, Fix… opens Set Up Factory with the missing checks. If setup says Foreman has no chat yet, choose Create Chat for an in-app conversation.
When setup is complete, Status names the computer running Foreman and shows its check-in time. This Mac shows your repository and background setting. Those local controls appear in Bisque for Mac, not in a phone's browser.
Do not move Factory just because you opened Bisque on a second Mac. If Status names another computer as the host, use that computer for its local setup. Join Factory adds a worker computer; it does not transfer Foreman.
Send a read-only request
-
Open Foreman.
-
Send this request, replacing the subject if your repository has no README:
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.
-
Read the reply. It must identify corrections in your project, not generic writing advice. If Foreman needs a file or a choice from you, answer in the same conversation.
-
If Foreman delegates the work, open Tasks to follow it. Open the task to read its next step, result, and any linked document.
The expected result is a read-only assessment. This request does not authorize implementation. If the result names the wrong project, stop there and check Repository on the coordinating Mac before asking for changes.
Ask for a small code change
Once the assessment is useful, choose one correction:
Update the README's install instructions to use the package manager this project actually uses. Change only that section and check the commands.
Factory can prepare a pull request with the change and its verification results. Read Ask for work and review the result before treating a merged pull request as a delivered change.
If setup or the request does not progress, use Get work moving again. You do not need an iMessage bridge to follow this in-app conversation path.