From 690637f300fe25d8f42505c78beb820b3fd369ab Mon Sep 17 00:00:00 2001 From: hongyi-chen Date: Tue, 18 Aug 2026 01:50:18 +0000 Subject: [PATCH] docs(factories): document that factories and the Oz web app coexist Aloke's soft-launch note to sales spells out three things a customer will experience that the docs never said: both the Slack and Linear integrations keep working after a factory exists, the two surfaces run side by side, and a factory enabled for a Linear team takes precedence over the legacy integration. The factories docs currently describe factories as though Oz v1 doesn't exist, and the platform Slack and Linear pages never mention factories at all, so the customer with both has no page written for them. - platform Slack and Linear: add a 'Factories and this integration' section. Slack has no conflict, since each factory installs its own app; Linear does, so that page states the precedence rule. - factories Linear: lead with precedence rather than framing it as a fallback, which read as though the legacy integration were primary. - factories overview: place the two web apps side by side and say plainly that creating a factory changes nothing you already run. Precedence is grounded in replaysBuiltInWhenUnclaimed in logic/ai/ambient_agents/webhook/workflow.go: a delivery with zero matched factory actions falls back to the provider's built-in behavior, so a matched one does not. No migration or consolidation timeline is mentioned, per Aloke's note not to communicate that yet. Co-Authored-By: Warp --- src/content/docs/factories/index.mdx | 2 ++ src/content/docs/factories/integrations/linear.mdx | 2 +- src/content/docs/platform/integrations/linear.mdx | 8 ++++++++ src/content/docs/platform/integrations/slack.mdx | 6 ++++++ 4 files changed, 17 insertions(+), 1 deletion(-) diff --git a/src/content/docs/factories/index.mdx b/src/content/docs/factories/index.mdx index eb05f3372..c51210ad1 100644 --- a/src/content/docs/factories/index.mdx +++ b/src/content/docs/factories/index.mdx @@ -46,6 +46,8 @@ Warp Factories is designed for engineering teams with repeatable work that exten | **{VARS.WARP_CLI}** | Runs the Warp Agent in any terminal and exchanges work with a factory through the Factory MCP. | | **{VARS.WARP_AUTOMATION_PLATFORM}** | Provides the cloud runs, environments, runners, integrations, secrets, orchestration, and APIs that a factory assembles into one workflow. | +Warp Factories runs alongside the {VARS.WEB_APP} rather than replacing it. Each has its own home: the {VARS.FACTORY_WEB_APP} for factories, and the {VARS.WEB_APP} for everything you run there today. Creating a factory changes nothing about your existing environments, schedules, and Slack and Linear integrations, which keep working. + ## Next steps * [**Set up a factory**](/factories/quickstart/) - Create a factory and send its first work item. diff --git a/src/content/docs/factories/integrations/linear.mdx b/src/content/docs/factories/integrations/linear.mdx index dabd6b147..d4b1065d9 100644 --- a/src/content/docs/factories/integrations/linear.mdx +++ b/src/content/docs/factories/integrations/linear.mdx @@ -50,7 +50,7 @@ Both paths end in the same state: Linear is connected to your factory, and a def ## Route agent sessions -When someone mentions, assigns, or delegates the Warp app on an issue, Linear starts an agent session. The default automation created when you connected Linear routes new sessions from your selected teams to the factory, so assigning an issue or tagging the factory in a comment is enough to start work. If a session doesn't match any automation, the [Linear integration](/platform/integrations/linear/) handles it with its default behavior. +When someone mentions, assigns, or delegates the Warp app on an issue, Linear starts an agent session. The default automation created when you connected Linear routes new sessions from your selected teams to the factory, so assigning an issue or tagging the factory in a comment is enough to start work. The factory takes precedence for the teams its automations cover: a matching session routes to the factory rather than to the [Linear integration](/platform/integrations/linear/), which still handles any session that matches no automation. Agent sessions don't appear as a trigger in the [automation editor](#configure-linear-triggers). To change how sessions route, for example by creator or keyword, edit the `agent_session_created` event in the factory's [version-controlled definition](/factories/factory-as-code/). Replies in an existing session continue that run; they aren't separate triggers. diff --git a/src/content/docs/platform/integrations/linear.mdx b/src/content/docs/platform/integrations/linear.mdx index 9648f3c14..8565c28ca 100644 --- a/src/content/docs/platform/integrations/linear.mdx +++ b/src/content/docs/platform/integrations/linear.mdx @@ -66,6 +66,14 @@ Because PRs are created as _you_, this makes code review, auditing, and team col --- +### Factories and this integration + +If your team also runs a [software factory](/factories/), both keep working. This integration continues to handle the Linear teams that no factory covers, so an existing setup needs no changes. + +Where the two overlap, the factory takes precedence: when a factory automation matches an agent session, that session routes to the factory instead of starting a run here. A session that matches no factory automation falls back to the behavior described above. For how that routing is configured, see [Connect Linear to your factory](/factories/integrations/linear/). + +--- + ### Requirements * **Team membership** - The Linear integration requires you to be part of a [Warp team](/knowledge-and-collaboration/teams/). Teams can be created on any plan, including Free. diff --git a/src/content/docs/platform/integrations/slack.mdx b/src/content/docs/platform/integrations/slack.mdx index 44dda2900..7d35fa440 100644 --- a/src/content/docs/platform/integrations/slack.mdx +++ b/src/content/docs/platform/integrations/slack.mdx @@ -96,6 +96,12 @@ Because PRs are created as you, the workflow slots seamlessly into your team’s --- +### Factories and this integration + +If your team also runs a [software factory](/factories/), both keep working. A factory connected to Slack installs its own app carrying that factory's name, so the two never compete for the same mention: **@Warp** starts a cloud agent run through this integration, and mentioning a factory's app sends the request to that factory. See [Connect Slack to your factory](/factories/integrations/slack/). + +--- + ### Configuration #### 1. Create an environment