Public Remote Backlog

  • Desktop, mobile and web
  • All plans

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.

Video (1 min 22): Public backlog under your own brand, shown in the real app. A client page shows Powered by AgentsRoom, Portal appearance gets a name, a color, a welcome message and CSS, the mention is hidden, and after a reload the page carries the brand and a client's message lands on the board.

Where to find it

  • Backlog header, while the board is not published: Public backlog opens the Share Backlog modal to create it. Once published, the control splits in two: the left half, Public backlog, opens the public page in your browser, and the right half, the settings button (Public backlog settings), opens Share Backlog. Client feedback filters the board to tickets sent by users and counts unread replies.
  • The Share Backlog window of a published board has a search bar on top and sections on the left: Sharing (Public access, Your own domain), Public page (Portal appearance, Permissions, Submission form, Client-facing status labels) and Incoming (Where submissions land, Working language, Default agent, Notifications). The search finds any setting of the window, opens its section and highlights the row.
  • The portal: agentsroom.dev/backlog/<slug>, also reachable at <slug>.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="<slug>"), 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 Development 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.

To put your brand on the page: in the Backlog header, click the settings button next to Public backlog, then Portal appearance in the left column of Share Backlog. Type Name shown to visitors, pick the Brand color, write the Welcome message, open Custom CSS, type your rules and click Save, then switch on Hide the AgentsRoom mention (Custom CSS and the hidden mention need Pro). The name and the message are saved when you leave their field. Reload the public page to see the result.

Signed-in visitors of the portal can keep a message as a private draft with Save as draft in the writing window, then find it under Your drafts on the board to refine, send or delete it later. Nobody else sees a draft, the board owner included, until it is sent. Anonymous visitors keep the automatic draft of their browser only.

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. Since 2026-10-26, until the release that carries the fix is out, the ticket's web page shows "This fix will be in the next version. You can retest it once that update is installed." instead of those two answers, so nobody retests a build without the fix (same on the desktop and the phone).

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.
  • Portal appearance: name, logo, color and welcome message are free on every plan; the hidden mention and the custom CSS are Pro only (since 2026-11-07). Every plan sees them; without Pro they are greyed, and the Pro only label (or a click on the row) opens the upgrade dialog. A board that already used them keeps them and can switch them off, not add new ones:
    • Name shown to visitors (displayName, 60 characters, empty = the name from the address; @, <, >, invisible characters and "AgentsRoom" are refused).
    • Project logo, Brand color (brandColor), Welcome message (welcomeMessage, Markdown).
    • Hide the AgentsRoom mention (hideAgentsRoomBranding, off by default, Pro only): gone from the page, the widget, the social image and emails to visitors, which are then sent under the board's name.
    • Custom CSS (customCss, 20 000 characters, Pro only): colors, borders, fonts and spacing only. Stable classes: .rb-portal .rb-header .rb-main .rb-title .rb-card .rb-inset .rb-btn .rb-btn-primary .rb-btn-secondary .rb-field .rb-chip .rb-footer. Refused: url(), @import, attribute selectors, content, position, display, opacity, negative margins. Never applied on sign-in screens. A board with custom CSS loads no outside image, including one a visitor put in a message.
  • Your own domain (publicBacklogDomain over MCP), Pro only: every plan sees the setting, without Pro the field is locked and the Pro only label next to the title opens the upgrade dialog. A subdomain such as feedback.yourcompany.com. Add the CNAME and TXT records shown, then Check now. Status: Waiting for DNS, Working, Stopped working.

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).
  • settings_get / settings_set with scope: "project": publicBacklogDomain connects the board's own domain (Pro), answers the DNS records to publish and the status, checks it when written again, and removes it with null.
  • report_issue: files a report about AgentsRoom itself on AgentsRoom's own public board, with your confirmation.
  • settings_get / settings_set with scope: "project": publicBacklog reads and changes everything in the Share window except the logo (only the fields passed change, the first write needs a slug and publishes the board, null switches it off and keeps its slug reserved); publicBacklogUsers is the list of people allowed on a restricted board (a new or changed address receives an invitation by email at once).

Providers

All providers, no difference: a client ticket runs on the agent you assign or on the board's Default agent.

Mobile

Portal appearance and the board's own domain are set from the desktop app, there is no Share window on the phone. Links on the phone follow the board's own domain once it works.

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).

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 20 images of 4 MB per ticket or reply, about 22 MB in total.
  • 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, and does not change the name shown to visitors if you typed one.
  • Your own domain must be a subdomain (feedback.yourcompany.com, not yourcompany.com), one per board, Pro only. Emails still leave from [email protected], under your board's name.
  • 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

  • How do I put my brand on the public backlog? The page where clients report bugs can carry your name, color and welcome message on every plan; with Pro, also your own CSS and domain, without the AgentsRoom mention. In the Backlog header, click the settings button next to Public backlog, then Portal appearance, and reload the public page. Video: https://youtu.be/hIgiZJ_XHPA
  • Is there a video that shows it? Yes, a little over a minute, filmed in the real app: https://youtu.be/hIgiZJ_XHPA
  • 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.
  • Can I white-label the backlog? Yes, in Share Backlog > Portal appearance. Your name, logo, color and welcome message are free on every plan; custom CSS, hiding the AgentsRoom mention and your own domain are part of Pro (since 2026-11-07, a board that already used CSS or the hidden mention keeps them). AgentsRoom stays on the sign-in and invitation screens, because the account people create is an AgentsRoom account, in the sending and reply addresses of emails, and in the address until you connect a domain.
  • Why can't I type in Your own domain? It is part of Pro. The setting stays visible on every plan, and the Pro only label next to its title opens the upgrade dialog. Name, logo, color and welcome message are free; custom CSS and hiding the AgentsRoom mention are Pro too, with the same label.
  • Why can't I sign in directly on my own domain? Whoever controls a domain's DNS can read what is sent to it, so no password is typed there and no account session lives there. The visitor signs in on the board's backlog.agentsroom.dev address and comes straight back, with a session valid on that board only.
  • What happens if I remove my domain's DNS record, or my Pro plan ends? Within a day the status reads Stopped working, you get an email, and links and emails go back to your AgentsRoom address, which never stopped working. When Pro ends the domain keeps being served, you can no longer change it, only remove it.
  • Can I write any CSS? No: anything that could fetch something from elsewhere could read what a visitor types. The field tells you which line is refused and why.
  • A reporter sent the same message several times. Will I get duplicates? No, since 2026-10-19: an identical submission from the same email within two minutes gets the answer of the first one, and the send button locks while sending. A feature request routed to the Idea Radar no longer vanishes from the form: it shows "Got it, thank you", so the reporter knows it arrived.
  • 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.