How Roomote works

Roomote is designed to act like a shared teammate inside the workflow your team already has. It is not an IDE, a local copilot, or a desktop app. It is a reviewable cloud agent that is most at home in chat, where teammates can ask questions, assign work, and review updates from the conversations they already use. Roomote also works from your source-control provider, Linear, and the web dashboard, but a chat surface such as 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 chat 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 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, or help with merge-conflict resolution when the relevant automation is enabled. Admins manage these in the web app under Automations — see Automations.

​

Where work starts

Chat 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 sandbox 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 hands work back through normal delivery paths such as a branch, pull request, or reviewable diff. For questions and planning, it gives a clear answer or next step without pretending code was changed.

​

Choosing an environment

In chat, Roomote can suggest the right environment and ask for confirmation when needed. In Slack, Telegram, and Discord, you can use the confirmation controls or reply naturally to accept, cancel, or correct that suggestion. 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 an environment from issue context. If a Slack request is ambiguous, Roomote shows the environment picker so you can choose where the task should run. If automatic routing is temporarily unavailable, the picker includes a warning instead of silently falling back. Choose an environment to continue; if the warning persists, ask an admin to check the deployment’s inference provider. For more detail, see Environments.