Factory's Droid Agent Now Reads Slack, Sentry, and Salesforce to Code Smarter

Factory just gave its Droid agent a way to reach into the rest of the stack. Connectors and Personas let Droid sign in to the apps a team already uses, then tailor its first suggestions to the role of the person driving it. Droid already writes and ships code, but most of the context that decides what to build lives in Linear tickets, Slack threads, Sentry alerts, Notion pages, and Salesforce records.

For anyone who has used Droid only as a terminal or IDE coding agent, this widens the surface considerably. Factory positions Droid as infrastructure-agnostic, working across any IDE, CLI, Slack, Linear, or web interface, and Connectors extend that reach into the operational tools around the codebase.

Connect once, delegate everywhere

Connectors give Droid managed access to the apps your team uses. Pick an app, sign in, start delegating. Droid finds the right tools when a task needs them, so there is no server to configure and no API to learn. Connect once and it works across Desktop, CLI, web, and mobile.

Custom or self-hosted systems still work through MCP for private services and internal tools. Connectors add a managed path for supported apps, and both approaches operate in the same session. Supported integrations at launch include Google, Linear, Databricks, Notion, Snowflake, Figma, Datadog, Sentry, PagerDuty, GitHub, Slack, Amplitude, Salesforce, Stripe, Gong, and Outlook, with the company citing over 50 tools in total.

Personas point each role at the right stack

Personas handle onboarding. When someone opens Factory for the first time, they pick the persona that matches their work: Engineering, Product, Design, Finance, Marketing, Sales, or Operations. Factory then shapes the starter tasks and recommends Connectors around that role.

In Enterprise organizations, Owners and Managers can recommend approved Connectors for each persona, so the walkthrough points each role to the apps it actually uses. That matters at scale because it removes the blank-page problem when a non-engineer first opens an agent tool.

Three workflows worth studying

Factory published three concrete scenarios that show how the Connectors chain together across systems:

• Engineering incident triage. The signals live in Sentry and Datadog, the incident timeline in PagerDuty, and the code, recent changes, and ownership context in GitHub and Linear. Droid correlates them, finds the first bad commit, drafts a patch, and prepares a Linear-ready incident brief.
• Product roadmap from feedback. Feedback and prior decisions are spread across Slack and Notion, commitments live in Linear, wireframes in Figma, and usage data in Amplitude. Droid returns a sourced recommendation with tradeoffs and open questions.
• Finance variance analysis. Revenue sits in Stripe, pipeline in Salesforce, expense detail in Expensify, and the forecast and plan in Google Sheets and Anaplan. Droid ranks the largest drivers of a forecast change and links each explanation to its source.

Guardrails IT will actually approve

The enterprise controls are where this stops being a plugin marketplace. Owners and Managers decide which Connectors members can use, which Personas are available, and which Connectors to recommend for each role. Recommendations do not grant access, so each person still authenticates their own account.

Kill-switch behavior is strict. If an admin turns off a Connector, its tools are removed from Droid, members can no longer create authorization links, and calls to that Connector are blocked, even from sessions already in progress.

Write actions are gated by the session's autonomy setting. The selected level determines whether read-only calls can run automatically and when Droid must ask for confirmation before a write, a destructive action, or anything it cannot classify.

Why it matters

Most autonomous coding tools have optimized for the inner loop: repo, terminal, IDE. The interesting shift here is Droid treating the whole SDLC operations layer as first-class context. Rather than each user wiring up their own MCP servers, Factory is offering a managed catalog with admin controls sitting on top.

The tradeoff is that this pulls Droid further into a full delegation model. As one review put it, the result is an agent that feels less like a coding assistant and more like a programmable colleague you can leave running overnight. How comfortable you are letting an agent read across production monitoring, customer feedback, and financial planning in a single session will decide whether you want that.

Availability and pricing

Connectors and Personas are live now inside Factory, reachable through Settings → Connectors, or by asking Droid to connect an app in chat. There is no separate SKU: they ship as part of the existing plans. Factory offers five tiers with no free plan: Pro at $20/month, Plus at $100/month (roughly 5x Pro usage plus Droid Computers), and Max at $200/month (roughly 10x Pro usage and early feature access). Business and Enterprise remain custom-priced with SSO, SAML/SCIM, audit logging, and zero data retention.