---
title: "Bisque Understand access and computers"
description: "Know where work runs and which account, file, and system access it uses."
canonical: https://bisque.cloud/docs/factory/access
---

# Understand access and computers

Know where work runs and which account, file, and system access it uses.

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

Factory uses your Macs to run agents against a selected project. Your Bisque
account holds the conversation and task records; the computer running the
agent supplies its local tools, files, and signed-in services.

## Separate conversation from execution

- **Foreman** coordinates work on one Mac. Check **Factory › Status** for
  the host name and its last check-in.
- **Workers** run the assigned work on a suitable Factory computer. A job
  stays with its assigned computer when that computer goes offline.
- **Your browser or phone** lets you talk to Foreman and review results.
  Leaving it open does not keep an execution Mac awake.
- **GitHub** holds a code change's pull request and checks. A document-only
  result can live in Bisque without a pull request.

Foreman chooses a computer based on the worker, tools, repository, and
available capacity the job needs. A healthy coordinator does not mean every
worker computer is online or ready for a particular project.

## Grant each kind of access deliberately

**Bisque sign-in** connects Foreman to your account. Approve the browser
pairing for the intended account. It is separate from your agent provider's
sign-in and from GitHub access.

**Provider sign-in** lets Foreman or a worker use a model. A saved credential
does not prove that the selected model is available. Setup's **Test** makes
a real request and can consume plan usage or incur provider charges.

**Repository and tool access** lets agents read files, run commands, and make
the changes you requested. Give the project the tools it needs for its own
checks. Do not paste credentials into chat to resolve a setup failure.

**macOS permissions** must be granted on the computer that needs them. Complete
the system prompt yourself. For work that controls apps or captures windows,
follow setup's checks for the relevant helper and permission.

Signing in to a Bisque account is not a local file sandbox. Foreman and its
workers can run shell commands with the access of the macOS user running
them. Use a separate macOS user or a virtual machine if that work must be
separated from other local files and credentials; Factory does not create
that separation for you.

## Add a worker Mac without moving Foreman

1. Open Bisque for Mac on the additional computer and use the same Bisque
   account.
2. Open **Factory › Status**. Confirm that it names the computer already
   running Foreman.
3. Choose **Join Factory** and complete the worker setup checks. On a joined
   computer, **Set Up Workers…** reopens those checks.
4. Check the computer's row in Status for available workers and any reason
   it cannot accept work.

To stop new assignments to that computer, choose **Leave Factory**. Work
already assigned can finish. Leaving does not cancel those jobs or move the
coordinator. Skill installation has a separate report; follow
[Choose skills for your agents](/docs/factory/skills) rather than treating a joined
computer as proof that every skill is installed.

## Stop work or remove access

To stop a task, ask Foreman to stop the named work and confirm it stopped.
To stop the coordinating Mac's background service, turn off **Run in the
background** in **Factory › Status** on that Mac. Quitting the Bisque window
alone leaves an enabled background service running. A background switch is
not confirmation that a worker on another computer has stopped.

To revoke a signed-in Mac's Bisque credential, open
[Settings › Keys](/settings/keys) and revoke its **Foreman on…** key. Revocation
removes that credential's access; it is not a command to undo code changes or
cancel every running process. Disconnect provider and GitHub access through
their own account controls when you need to remove those permissions too.
