Skip to main content
Roomote is designed to act like a high-agency teammate inside the workflow your team already has. It is not an IDE, a local copilot, or a desktop app. It is a shared cloud worker that is most at home in Slack, where teammates can ask questions, assign work, and review updates from the conversations they already use. Roomote also works from GitHub, Linear, and the web dashboard, but Slack is the primary day-to-day surface for most teams.

​
Shared engineering work

Most natural-language work starts as a general Roomote task. The recommended first path is to mention Roomote in Slack with a scoped ask. Use it for implementation, debugging, investigation, small refactors, test fixes, documentation updates, planning, and codebase questions. Good handoffs include:
  • the outcome you want
  • the repository, environment, or Slack thread context Roomote should use
  • links to related issues, pull requests, logs, or screenshots
  • any constraints, such as “do not change the API contract” or “keep this behind the existing feature flag”
  • how you want the result returned, such as a plan, explanation, patch, or PR

​
Work that starts itself

Some work starts from repository events instead of a manual prompt. For example, Roomote can review pull requests, follow up on PR comments, suggest improvements from feedback, or help with merge-conflict and repository maintenance work when the relevant automation is enabled. Admins can manage these settings in the Roomote dashboard under Settings.

​
Where work starts

Slack is the recommended surface for the first task after setup because it makes Roomote visible inside an existing team conversation. Use the dashboard when you want to choose the environment directly, inspect task details, review diffs, or continue with a richer task view.

​
How Roomote stays reviewable

Roomote runs in an isolated cloud environment and keeps the work visible. The task view gives your team the transcript, logs, diffs, previews, artifacts, and task metadata before anything ships. For code changes, Roomote should hand work back through normal delivery paths such as a branch, pull request, or reviewable diff. For questions and planning, it should give a clear answer or next step without pretending code was changed.

​
Choosing a workspace

In Slack, Roomote can suggest the right workspace and ask for confirmation when needed. When you start from the dashboard, choose the environment yourself or use Auto when you want Roomote to route the task. Linear can also suggest a workspace from issue context. For more detail, see Environments.