Open your profile
Use Profile to update account details such as your name, email, avatar, and security settings. These settings affect your own Roomote account. They do not change deployment membership, environment access, or integration setup for the rest of the team.Set a password
If you signed in through a communications or source-control provider, you can select Set password to add email-and-password sign-in to the same Roomote account. After setting a password, you can update it from Personal Settings.Link your accounts
Use Linked Accounts to connect your personal identity for tools your deployment has enabled. You may see rows for:- your source-control provider
- your communications provider
- Linear
- user-linked integrations such as docs, issue trackers, databases, or analytics tools
Manage personal integrations
Use Personal integrations to add, edit, or revoke API-key integrations that only your Sessions and coding tasks can use. Roomote keeps the key server-side; agents receive an opaque reference or a task-scoped substitute rather than the key itself. An integration-key approval created from a Session also appears here when you choose Only me. Deployment-wide integration keys instead appear under the administrator’s Settings → Integrations page. If an administrator changes a shared integration to owner-only access, Roomote moves it to that owner’s Personal integrations card. See Integration keys for approval methods, security boundaries, task behavior, and self-hosting options.Manage personal MCP servers
Use Personal MCP servers to add remote MCP servers that only your Sessions and coding tasks can use, for example a service you authorize with your own account. Roomote reaches the server through its proxy and keeps headers and OAuth tokens server-side. A server you ask Roomote to connect privately in a Session appears here too. Open a server to edit it, manage which tools agents may use, or share it with everyone in the deployment; Roomote then moves it to Settings → Integrations. See Custom MCP servers for authentication options and security boundaries.Why personal linking matters
Personal linked accounts help Roomote act with the right context. Depending on the integration, linking can help Roomote:- associate your chat, source-control, or Linear identity with the Roomote task
- use your user-scoped connection for tools that require individual authorization
- route follow-up activity back to the right person or thread
Adjust the app
Personal Settings also include app preferences such as:- Color Theme for light, dark, or system-defined appearance
- Mind Reader Mode to expand LLM thoughts by default in task conversations; you can still collapse or expand individual thought messages
- Narration Mode for a more streamlined task conversation view
- How to work with me for private personal instructions and conversational learning
Try personalized Home suggestions
Home suggestions is a deployment-wide experiment. When an admin enables it under Settings > Experimental, Roomote uses up to five of your recent successfully completed and ingested task memories to prepare short ideas for what to do next in the Home composer. Suggestions are prepared in the background when possible and rotate until you focus the composer; press Tab to accept the current suggestion. Only your visible, manually initiated work is eligible. Roomote excludes other members’ work, automations, system tasks, hidden or deleted tasks, incomplete runs, and memories that have not finished ingesting. If Memory or helper-model generation is unavailable, Home keeps the standard non-personalized suggestions. An admin can turn the experiment off to stop personalized suggestion requests for every member.Continue peer conversations
Peer conversations is a deployment-wide experiment controlled by admins under Settings > Experimental. When enabled, eligible human replies in established Slack or Discord session threads can continue reaching Roomote after someone mentions another participant. Roomote is instructed to stay quiet around peer discussion unless Roomote is addressed directly or the context clearly calls for its response. Direct Roomote mentions work normally with the experiment on or off. The experiment does not monitor whole channels. Discord supplies messages from the established thread and resolved user mentions. Telegram is not included: bot privacy settings can prevent ambient group messages from reaching Roomote, and Telegram sessions are isolated per linked sender. Microsoft Teams is also not included because its channel sessions are isolated per linked sender; webhook delivery and delegated Graph history are not a single shared, owner-bound session signal.Personalize how Roomote works with you
Use How to work with me for durable context and preferences that can help Roomote work with you in the future. This can include recurring responsibilities, workflows, tools, constraints, and collaboration patterns, along with your preferred name, language, formality, answer length, use of examples, directness, update frequency, or accessibility and presentation preferences you choose to share. These instructions apply to conversations with you; they do not silently rewrite code or customer-facing deliverables. Learn from conversations is on by default. Roomote may save durable work context or a preference you state explicitly and may form modest, revisable style preferences from repeated behavior. It does not save one-off task details or facts about other people as personal context. Turning learning off stops new automatic updates but keeps the instructions already shown in the text box active. Reset clears both edited and learned instructions. A reset does not rebuild them from older conversation history. Roomote captures each participant’s personalization when they first speak in a conversation and keeps that private snapshot for their later turns in the same conversation. New preferences stated in a message still guide that request and are saved for future conversations, but they do not rewrite the current conversation’s snapshot. Edits and resets in Personal Settings likewise apply to new conversations, or to a participant who has not spoken in the current conversation yet. Personalization follows the trusted account associated with the current speaker on supported chat surfaces and with the person who requested a task. In a shared thread, Roomote adapts its conversation to the current speaker while preserving the original requester’s task requirements when they conflict. Personalization is encrypted at rest and is not available to other members or admins through Roomote’s normal UI or API. It is excluded from shared task transcripts, summaries, memory, and ordinary tool output. It remains subject to the deployment operator’s infrastructure access, backups, and retention policies. Roomote does not use public-web or LinkedIn enrichment for this feature.Common issues
- A linked account is missing. Ask an admin to enable the integration from Settings > Integrations.
- A task uses the wrong identity. Check that the relevant account is linked and that you started the task from the expected chat, source-control, or dashboard user.
- You cannot link an account. Try again after confirming pop-ups and redirects are allowed for the Roomote app.