Get a factory

Public UID of the factory.

Public UID of the team that owns the factory.

Display name of the factory.

Optional description of the factory.

Optional display handle for the factory, unique across the team's Warp workspace when set.

Short-lived signed URL for displaying the factory's avatar. The URL may change between reads.

Primary source-control provider for the factory. GITHUB and GITLAB identify the compatibility primary when repositories span one or more forges. AZURE_DEVOPS identifies Azure Repos. NONE declares a repo-less factory with no native repositories; its environment relies on setup_commands to clone from any host.

Public UID of the factory's default environment. File-managed factories may omit this default.

The default model ID for the factory's runs. File-managed factories may omit this default. Live-managed create and PATCH requests still capture a concrete validated model ID.

Default credential strategy for runs executed by the factory's named agents.

• EXECUTOR (default): runs authenticate with the named agent's own credentials (e.g. a GitHub App installation token for the factory's team).
• CREATOR: runs authenticate with the credentials of the principal that created the run.

When true, only the Warp user who started a run may send it follow-ups. Senders on Slack, GitHub, Linear and other integrations are matched to Warp users through their linked accounts; follow-ups from agents and the system are unaffected.

When true, follow-ups sent with a service account's API key are accepted even though restrict_followups_to_starter is true. Has no effect while restrict_followups_to_starter is false.

Time the factory was created.

Time the factory was last updated.