Sessions are shared
Start a session from Slack, review the results in the web dashboard, resume it from the CLI. All clients see the same sessions, the same history, and the same outputs. This means:- A product manager requests a change in Slack
- An engineer reviews the diff in the web dashboard
- Another engineer picks up the session from their terminal to iterate
Web dashboard
The web dashboard is the control tower for all agent activity across your organization. What you see:- Active and recent sessions, who started them, and what triggered them
- Repo, branch, and current status for each session
- Preview links for running environments
- Approve/reject controls for pending actions
- Full conversation history
- Real-time agent activity as work happens
- File diffs showing exactly what changed
- Terminal output from the agent’s environment
- Preview environment for visual review
Slack
Slack is the fastest way to start work and collaborate with agents. Mention the bot, describe the task, and iterate in a thread. For the full breakdown of Slack capabilities — starting sessions, notifications, thread-based collaboration, triage, and channel configuration — see Slack.Terminal and CLI
Engineers can spin up cloud sessions directly from the terminal. The CLI is a lightweight remote agent launcher — start sessions, watch progress, and collaborate on active work without leaving your editor workflow. Sessions started from the CLI are visible in the web dashboard and Slack. Your teammates can watch your session, and you can watch theirs.See CLI Getting Started for installation and setup.
Triage workflows
When agents produce work, someone needs to review it. Proliferate supports triage from every surface:Review diffs
See exactly what changed in the web dashboard’s diff view before approving.
Check previews
Open preview URLs to see the result in a running environment before merging.
Approve or reject
Approve actions from Slack threads or the web dashboard. Agents wait for sign-off on write-level actions.
Provide feedback
Reply in the Slack thread or web session to request changes. The agent picks up the context and iterates.
Getting your team started
Start small
Pick one workflow and define what success looks like before expanding. A single automation running well builds more trust than five running poorly.By team
Engineering teams — Start with Sentry error triage, GitHub issue response, or Linear ticket first-pass. These are high-frequency, well-defined tasks where agents reduce interruptions without losing control. Product teams — Great starting points are Slack-based requests (“add a tooltip to the settings page”), preview link reviews, and Intercom feedback triage. Keep requests specific and outcome-focused. Marketing teams — Landing page tweaks, copy updates, and UTM or analytics event fixes. Provide exact copy and acceptance criteria, and use preview links to confirm before merging.Keep it collaborative
- Review together: Use Slack threads and the web dashboard to discuss agent output as a team
- Share previews: Send preview URLs to stakeholders before merging changes
- Tight permissions first: Start with conservative action permissions, then expand as your team builds confidence
