Something not behaving? Write to us.

Email support@justrytrace.app. That reaches us directly.

It helps enormously if you include your Trace version (shown in /config), your macOS version, and what you expected to happen instead of what did.

Trace reads Slack as you, so it can only see channels you are a member of. If a channel is bound but producing nothing, the usual cause is that you are not in it — the channel picker marks those you’re not in it. Join it in Slack and Trace will start reading it.

The other cause is that no channel is bound yet. Binding happens per project: open the project and run /slack-connect.

• The reaction has to be yours. A teammate reacting to a message is their bookmark, not your record, and Trace deliberately ignores it.
• The channel has to be bound to a project at the time you react. Bind it first with /slack-connect, then react.
• Reactions added while Trace was closed are not picked up. Trace re-reads what you have reacted to when it starts, but treats it as history rather than a fresh instruction — otherwise every old pin would arrive at once.

Many companies require an administrator to approve any app before it can be installed. If your Slack workspace does, the first person to connect Trace will see a request-to-install screen rather than a consent screen, and an admin has to allow it. Everyone after that just approves it for themselves.

Some workspaces are stricter still and only permit apps listed on the Slack Marketplace. Trace’s listing is in progress; until it is published, those workspaces will refuse the install outright and there is nothing we can change on our side to allow it.

Disconnect and connect again from /config → Read a Slack channel. That re-authorizes cleanly and is the fix for almost every credential problem. If it recurs, tell us — that is a bug and we want it.

Your record lives on your own Mac and we cannot see it — which also means we cannot recover it for you. See the privacy page for exactly what that covers.

Mail support@justrytrace.appwith “security” in the subject and we will come back to you quickly. Please give us a chance to fix it before publishing.