Repository navigation
Releases
v0.5.1
A small fix release for the dashboard.
Fixes
- Dates no longer break the issue, Triage and list pages. The server and the browser rendered times and dates in different time zones, so React failed to hydrate those pages (error #418 in the console). Dates and times now render the same on both sides, then show in the reader's own time zone.
- The public page's address is checked in the browser again. Browsers rejected the field's
patternand skipped the check; a value such as-shopnow shows as invalid before it is sent.
Upgrade
No new setting, no migration. Pull the new image and restart:
docker compose pull && docker compose up -dImages: ghcr.io/lilybarberou/tattle:0.5.1 (also :0.5, :0 and :latest), for amd64 and arm64.
v0.5.0
A security release. It closes a way to take over a pending invitation, keeps secrets and admin-level settings away from plain members and API tokens, makes rate limits hold behind proxies, stops webhooks and AI calls from being pointed at the server's own network, and keeps reporters' data out of logs, webhook copies and chat mentions. It also lets apps turn the widget's collectors off, and brings an accessibility pass, faster pages and a large test suite, end-to-end included.
A few behaviors change: invitation links sent before this version must be sent again, TRUST_PROXY counts proxies (a CDN in front of nginx or Traefik needs 2), and plain members keep fewer rights. See Behavior changes and Upgrade.
Security
- Invitations can no longer be taken over. A pending invitation was granted to whichever account had the invited email. Invitation links now carry a signed token; creating the account and joining need the link and the invited email. Better Auth's unused invitation endpoints are turned off.
- API tokens only work with MCP. Tokens (
tat_…) were also accepted by the dashboard's internal endpoints, which did not enforce read-only tokens. They now work with/api/mcponly. - Secrets and admin-level settings are for owners and admins. Plain members no longer receive the identity secret, webhook secrets or full Slack and Discord URLs, and can no longer change verified identity, webhooks, the project's name, allowed sites or public page, revoke other people's tokens, or delete issues and reports.
- Rate limits hold behind a proxy. With
TRUST_PROXY=true, Tattle now reads the address your proxy added toX-Forwarded-For, not the first one. Ingest counts a request before reading its body, and the GitHub webhook limit also applies across projects. - Webhooks and AI base URLs cannot reach the server's own network. The address is checked on the connection itself, not only before it; network errors only show their kind.
- One email address per recipient. A reporter's or voter's email that is not one plain address is never mailed.
- No links in the logs. Without SMTP, unsent emails (password resets included) were logged with their link.
- A saved AI key is only used with the base URL it was typed for.
- GitHub sync: an open pull request links issues only when its author has access to the repository; at most 10 issues per pull request.
- Widget and React Native SDK: console logs are scrubbed of credentials before they are sent, serialization is bounded, and clicks inside rich text editors no longer record what was typed.
- Hardening: reporters' text stays plain in Slack and Discord (no mentions); MCP flags issues written by end users as
untrustedUserContent; an MCP project slug shared by two of your organizations is refused instead of picking one; Better Auth's organization delete endpoint, which left screenshots in storage, is turned off; admin-only actions answer 403. - Dependencies: Better Auth 1.7.25 (OAuth provider fixes), and overrides that clear the three moderate advisories reported by
pnpm audit.
Privacy
- Webhook deliveries keep their copy of a report only while they may be sent. Finished deliveries drop it, a sweep every 6 hours clears older copies and gives up deliveries pending for more than a day, the delivery log keeps 30 days, and erasing a reporter covers their pending deliveries. Nothing to run by hand.
- New: turn the widget's collectors off, and filter reports.
collect: { console, network, steps }andbeforeSend(report)in the web widget (data-collecton the script tag) and the React Native provider. Defaults are unchanged.
What's new
- Keyboard and screen reader pass on the dashboard: "Skip to content", report logs as a real tab widget, named landmarks and pickers, focus kept through confirmations, a visible focus ring on every field, focusable code blocks, a phone menu whose close button no longer covers "New issue", and better contrast in the widget's "My reports".
- Real "not found" and error pages, with a way back; a wrong issue number is a 404, also when you navigate to it inside the app. A stale parameter in an address opens the page on its default.
- Invitations: owners and admins can show a waiting invitation's link again, and opening a link with another account says so.
- Erasing someone's data asks "Keep them?", with the focus on keeping.
- Faster pages: fonts served by Tattle itself (no request to Google), files served compressed (
/widget.js82 → 24 kB), a lighter browser bundle, and the bundled Caddy compresses pages too. - The issue list stays fast on issues reported thousands of times (about 7 s → 40 ms on 300,000 reports), and Triage shows the oldest reports first even beyond 200.
- Widget documentation for pages with a strict Content-Security-Policy.
- For contributors: an end-to-end Playwright suite on local containers (
pnpm test:e2e, also run in CI), server function and API route tests, andtest:coveragein each package.
Fixes
- A refused assignee no longer leaves a half-created issue behind.
- Merging two issues into each other at the same time can no longer hide both.
- A portal address already taken answers "This address is already taken." instead of an error 500.
- Triage shortcuts no longer fire while a menu is open.
- After creating the first account and signing out, the login page shows "Sign in".
- When S3 cannot delete a screenshot, Tattle keeps the reference and retries.
- The retention purge handles up to 20,000 reports per run.
- SMTP connections time out (15 s to connect, 30 s of silence).
- Issue titles, descriptions and comments have the same length limits through MCP as in the dashboard; pull request URLs must be http(s).
- Two first reports sent at once from a React Native app share one device key, so both show in "My reports".
- The browser's theme color follows light mode again; pages have a meta description.
Behavior changes
- Invitation links sent before 0.5.0 no longer work. Cancel and send pending invitations again. People who already have an account join by opening the link.
TRUST_PROXY: with two proxies in a row (CDN + nginx or Traefik), setTRUST_PROXY=2; otherwise visitors behind the same CDN node share one rate limit and get 429s. One proxy, the bundled Caddy or a hosting panel: nothing to change.TRUST_PROXYnow accepts a number of proxies.- Plain members can no longer see secrets, manage verified identity, webhooks, the project's name, allowed sites or public page, revoke other people's tokens, or delete issues, reports and projects. Promote people to admin where needed.
- API tokens are refused (401) outside
/api/mcp. - Without SMTP, password reset is not possible.
- MCP writes follow the dashboard's limits (title 200 characters, description and comment 20,000), and MCP answers carry
untrustedUserContentandorganizationfields. - The webhook delivery log keeps 30 days, and deliveries pending for more than 24 hours are marked failed.
- GitHub sync: a pull request from someone without access to the repository moves its issue only once merged.
- Widget and SDK console logs are scrubbed; very large logged objects are cut after 2,000 values; clicks inside rich text editors are not recorded.
- Invalid ingest requests count against the per-IP limit. Changing the AI base URL asks for the key again.
Updates
- Better Auth 1.7.20 → 1.7.25,
@aws-sdk/client-s33.1166 → 3.1169,undici7.30.1 (new, MIT). - Nitro 3.0 beta → 3.0 release candidate (the server runtime).
- TypeScript 6 → 7 (native compiler), Biome 2.4 → 2.6, esbuild 0.25 → 0.28, lucide-react 0.577 → 1.73,
@types/node22 → 24, dotenv 17 → 18 (dev only);drizzle-kitmoves to dev dependencies. - IBM Plex fonts from
@fontsource(OFL-1.1) instead of Google Fonts. - Node 24 and pnpm 10.15 unchanged.
Upgrade
Before upgrading:
- Back up the database and the screenshots (see Backups in
docs/SELF-HOSTING.md). - Note the invitations still waiting (Members → Waiting to join): you will send them again.
- Count the proxies in front of Tattle (see the table below).
- On a large instance, count reports (
SELECT count(*) FROM report;): migration 0008 rebuilds an index on that table, and new reports wait while it runs (about 1.5 s per 300,000 reports). With several million, plan a quiet moment.
Then:
docker compose pull && docker compose up -dThe app applies migration 0008 on start. No new required setting.
After upgrading:
- Send pending invitations again (cancel, then invite).
- If a CDN sits in front of your proxy, set
TRUST_PROXY=2and restart. - If members you do not fully trust had access to your projects, rotate the identity secret (then update your backend) and recreate webhook endpoints whose secret matters; if admins you do not fully trust had access, rotate the AI provider key.
- With the bundled Caddy (
--profile https), download the newdeploy/compose.yamlto get page compression, thendocker compose --profile https up -d. - If your proxy sets a Content-Security-Policy,
font-src 'self'is now enough.
| Setup | TRUST_PROXY |
|---|---|
| Bundled Caddy, or one nginx, Traefik, Caddy or hosting panel | true (unchanged) |
| A CDN (Cloudflare…) in front of your nginx or Traefik | 2 |
| A load balancer in front of a panel's Traefik, behind a CDN | 3 (one per hop) |
| Nothing in front (Tattle reached directly) | unset |
Rolling back: set TATTLE_VERSION=0.4.0 and docker compose up -d. 0.4.0 runs on the upgraded database (migration 0008 only replaces an index with a wider one). Set TRUST_PROXY=true again if you had set 2: 0.4.0 only understands true.
Web widget: served by your Tattle server, it updates with it; no snippet change. Pages with a strict CSP: see the widget's README.
React Native apps: rebuild @tattle/react-native from th...
v0.4.0
What's new
- Talk with your reporters, inside your app. The web widget and the React Native SDK get a My reports view: reporters see what they reported, its status in plain words (Received, Planned, In progress, Fixed, Won't fix), the team's replies, and can answer or add details. A badge on the launcher tells them when the team replied.
- On the issue page, each report has its own conversation. Reply to reporter is visible to them; internal comments never are.
- A reporter whose email is known gets the team's replies by email, with a link to read and answer the conversation in a browser, no account needed.
- By default a reporter finds the reports sent from their device. Turn on identity verification in project settings and pass
hash(HMAC-SHA256 of the user id, computed by your backend) toidentify(): they then find their reports on every device. See the widget READMEs. - Agents can answer with the new
reply_to_reporterMCP tool, and webhooks get amessage.createdevent.
- The steps before a bug. Reports now carry what the user did before sending them: pages visited, clicks, fields changed (never their content; password and card fields are skipped), tab switches. The Steps tab shows them in one timeline with console errors and failed requests. Add your own with
addBreadcrumb(); in React Native,trackNavigation(navigationRef)records screens from React Navigation and Expo Router. Agents get the timeline inget_report. - Releases and regressions. Pass
releaseto the web widget (ordata-releaseon the script tag); React Native sends your app's version and build. Issues show which releases they were seen in, the issues list filters by release, and a fixed bug that gets a report from after its fix is reopened and marked as a regression. - Duplicate suggestions. Each new report is compared with the project's most similar issues. When one looks like the same problem, Triage and the issue page show Looks like #12, with Merge and Not a duplicate. Nothing is merged automatically.
- Without AI, only near-identical wording is suggested, and nothing leaves your server.
- With your own key (Agents & API → Duplicate suggestions: Anthropic, OpenAI, or any OpenAI-compatible server such as Mistral, OpenRouter or Ollama), a model judges each report against the candidates. The README lists exactly what is sent. The key is encrypted with
BETTER_AUTH_SECRET; changing that secret means entering the key again.
- GitHub: merged pull requests close their issues. Turn it on in project settings → GitHub and add the webhook to your repository. A pull request is linked to an issue by its
pr_url, or by writingFixes Tattle #12(or Closes, Resolves) in its title or description. Opening it moves the issue to In review; merging it into the default branch moves it to Done and tells the reporters. Off by default. - Emails for what needs you, and nothing else. Each person picks theirs under their name → Notifications, and every email has a one-click unsubscribe:
- a reporter answered (to the assignee, or whoever replied, or the admins), grouped over about 10 minutes;
- an issue was assigned to you;
- a fixed bug came back;
- a daily Triage digest, only on days with something new (on for owners and admins, at
TRIAGE_DIGEST_HOUR, 8 UTC by default); - for admins: your AI key stopped working, or a webhook keeps failing.
- Reporters can stop the emails about one of their reports.
- Overview page. Each project has an Overview: reports per day over 30 days, the Triage inbox, open issues by status, the most reported issues, the most voted requests, and the median time to resolve.
- Markdown. Issue descriptions and comments are rendered as Markdown, with a Write / Preview editor. Raw HTML is shown as text and images are not loaded. Reporters' messages stay plain text. Editing a description now has a Save button instead of saving when you click away.
- Widget animations.
theme.animationpicks how the widgets appear and disappear:"pop","slide","fade"or"none", or enter and exit separately with their own duration and easing. - More React Native styling. The theme takes a title font and size, colors for the chosen type, and
accentEdge, a solid edge under the send button.
Security
- AI base URLs and webhook URLs on the server's own network (loopback, private and link-local addresses, cloud metadata) are refused, at save time and before each request, and redirects are not followed. Set
ALLOW_PRIVATE_URLS=trueto allow them, for example for Ollama or a webhook receiver on your network. - The AI settings never send the provider's raw answer back to the browser.
- Request bodies are cut off as soon as they exceed their limit, chunked ones included.
- Logs carry only the kind of an error, never email addresses, report content or SQL parameters.
Upgrade
docker compose pull && docker compose up -dThe app applies six migrations on start. New optional settings in .env: ALLOW_PRIVATE_URLS, TRIAGE_DIGEST_HOUR, GITHUB_LIMIT_PER_IP, REPORTER_READ_LIMIT_PER_IP, REPORTER_MESSAGE_LIMIT_PER_IP (see the settings table in docs/SELF-HOSTING.md). AI_ALLOW_PRIVATE_URLS also works as a name for ALLOW_PRIVATE_URLS.
Websites that load widget.js from your server get the new widget with the upgrade (about 27 KB gzipped, up from 22). React Native apps need the SDK rebuilt from this release; it has new optional peers for remembering the reporter between launches: expo-secure-store or @react-native-async-storage/async-storage, and expo-crypto.
Image: ghcr.io/lilybarberou/tattle:0.4.0 (also :0.4, :0 and :latest), for amd64 and arm64.
v0.3.0
What's new
- Make the widget look like part of your app. The web widget and the React Native SDK used to take only an accent color. They now take your app's design from the code that embeds them, so users barely notice it is a separate tool:
theme: every color (accent, text on accent, background, text, muted text, border, secondary surface, error colors, backdrop), with optional overrides for dark mode, the font, and the corner radius of fields and of buttons (999gives pill buttons).colorScheme:"light","dark"or"system". An app with its own theme switch can drive the widget with it.strings: replaces any text of the widget, in any language.
- Web widget extras.
- The widget reads
--tattle-*CSS variables from your page, so you can map your design tokens in CSS and let your own dark mode selector switch them. fontFamily: "inherit"uses your page's font.cssadds your own CSS inside the widget's Shadow DOM, for anything the theme does not cover.Tattle.setTheme()andTattle.setColorScheme()change the look at runtime without losing what the user typed. The script tag acceptsdata-color-scheme.
- The widget reads
- React Native extras.
fontFamilyBoldtakes the bold file of your custom font, since Android ignoresfontWeightwith most of them.
Without a theme, both widgets look exactly as before, and accentColor still works. See "Match your app's design" in the web widget README and the React Native README.
Upgrade
docker compose pull && docker compose up -dNo migration or setting to change. Websites that load widget.js from your server get the new widget with the upgrade. React Native apps need the SDK rebuilt from this release.
Image: ghcr.io/lilybarberou/tattle:0.3.0 (also :0.3, :0 and :latest), for amd64 and arm64.
v0.2.1
What's new
- See which version is running. Open the menu under your name, at the bottom left of the app: it shows the version, linked to its release notes.
/healthnow answers with it too ({"ok":true,"version":"0.2.1"}), which uptime monitors can check after an upgrade. Images built from themainbranch showmainand the commit.
Fixes
- MCP clients were always told the server ran version 0.1.0. They now get the real version.
Upgrade
docker compose pull && docker compose up -dNo migration or setting to change.
Image: ghcr.io/lilybarberou/tattle:0.2.1 (also :0.2, :0 and :latest), for amd64 and arm64.
v0.2.0
What's new
- Reports from mobile apps. Tattle now takes bug reports and feature requests from iOS and Android apps. A mobile report shows the app version, the device model, the system and the screen it came from, instead of the browser and page. Discord and Slack messages and what agents read through MCP show the same details. Phone screenshots are shown at a size that keeps the logs in view.
- Ingest API reference. docs/INGEST-API.md documents the one request every report goes through, with examples in Swift, Kotlin and Flutter. Any app or backend can send reports with it.
- React Native and Expo SDK.
packages/react-nativeadds the same button and form as the web widget to React Native and Expo apps (Expo Go included): a screenshot of the current screen that users can annotate or remove, console logs, uncaught errors, network requests, and the device and app version. It is not on npm yet: its README explains how to install it from the repository. - Install instructions per platform. The project settings page now has a Website tab and an API tab with a ready-to-run
curlrequest for your project.
Security
- Allowed sites no longer block mobile apps. A project's allowed sites now only apply to requests that carry an
Originheader. Browsers always send one and pages cannot change it, so websites are still checked as before. Native apps send none, and were refused until now. A script outside a browser could always send anyOriginit liked, so this removes no protection: the list stops other websites from using your key, not scripts.
Internal
- The Docker image builds its JavaScript natively instead of under arm64 emulation, which took minutes and could hang. Releases now stop after 30 minutes.
Upgrade
docker compose pull && docker compose up -dNo migration or setting to change.
Image: ghcr.io/lilybarberou/tattle:0.2.0 (also :0.2, :0 and :latest), for amd64 and arm64.
v0.1.2
What's new
- Favicon and app icons. Tattle now has its own icon in browser tabs (light and dark), on the iOS and Android home screen, and a web manifest. The browser chrome takes the colour of the app frame.
- Install instructions: script tag only. The npm tab is gone from the project settings and the widget README, since
@tattle/widgetis not on npm yet.
Security
- Tattle can no longer be shown inside another site's frame. Every response now sends
Content-Security-Policy: frame-ancestors 'none'andX-Frame-Options: DENY, so no site can frame the OAuth consent page and trick a signed-in user into allowing an agent. This also applies to the public feature-request portal.
Internal
- Fixed a test that failed about one run in 16, and the test suite now runs from a path that contains spaces.
Upgrade
docker compose pull && docker compose up -dImage: ghcr.io/lilybarberou/tattle:0.1.2 (also :0.1, :0 and :latest), for amd64 and arm64.
v0.1.1
Fixes
- Hosting panels: the container no longer shows as unhealthy. Some panels (EasyPanel, Coolify…) set a
PORTvariable on every app, often to80. Tattle listened on that port, but its health check still called port 3000, so the panel saw an unhealthy container and stopped sending it traffic. The health check now followsPORT. - The self-hosting guide now covers
PORTon hosting panels, with a troubleshooting entry.
Upgrade
docker compose pull && docker compose up -dImage: ghcr.io/lilybarberou/tattle:0.1.1, for amd64 and arm64.
v0.1.0
The first release of Tattle: self-hosted bug reports and feature requests for your web app, built to be triaged by AI agents.
What's in it
- Widget. A button in your app, added with one script tag. Users report a bug with an annotated screenshot, or suggest an idea. Console logs, JS errors, network requests, device info and the signed-in account are attached automatically. About 20 KB gzipped, French and English, light and dark.
- Tracker. Projects, a Triage inbox, and issues with status, priority, labels and assignee. Duplicates are merged with their reports.
- For agents. An MCP server on
/api/mcp, reached with OAuth from your own client (Claude Code, Cursor…) or with an API token for bots. Plus signed webhooks. - Discord and Slack. New reports, status changes and comments posted to a channel.
- Public feature requests. An optional portal where visitors vote and suggest ideas.
- Privacy tools. Find, export and erase everything about one person, and automatic retention for screenshots and logs.
Security
- The first account is the admin, and creating it takes a setup code printed in the logs, so nobody else can claim a fresh server. Sign-up then closes; the rest of the team joins by invitation.
- Passwords found in known data breaches are refused.
- Reports and sign-in attempts are rate-limited per IP.
Install
Tattle ships as a Docker image for amd64 and arm64. Follow the self-hosting guide, or run:
mkdir tattle && cd tattle
curl -fsSLO https://raw.githubusercontent.com/lilybarberou/tattle/main/deploy/compose.yaml
curl -fsSL https://raw.githubusercontent.com/lilybarberou/tattle/main/deploy/.env.example -o .env
# fill in .env, then:
docker compose up -dImage: ghcr.io/lilybarberou/tattle:0.1.0.