You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An icon. Embedded in the Windows executable as a six-frame .ico (16 through 256), so it shows in
Explorer, the taskbar and file properties. Set only for Windows targets: Linux and macOS binaries have nowhere
to put one, and setting the property unconditionally makes those publishes warn about a resource they cannot
use. The release bundles carry assets/rtfq.png because the bundled README references it.
Changed
RTFQ now expands as Remote Tool For Queries. Same four letters, safe on a shared screen, and a truer
description besides: reaching data sources on a machine you cannot otherwise get to is the whole pitch.
no token now says where the value comes from. "pass --token or set RTFQ_TOKEN" is accurate and useless
in the case people actually hit — standing on the server box, where the config's secrets are exported and the
client variable is not, with nothing to suggest the two want the same string.
Documentation
The approvals walkthrough gained the three things a field report showed were missing: that the agent cannot
approve its own write and no tool will ever let it; that nothing notifies you, with both answers
(--watch for one operator, a webhook for a team); and when to turn approval on at all — production,
where a small in-bounds wrong write is what no structural gate catches, rather than a dev database, where
signing off every scratch write is how people end up removing the gate everywhere.
Says where to run rtfq approvals --watch: it is a client, not a server component, so your own machine is
usually the right place. Several people can watch at once — the first answer wins and the request leaves
everyone else's queue.