docs: compare how to start work with a factory from every source

[warp-agent-staging]

What this feature does

Warp Factories docs describe how to start work from each connected surface, but the mechanics are scattered across five separate integration guides with no single place to compare them or link to. This adds a "Start work by" column to the existing "Choose a source" table so a reader (or an external article) can see the concrete action per surface in one place.

Summary

Adds a "Start work by" column to the "Choose a source" table on factories/connect-your-factory.mdx so a reader can compare, side by side, the concrete action that hands work to a factory from every connected surface (Slack, GitHub, GitLab, Linear, Jira, the factory API, Factory MCP, and direct runs/schedules) — each linking to that integration's existing "start work" section instead of repeating it.

Per docs-worthiness-criteria.md (a person's direct request is subject to Gate 0 only) and its bias toward updating an existing page, this extends connect-your-factory.mdx — already the cross-integration overview page — rather than creating a new page. The "Choose a source" table and heading (#choose-a-source) are unchanged as an anchor, so it stays a stable link target for the follow-up backlink from the marketing article (tracked separately; that's a change to warp.dev, not this repo).

Changes

src/content/docs/factories/connect-your-factory.mdx

• Added a "Start work by" column to the "Choose a source" table, naming the concrete action per source and linking to that integration's existing "start work" section
• Added one sentence introducing the new column

Content design plan

Short form (update that adds a new concept to an existing page):

• Reader and job: Someone deciding how to send work to a factory from wherever they already are (Slack, an issue tracker, a PR, a script, or a local coding agent), or a reader following a link from an external article who wants the concrete action without reading five separate integration guides.
• Gap today: "Choose a source" compares sources by "Best for" and "Continues in," but never states the concrete action that starts work — that detail is scattered one level down, in each integration guide's own "start work" section.
• Change: One new "Start work by" column in the existing table, naming the action per source (a mention, an assignment, an API call, an MCP tool call) and linking to the fuller instructions. Excludes repeating each integration's full setup/authorization steps, which stay owned by their own guides.

Unverified claims

None — every mention handle, label, endpoint, and MCP tool name in the new column is copied from that integration's own already-published page in this repo; no new product claims were introduced.

Originating thread: https://warpdotdev.slack.com/archives/C09BVK0PL3Y/p1788371982148849

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 3, 2026 12:33am UTC

[warp-for-oss]

@warp-agent-staging[bot]

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

Overview

This PR updates the factory connection overview table with a Start work by column so readers can compare the concrete handoff action for each supported source. I checked the new links against the referenced source docs, reviewed the docs style guidance, confirmed the attached spec context has no approved spec to enforce, and found no security-relevant concerns in this documentation-only change.

Concerns

• No blocking concerns found.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz