# Public Remote Backlog > Publishes a project's backlog as a feedback portal for clients, users and teammates. - Area: Desktop, mobile and web - Plans: All plans - Last checked against the product: 2026-09-20 - Web page: https://agentsroom.dev/docs/public-backlog ## What it does Publishes a project's backlog as a feedback portal for clients, users and teammates. They write to you (a bug, an idea, a question), vote "I need this too", comment, follow tickets and see what is received, in progress and done. Every submission lands on the same board your agents execute from, so a client report becomes an agent run with the client's own words as the prompt. Reporters are kept informed by email (and, on AgentsRoom's own board only, by a message in their AgentsRoom conversation): work started, prioritized, not planned, shipped, team replies; notifications for a shipped fix can wait for the next release and are grouped per person. ## Where to find it - Backlog header: **Public backlog** opens the **Share Backlog** modal (create, then settings); a second button opens the public page in your browser; **Client feedback** filters the board to tickets sent by users and counts unread replies. - The portal: `agentsroom.dev/backlog/`, also reachable at `.backlog.agentsroom.dev`, with the tabs Ideas (when public ideas exist), Received, In progress and Done. - Feedback surfaces for your users: the portal, an embeddable widget (`agentsroom.dev/embed/widget.js` with `data-backlog=""`), and the AgentsRoom Chrome extension. - Shared on X, LinkedIn or Slack, every page of the portal (board, ticket, ideas, idea) shows a preview card with the board name, its address and its logo or brand colour. ## How to use it 1. Open the Backlog and click **Public backlog**. Choose the **Public URL** slug and the **Visibility**: **Public** (indexable), **Unlisted** (link only) or **Restricted** (invited people, each with an AgentsRoom account). Click **Create public backlog**. 2. Share the link, drop the widget on your site, or point users to the Chrome extension. 3. A submission appears on your board as a client ticket with a **Client feedback** section: reporter, URL, browser context, chosen topic, translation of the original report when the board has a working language. Drag it to In Progress like any ticket: the reporter is told work started. 4. Talk to the reporter from the ticket's conversation block; their replies arrive as comments and unread ones are counted on the card. **Prioritize** emails them that the ticket moved up. **Won't fix** asks for a reason and tells them it is not planned. 5. When the ticket reaches Done, the **Notify Client** modal opens: pick **Notify at next release** (default, one grouped message per person when a new version ships) or **Notify now**, a **Resolution message** (**Standard**, **Idea implemented**, **Bug fixed**), and an optional message. On your board the **Delivery** is **Send email**: the reporter and the followers get the branded resolution email. The **Send chat message** option (a message in the reporter's AgentsRoom conversation, signed by the AgentsRoom team) is only offered on AgentsRoom's own backlog; since 2026-09-18 any other board's notification is delivered by email, whatever channel was requested. Publish an internal task on the portal with **Publish on the public backlog** in the ticket modal. Merging duplicate client tickets keeps every reporter subscribed and redirects the old public links. A reporter of a closed ticket can mark it retested or send it back with **Still not fixed** (up to three times): the card shows "Reopened ×N" and the agent's prompt says a previous fix was rejected. ## Settings All of them live in **Share Backlog** (the public backlog settings button in the Backlog header), per board, not in the global Settings: - **Remote backlog enabled**, **Accept new tickets**, **Enable upvotes**, **Show what is done publicly** (adds the Done tab). - **Notify client when ticket is done**, **Team hourly digest**, **Team email on every client comment**. - **Client-facing status labels**, **Invited collaborators** (restricted mode), **Default agent** for tickets that arrive unassigned. - **Credit reporters in commits** ("(reported by Name)" in commits made from user-reported tickets). - **Submission form**: **Quick** or **Detailed**, and the **Topics offered** list (empty = the question is not asked). - **Idea Radar tab** and **Where submissions land** (bug, question, feature routed to the Backlog or to the Idea Radar). - **Working language**: translate incoming reports for you and your agents; the reporter keeps seeing their own words. ## Agent tools (MCP) - `backlog_notify_done`: park the "your bug is fixed" notification until the next release ships. On your board it reaches the reporter by email; the in-app chat message exists only for AgentsRoom's own backlog. - `backlog_comment`: reply on a ticket thread; a comment on a client ticket reaches the reporter. - `backlog_publish_mockup`: attach a mockup to a feedback ticket (see [Ticket Scoping](https://agentsroom.dev/docs/ticket-scoping.md)). - `report_issue`: files a report about AgentsRoom itself on AgentsRoom's own public board, with your confirmation. ## Providers All providers, no difference: a client ticket runs on the agent you assign or on the board's Default agent. ## Mobile Present for the owner: client tickets on the phone's board with the Client feedback details, the original report and its translation, prioritize, decline with a reason, the Notify client sheet with the same templates, merge and clean up. The reporter side is the phone's **Your feedback** thread (see [Feedback & Support Chat](https://agentsroom.dev/docs/feedback-and-support-chat.md)). ## Limits - The widget does not work on a restricted backlog (by design, it would bypass the invitation). - Portal rate limits: 10 tickets per hour per reporter, 20 comments per hour, one upvote per email and no vote on your own ticket. Up to 3 images of 4 MB per ticket or reply. - Automatic client emails are delayed 10 minutes (cancelled if the ticket moves back), capped at 3 per recipient per day, and carry an unsubscribe link. - A reporter can send a closed ticket back three times at most. - Renaming the slug keeps a 30 day redirect from the old address. - Routing an incoming client ticket to the best agent and a sized model with AI needs the Pro plan; Free uses the default agent. - Attachments sent through the support chat are not shown on the public page and are deleted from the server once the ticket is done, unless you allow it on the ticket. ## Common questions - **Can my clients vote?** Yes, "I need this too" on public and unlisted boards, one vote per email address, and you can switch upvotes off. - **Do both reporters get notified after a merge?** Yes, everyone who reported an absorbed ticket becomes a follower of the surviving one, and their old links redirect. - **Will a user receive one email per shipped ticket?** No, tickets shipped in the same release are grouped in one localized digest per person. - **How does restricted access work?** Only invited emails get in; each signs in with an AgentsRoom account matching that email, and removing them cuts access immediately. - **Why is there no "Send chat message" option in Notify Client?** That channel posts in the reporter's AgentsRoom support conversation in the name of the AgentsRoom team, so it only exists on AgentsRoom's own backlog. Your reporters are notified by email, which needs no AgentsRoom account. - **The client wrote in a language I do not read.** Set a Working language on the board: reports are translated for you and your agents, the reporter keeps their words. ## Related - [Backlog Task Board](https://agentsroom.dev/docs/backlog-task-board.md): the board every submission lands on. - [Idea Radar](https://agentsroom.dev/docs/idea-radar.md): where feature requests can land instead, to gather votes. - [Ticket Scoping](https://agentsroom.dev/docs/ticket-scoping.md): turn a fuzzy request into a mockup before building. - [Feedback & Support Chat](https://agentsroom.dev/docs/feedback-and-support-chat.md): the reporter's Your feedback thread. - [Chrome Extension](https://agentsroom.dev/docs/chrome-extension.md): file a ticket from any web page. - [Contributor Status](https://agentsroom.dev/docs/contributor-status.md): how reporters are credited.