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.

An environment is the workspace configuration Roomote uses when it runs a task. It tells Roomote which repositories to clone, what services to start, what environment variables are available, and what guidance it should follow. This is what turns Roomote from a generic coding tool into something grounded in your actual product.

​
How the first environment is created

During onboarding, you pick the repository or repositories for the first environment and add any setup guidance you already know. Roomote then starts an environment setup task that figures out how to run the app locally and prepare the workspace for future tasks. The setup task is meant to produce a working environment Roomote can reuse. If it cannot finish, onboarding keeps your repo selection and guidance so you can adjust the input and try again.

​
What to include

Add enough context for Roomote to start productively:
  • repositories and the default branch to use
  • setup commands, package manager expectations, and tool versions
  • services such as databases, caches, queues, or local APIs
  • environment variables and secrets required for local development
  • named preview ports for web apps or APIs so Roomote can open a live preview
  • instructions that are specific to this workspace
  • links or notes for docs, logs, ticket systems, or other connected tools when relevant
Environment changes apply to new tasks. Running tasks keep the workspace they already started with.

​
When to create multiple environments

Use separate environments when work needs meaningfully different setup. Common examples:
  • one environment per product surface, such as web app, API, or worker
  • one environment for a monorepo service with heavy dependencies
  • one staging-style environment with extra credentials
  • one lightweight environment for code review, questions, and investigation

​
Make verification possible

Roomote works best when the environment lets it prove what changed. Include the commands and services needed to run tests, start the app, and open previews. For UI work, configure preview ports so teammates can inspect the result without pulling the branch locally.

​
Agent guidance

Environment guidance should be concrete and durable. Prefer instructions like “run pnpm test --filter @acme/web before changing web routes” over broad preferences that apply to every repository. Use organization-level guidance for cross-team rules, and environment guidance for workspace-specific rules.