AgentsRoom Help
- Desktop app
- All plans
What it does
An assistant that answers questions about AgentsRoom itself: what a feature does, where a setting lives, how to set something up. It reads the product knowledge base shipped with the app and, when it runs on your own CLI, your actual configuration too, so the answer matches your machine rather than a generic manual. Depending on the engine it can also change a setting or open the right screen for you when you ask.
It is not a coding agent and it never touches your project. It answers in the language of your question.
When you ask for something the product cannot do, it says so, names the closest thing that exists, and offers in one line to file the request on the public backlog. It never files anything without your yes.
Where to find it
- Title bar: the Help button (its bubble is titled AgentsRoom Help), in the right-hand group next to the personal assistant and your account, on the projects home and inside a project. Its logo carries the service status dot (green, orange, red).
- Projects home, search bar: the third cell Help ("Ask how AgentsRoom works") opens the same bubble. The other two cells, Projects and Build, are search modes.
- Inside two dialogs, an Ask for help button (the AgentsRoom logo, in the header of Add agent when you create a real agent, and at the top of Agent Teams): it opens the same bubble over the dialog, with a question about that step already typed for you.
- At the very bottom of the bubble, Or reach us directly: Guide, Feedback, Bug or idea, Community, Status. The Community link opens the same panel as the Community button of the top bar (both called Chat before 1.184.0; the link kept the old name until 1.185.0).
- Settings > Defaults > Product assistant: which engine answers.
The bubble opens by itself once, a moment after the first-launch walkthrough, and never again. It always stays in the main window: unlike the personal assistant and the chat, it has no "Detach into a window" button.
How to use it
- Click Help in the title bar and type your question ("e.g. can I use two Claude accounts?"), then Ask.
- Watch what it is doing under the answer: Reading the knowledge base…, Reading your settings…, Changing a setting…, Opening the screen…, Filing the request….
- Ask it to act when the engine allows it: "turn that on for this project", "open that screen". An explicit request is carried out; its own idea is proposed first and waits for your yes.
- The conversation survives closing the bubble. Start a new conversation clears it.
- Nothing left to ask? Use the tiles under Or reach us directly to reach a human or the public board.
Help on the step you are in: in Add agent or Agent Teams, click Ask for help. The bubble opens next to the form (the form stays where it is, nothing is lost) with a ready-made question ("Help me create an agent: which role, provider and settings should I pick for what I need?" or "Help me build a team of agents: which roles should follow each other, and how do I connect the steps?"). Edit it or send it as is: nothing is sent until you click Ask. The assistant knows which dialog you are in, so "this screen" means that dialog.
Settings
assistantProvider(global, Settings > Defaults > Product assistant): the engine. A CLI with a headless mode (claude, codex, grok, opencode, copilot, mistral, antigravity, kimi),"cloud"for the AgentsRoom fallback, or empty to follow your default provider and fall back to the cloud when that CLI is missing. Only Claude Code can act; the row tells you which case you are in.assistantIntroShown(global, no UI): whether the bubble already opened by itself once. Set it back to false to see the intro again.
Agent tools (MCP)
The knowledge base is not reserved to the assistant: every agent in your projects can read it.
product_help_index: the list of feature fiches with what each one covers.product_help_get: one fiche in full, by slug.product_help_search: the fiches that match a question.
The assistant itself also uses settings_list / settings_get / settings_set, ui_open (a fixed list of screens it may open) and report_issue (a feature request or bug on AgentsRoom's public board, only after your yes).
Providers
Claude Code answers and acts (settings, opening screens). Codex, Grok, OpenCode, Copilot, Mistral, Antigravity and Kimi answer only, on their own read-only flags. A CLI with no headless mode is refused with a message pointing at the setting. With no usable CLI on the machine, the AgentsRoom cloud answers instead: it explains and gives the exact click path, and leaves the change to you.
Mobile
Not on the phone. The mobile companion reaches the team through its chat, opened from the people button next to the AgentsRoom logo, at the top of the Projects screen (with the unread badge), and the guide and support links live there.
Limits
- On a CLI engine, each question runs on your subscription and counts toward its quota. Nothing is sent to AgentsRoom on that path.
- The cloud fallback is capped at a few questions a day per address; past it, the message points at installing a CLI. Only your question and the interface language are sent.
- When your CLI cannot answer (not signed in, usage limit reached, stopped before replying), the cloud answers that question instead and a note under the answer says why the CLI was skipped and how to get it back (sign in to the CLI in a terminal, wait for the limit to reset, or pick another CLI in the setting).
- The cloud engine cannot read your configuration, change a setting or open a screen.
- It knows the product, not your code: questions about your own repository belong to an ordinary agent.
- A feature shipped without its knowledge-base entry is invisible to it; it will say it does not know rather than guess.
Common questions
- Does it cost me anything? On a CLI it uses your own subscription quota. The cloud fallback is free and rate-limited.
- Is my code or my project sent anywhere? No. On a CLI everything stays local; on the cloud only your question and the UI language leave.
- Why can it not change my setting? Only Claude Code can act. Pick it in Settings > Defaults > Product assistant, or apply the path it gives you.
- It said a feature does not exist. Ask it to file the request: it opens a ticket on the public backlog and hands you its URL.
- Where did "Feedback & support" go? It became this button. Its five destinations are the tiles at the bottom of the bubble.
- I am stuck in the agent or team form. Click Ask for help in the dialog: the bubble opens on top of it with the question already written, and the form keeps what you typed.
- Can I open Help in its own window? No, the Help bubble stays in the main window. The personal assistant and the chat can be detached, Help cannot.
Related
- In-App Guide: the step-by-step tour, one of the tiles at the bottom of the bubble.
- Feedback & Support Chat: reaching a human, and following what you reported.
- Public Remote Backlog: where a filed request lands.
- Welcome Chat: the Build mode of the same search bar.
- AgentsRoom MCP: the connector the knowledge-base tools belong to.
- Assistant (personal assistant): the other title-bar assistant, which works in your projects instead of answering about the product.
- Customize Agents: the Add agent dialog where the Ask for help button sits.
- Agent Teams: the Agent Teams dialog, the other place with that button.