Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.newmote.dev/llms.txt

Use this file to discover all available pages before exploring further.

This guide follows the onboarding flow for a new organization. The goal is to get Roomote connected to GitHub and Slack, then let Roomote help configure the first development environment it will use to verify work.
1

Open the Roomote app

Sign in to app.roomote.dev. If you are creating a new organization, follow the setup prompts in the dashboard.
2

Install the GitHub app

Connect GitHub from Settings or the setup flow. Choose the repositories Roomote should be allowed to access.
3

Connect Slack

Connect Slack so your team can ask Roomote questions, assign work, and review suggestions from the place work already happens.
4

Pick repositories for the first environment

Choose the repository or repositories needed for the first environment. Start with something simple, such as a marketing site or internal tool, so Roomote can prove the workflow quickly.Add any setup guidance Roomote should know, such as package manager expectations, commands, services, credentials, preview ports, or “watch out for this” notes.
5

Let Roomote configure the environment

Roomote starts an environment setup task for the selected repos. It works out how to run the app locally, what dependencies and services are needed, and how to make verification possible.
6

Optionally connect Linear

After environment setup, connect Linear if your team wants to assign issues to Roomote and get updates in your project tracker. You can skip this during onboarding.
7

Start the first task in Slack

Mention Roomote in a Slack channel or DM and ask for something scoped. Starting in Slack helps the team see Roomote in the workflow they already use.You can also launch from Home in the dashboard when you want to choose the environment directly.
8

Review the result

Open the task view to follow progress, inspect terminal output, review code changes, open previews, and continue the conversation. Code-changing work should still go through your normal review process.

​
A good first task

Start with something scoped and easy to verify. The best first tasks clear a real annoyance without requiring a long product meeting. In Slack, a first ask might look like: 
@roomote look at the marketing site repo and explain why the local preview is failing
  • “Find why the login test is failing and propose a fix.”
  • “Add a small loading state to the settings page.”
  • “Review this PR for regressions.”
  • “Explain how the billing webhook flow works.”
  • “Look at this Linear issue and draft an implementation plan.”
Include the repository, branch, file path, issue link, or pull request link when you already know where the work should happen.

​
Optional integrations

After the first environment is ready, start in Slack. GitHub is useful for PR review and follow-up, and Linear is useful when your team tracks engineering work there, but Slack is the best first task surface.

GitHub

Review PRs, follow up from comments, and keep repository work in GitHub.

Slack

Mention Roomote in channels and continue task threads.

Linear

Start and follow agent work from Linear issues.