# Workstream Settings and Usage

Change a workstream's name and models, set your Workstream Defaults, see what your organization controls, and track what a workstream uses.

Workstreams have two places for settings: **Workstream settings** for one workstream, and **Workstream Defaults** in Settings for every workstream you start.

## Workstream settings

Open **Workstream settings** from the gear icon in the workstream's header.

![Workstream settings dialog on its General section, with Name and the orchestrator and agent models](/docs-assets/images/workstreams/workstream-settings.webp)

<PropertyList>
  <Property name='Name'>
    Shown in the sidebar and above the workstream.
  </Property>
  <Property name='Orchestrator model'>
    The model that plans the work and coordinates agents.
  </Property>
  <Property name='Orchestrator reasoning'>
    Reasoning effort for the orchestrator.
  </Property>
  <Property name='Agent model' defaultValue='Default'>
    The model for all agents. **Default** uses each agent machine's default model.
  </Property>
  <Property name='Agent reasoning' defaultValue='Default'>
    Reasoning effort for all agents.
  </Property>
</PropertyList>

The **Usage** section shows the credits the workstream has used, how many agents it has, and a breakdown by session with each session's model, credits, and share of the total.

## Workstream Defaults

Open **Settings → Workstream Defaults** to set defaults for every workstream you start.

<PropertyList>
  <Property name='Remote delegation' defaultValue='On'>
    Lets agents run on other machines: fresh computers from your default environment or the orchestrator's environment, and your additional machines. Off keeps every agent on the orchestrator's machine.
  </Property>
  <Property name='Orchestrator compaction budget' defaultValue='500,000 tokens'>
    How much context the orchestrator keeps before it compacts its conversation.
  </Property>
  <Property name='Default environment' defaultValue='None'>
    Where agents run when the orchestrator doesn't name a machine. Each agent gets a fresh computer. If you don't set one and the orchestrator runs on an environment, agents use that environment. It needs a description, like additional machines.
  </Property>
  <Property name='Additional machines' defaultValue='None'>
    Other machines agents may use, each with a description the orchestrator reads to route work.
  </Property>
</PropertyList>

See [Machines](/workstreams/machines#choose-where-agents-run) for how to set up machines and descriptions.

The orchestrator and agents start with your default [autonomy level](/factory-app/settings#autonomy-level), capped by your organization's policy.

## Usage limits

Workstreams have no separate fee; they use your regular Factory usage. They use more tokens than a single session because several agents work at once.

- When you reach 90% of a usage limit, the workstream shows a banner. Agents keep working until the limit, then stop until it resets. To make your usage last, switch the orchestrator or agents to a lower reasoning effort or a cheaper model with **Change models**.
- When your standard usage is used up, agents stop until it resets. You can switch the workstream to Droid Core models, which have a separate allowance, or add usage. See [Plans and pricing](/pricing/individuals).
- When you reach a limit your organization set, agents stop until it resets. Ask your organization to raise it.
- You can also switch to a model you bring yourself. See [BYOK](/model-independence/byok).

## Organization controls

Organization managers can shape what workstreams can do from **Enterprise Controls**:

| Control | Effect on workstreams |
| ------- | --------------------- |
| Store Shared Folders | Keeps shared folders when session contents sync is off. See [Shared folder](/workstreams/shared-folder#organization-settings). |
| Local computers | When turned off, workstreams can't run on members' own computers through the desktop app. |
| Remote Control | When not allowed, an orchestrator on a member's own computer can't send agents to other machines. See [Remote Control](/remote-control). |

Model policy and other [managed settings](/enterprise/hierarchical-settings-and-org-control) apply to workstream sessions like any other session.

<RelatedLinks>
  <RelatedLink href='/workstreams/machines' title='Machines'>
    Choose where the orchestrator and agents run.
  </RelatedLink>
  <RelatedLink href='/workstreams/pull-requests' title='Pull requests'>
    The PRs tab.
  </RelatedLink>
</RelatedLinks>