Skip to main content

Documentation Index

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

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

The web app is where admins set up Roomote and where reviewers inspect the full task record. Slack, GitHub, and Linear may be where work starts, but the dashboard is where you manage the operating surface and review the detailed evidence.

Home

Use Home to launch a task directly from the web app when you want to choose the environment yourself or start from a prompt instead of an external thread. Home is also where new organizations see setup and onboarding guidance, recent task activity, and prompts to finish key connections such as GitHub or Slack.

Tasks

Use Tasks to review active and completed work across the organization. The task view is the main review surface. It can show:
  • the conversation and follow-up history
  • terminal output and logs
  • artifacts such as plans or reports
  • previews for running apps
  • diffs and PR links for code changes
Read Review a task for the practical review flow.

Settings

Settings is where admins shape how Roomote works for the organization. Members also use it for their own linked accounts and personal profile settings.
AreaWho uses itWhat it controls
PersonalEveryoneProfile details and linked personal accounts
EnvironmentsAdminsRepositories, services, environment variables, and workspace config
Agent GuidanceAdminsShared instructions that apply across tasks
AutomationsAdminsBackground or scheduled Roomote work
IntegrationsAdminsOrganization-level integrations and integration enablement
SkillsAdminsEnvironment-level playbooks and custom skills
VibesAdminsTone and summon behavior that helps Roomote fit your team
TeamAdminsMembers and organization profile settings
Read Agent Guidance, Automations, Skills, and Vibes for the main admin settings that shape how Roomote behaves after the first environment is working.

A practical order for new admins

If you are just getting started, this order usually works well:
  1. connect GitHub and Slack
  2. create the first environment
  3. review the environment setup task
  4. run a small first task
  5. add the next integration or automation only after the first path feels stable

When to stay in the dashboard

Prefer the dashboard when you need to:
  • inspect the full task output
  • compare logs, artifacts, diffs, and previews
  • continue or resume an existing task
  • manage environments or organization settings
  • review work that started in Slack, GitHub, or Linear