Hosted OAuth
Workspace admins click Connect Slack, approve the Recursiv-hosted app, then choose org, project, agent, brain, and optional channel context in Recursiv.
No Slack secrets, manifests, Slack CLI, API keys, or proof scripts.Slack integration
Prompt apps and agents from the thread where the idea starts.
Recursiv for Slack turns everyday team conversation into a shared AI development surface. Ask for an app, agent, or project follow-up in Slack, and Recursiv runs the real project-room workflow behind it.
# product-build
Prompt-driven development
Slack
Events API
Recursiv workflow
Project + agents
Why it matters
AI development becomes multiplayer.
Today, a capable AI agent usually lives inside one operator's IDE or terminal. Recursiv for Slack moves that power into the shared workspace without giving up the infrastructure that makes work real: auth, projects, sandboxes, deploys, agents, memory, billing, integrations, and governed approvals.
Setup modes
Hosted install first. Enterprise controls when needed.
Most workspaces connect through Recursiv-hosted OAuth and never touch Slack app credentials. Advanced and developer paths stay separate for teams that require ownership or local operator tooling.
Customer-owned app
Enterprises that need Slack app ownership can generate a guarded manifest and point every callback back to the Recursiv API.
For teams that require their own Slack app record.CLI/API setup
Internal teams can use Slack CLI or API manifest setup for local tunnels, callback checks, and proof harness runs.
For local builds, staging, and operator diagnostics.Architecture
Slack is the surface. Recursiv is the system of record.
The live bot path is thread-first and bot-token based. Recursiv autopilots trusted first-party work, while high-impact policy gates still protect deploys, external writes, billing, destructive actions, and new tool grants.
Slack
Prompt
Mentions, slash commands, files, and high-impact approval clicks arrive through signed Slack webhooks.
Ingress
Verify
Recursiv verifies the signature, dedupes the event, normalizes the thread, and binds it to an org/project.
Recursiv
Run
Project creation, agent setup, sandbox work, deployment, memory, approvals, integration grants, and audit logs stay in Recursiv.
Delivery
Reply
Progress and final results return to the original Slack thread through the bot token and retryable delivery outbox.
Live bot
Built for everyday prompting. It sees the current Slack thread, runs a Recursiv workflow, and posts concise progress back where the request started.
Optional ETL
Built for searchable company context. Optional admin-enabled Slack ETL is off by default and syncs only selected public channels.
How to use it
Ask in Slack. Get the working object back.
Build an app
@recursiv build a donor CRM with auth, saved contacts, CSV import, and a polished dashboard.
Recursiv creates the project, starts the app workflow, and returns the project room and preview link.
Create an agent
@recursiv create a support triage agent for this project. Give it Slack and Linear context.
Recursiv configures the agent, tools, memory seed, scope, and existing Recursiv integration grants.
Ship a change
@recursiv deploy the latest version and tell me what changed before it goes live.
Recursiv runs the deploy path, summarizes the diff, and asks for approval only when policy requires it.
Permission model
Useful by default. Explicit when broad context is needed.
The integration should not imply workspace-wide Slack access. The default path is deliberately narrow; broader indexing is a separate admin choice.
Setup path
Start with one channel. Expand only after proof.
Install the hosted Recursiv Slack app, choose a default Recursiv organization and project brain, invite the bot to a test channel, and run the first prompt. Advanced customer-owned manifests and developer Slack CLI setup stay separate from the default hosted path. ETL remains off until an admin selects public channels for indexing.