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.

Slack is part of the core setup path because it is the main way most teams interact with Roomote. Teammates can start work from a channel or direct message without opening an IDE or learning a new workflow. Use Slack for questions, investigations, small fixes, bug reports, review follow-up, and quick handoffs from teammates who already have the context in a thread.

​
Setup

1

Connect Slack

In Roomote, connect your Slack workspace during onboarding or from Settings later.
2

Invite Roomote to a channel

Add the Roomote app to the channels where teammates should be able to start tasks.
3

Link your account

If Roomote asks you to link your Slack identity, follow the link so Slack messages can be tied to your Roomote account.

​
Starting a task

After your first environment is ready, start your first real task in Slack. Mention Roomote with the work you want done: 
@roomote investigate why the checkout preview is failing and propose a fix
Roomote may suggest a workspace and ask you to confirm before it starts. Once the task is running, the Slack thread stays connected to the task view in Roomote.
Starting in Slack makes the first task visible to teammates and demonstrates the workflow Roomote is designed for: normal team conversations that turn into reviewable engineering work.

​
Good Slack handoffs

  • include the customer report, log snippet, screenshot, PR, or issue link already being discussed
  • say whether you want an answer, a plan, or code changes
  • keep one task per thread when possible
  • open the Roomote task view when you need diffs, logs, artifacts, previews, or private input

​
Continuing a task

Reply in the same Slack thread to add context or ask for follow-up work. Roomote keeps lightweight updates in Slack and uses the task view for the detailed transcript and review surface.

​
Tips

  • Ask for plain-English explanations when you do not need code changed.
  • Ask for a plan before implementation when the work is ambiguous.
  • Use Slack to bring non-engineers into the workflow without making engineers change their local setup.