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 Roomote session. 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

Roomote acts autonomously on authorized work when the next step is clear, but that autonomy does not give it authority over people. Unless you explicitly ask it to coordinate teammates, Roomote leaves human ownership open instead of assigning work, setting deadlines, or presenting proposed commitments as accepted.

​

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. The same review is available on demand. Mention Roomote on a pull request and ask for a review, or ask in any session, and the Review Code pipeline runs as a task inside that session and reports back when it finishes. A pull request opened by a Roomote task stays part of the session that asked for the work. Mentions on that pull request join that session rather than starting a new one, and Roomote answers both on the pull request and where the session lives.

​

Where work starts

Chat is the recommended surface for the first session after setup because it makes Roomote visible inside an existing team conversation. Use the dashboard when you want to continue a session or open delegated task details such as logs, diffs, and previews.

​

How Roomote stays reviewable

Roomote runs delegated work in an isolated sandbox and keeps it visible. The session holds the conversation and reports; each task view exposes its transcript, logs, diffs, previews, artifacts, and execution 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, the session decides whether a request needs a workspace and which environment fits, and it says so before delegating. Reply in the same thread to redirect it. When you start from the dashboard, choose the environment yourself or leave the selector unselected to let the session decide. A Linear agent session works the same way: the session reads the issue and chooses the environment before delegating. If a request is ambiguous, the session asks a clarifying question in the same thread before it delegates, so you can name the environment or repository in your reply. If the deployment’s inference provider is unavailable, Roomote says so in the thread instead of silently doing nothing; ask an admin to check the provider connection in that case. For more detail, see Environments.