Bug: Tailscale node list still shows, even when disconnected from Tailscale.
Feature Request: Public IP address in addition to Tailscale node IP address.
isConnected state becomes stale between timer polls
TailscaleWidget.qml mixes UI, timers, Processes, and logic with no separation
Clipboard path uses fragile sh -c string construction
Implement i18n/localization for Tailscale plugin strings
Zero test coverage for Process lifecycles, timing, or widget behavior
No structured logging of command execution or results
tailscale binary invoked via PATH with no absolute path or sandboxing
sigh
Why is #52 a thing? Why do we care? What concrete, meaningful checks and actions can we do and then act on reliably? How does our behavior change?
If the tailscale binary is doing…
Timer continues polling after tailscale binary disappears or fails
Don't like this. See issue #11. See your AGENT.md file's discussion of storing state. We explicitly removed this approach to using a binaryAvailable flag, and were opting to instead enter an…
Extract QML-embedded logic into testable JavaScript modules
Add conduct rules for agents.
Add conduct rules for agents.