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.

A task is a single unit of Roomote work. It may start from Slack, GitHub, Linear, or the web dashboard, but the task view gives your team one shared place to inspect what happened.

​
Task view

The task view gives you the working context for a run:
  • conversation history and Roomote updates
  • terminal and runtime logs
  • generated artifacts
  • code diffs
  • previews for running apps
  • task metadata and links back to Slack, Linear, or GitHub when available

​
Verification

Roomote is most useful when it can show its work. For implementation tasks, look for:
  • commands, tests, or checks it ran
  • logs or errors it used to make decisions
  • screenshots or live previews for UI changes
  • a diff or pull request for code changes
  • a clear explanation when something could not be verified

​
Continuing work

You can send follow-up instructions while a task is active. If a task has completed and Roomote has a restorable snapshot, a follow-up can resume from that prior workspace instead of starting over. Good follow-ups are specific:
  • “Apply the second option and add a regression test.”
  • “Use the existing settings card pattern instead of adding a new component.”
  • “Open a PR with the fix.”
  • “Explain the tradeoff before changing code.”

​
Reviewing output

Before you merge changes, review the diff and the verification Roomote ran. Roomote can move quickly, but your normal review process still matters.
For implementation work, ask Roomote to include the tests or validation it ran in the final task message.

​
Multi-person tasks

Different teammates can run separate tasks in parallel. Teammates can also join the same task conversation when the work needs shared context, for example when a PM clarifies requirements and an engineer reviews the implementation plan.