All pages
Docs · AI features
Reporting bugs and requesting features
Send a bug report or feature request straight to the people who build TRMNLY.
You need to be signed in to trmnly.dev. On the Mac that's Settings →
Account; on Linux and Windows run trmnly account login. Each report gets a
reference like FB-1A2B3C4D, and you can see everything you've sent at
trmnly.dev/app/feedback.
From the Mac app
Help → Report a Bug or Request a Feature…
Choose Bug report or Feature request, then write a title and the details. For a bug, the most useful details are what happened, what you expected, and the steps to reproduce it. Include diagnostics is on by default and attaches the app version, build, macOS version and architecture. The exact values are listed under the toggle before you send. No paths, hostnames or file contents are ever included.
Under it, Include recent logs attaches TRMNLY's own error log: the last 30 minutes of its error messages and a stack summary of its latest freeze, so a problem can be traced after it's over. Keys, passwords, email addresses and your home folder are replaced first, the form shows a summary of what will go, and Show the log in Finder opens the file. It's on by default for a bug report only when error reporting is on (and only while Include diagnostics is on); untick it to leave the logs out.
Attaching the agent conversation
When the problem is something the agent did, tick Include the current agent conversation. It's off unless you tick it, and greyed out when the front window's Agent sidebar has no chat. Ticking it shows what will go: the chat's title, how many messages, and the size. The conversation is sent as text — your messages, the agent's replies, and each tool it ran with its input and result. Images and files in the chat are not sent. Anything that looks like a key, token or password is replaced first. Chats over 2 MB lose their oldest messages, and the window says how many. Only TRMNLY administrators can open it. It's deleted with your account, or sooner if you email the report's reference to will.schulz@aw3.tech.
The Agent sidebar's gear menu has a shortcut: Report a problem with this conversation… opens this window for a bug, with that chat already ticked.
The agent's feedback_submit tool and trmnly feedback never attach a
conversation.
If you aren't signed in, the window says so. Copy Report puts the text on your clipboard so nothing you wrote is lost.
From an agent or MCP client
Ask the agent, or Claude Code connected to TRMNLY over MCP, to report it. For
example: "file a TRMNLY bug: the Files sidebar goes blank after switching
projects". It calls feedback_submit:
| Input | |
|---|---|
kind |
bug or feature |
title |
one line |
body |
the details |
include_diagnostics |
default true |
On the Mac this goes through the approval prompt, so you see the report before
it leaves your machine. The same tool is on trmnly-core-mcp (Linux and
Windows) and on the cloud workspace's MCP endpoint. Reports sent through MCP
record the client's name (for example "Claude Code").
This is different from wish_submit, which turns a request into cards on
your own project board. feedback_submit goes to the TRMNLY team.
From the command line (macOS, Linux, Windows)
trmnly feedback bug "Files sidebar goes blank" --body "Steps: open a project, switch to another…"
trmnly feedback feature "Group tabs by project" --body "…"
some-command 2>&1 | trmnly feedback bug "Crash in some-command" --stdin
--no-diagnostics leaves out the version, OS and architecture. --json prints
one line, {"ok":true,"reference":"FB-…"} or {"ok":false,"error":"…"}.
On Linux and Windows, --include-logs adds the end of TRMNLY's log file to the
details: at most 8 KB, with keys, tokens, email addresses and your home folder
replaced first. It's off unless you pass it. (The Mac keeps its logs in the
system log, so the flag isn't available there.)
Error reports (Linux, Windows, trmnlyd, the CLI)
Like the Mac app, the GTK app's core, trmnlyd and the trmnly CLI send
trmnly.dev a short report when something goes wrong: an error the core logs, a
store it can't read or write, the app's window not answering for more than four
seconds, or — with trmnly crash-report send — the summary of a crash (what
failed, the version, and where in the program as offsets; never the crash dump
itself). Reports go only from a machine signed in with trmnly account login;
otherwise they wait on disk until it is. Secrets, email addresses, your home
folder and ids are removed before anything is sent.
trmnly diagnostics # on or off, what's waiting, where the log is
trmnly diagnostics off # stop sending (or set TRMNLY_ERROR_UPLINK=0)
trmnly diagnostics send # send what's waiting now
trmnly crash-report # list crash dumps, and which were sent
trmnly crash-report send # send the newest one not sent yet
trmnly diagnostics off also deletes the reports waiting to be sent, and
running TRMNLY processes stop sending within a few seconds — no restart.
Warnings and errors are also written to logs/trmnly.log (logs/trmnlyd.log
for the daemon) under ~/.local/state/trmnly (%LOCALAPPDATA%\TRMNLY on
Windows), two files of at most 2 MB each, so you can attach them to a report.
From the web
Sign in at trmnly.dev and choose Feedback in the header. The page has the same form, plus the list of reports you've sent.
Limits
Up to 20 reports per account per hour. Titles are cut at 200 characters. Details over 20,000 characters are clipped, and the report says how much was left out.