Why Tink Never Runs Commands Without Asking

Automated remediation sounds great in a pitch deck. "AI that fixes your servers automatically!" In practice, it's terrifying.

Restarting a service during peak traffic. Cleaning up a directory that turned out to be important. Applying a config change that breaks something downstream. The failure modes of automated remediation are unbounded.

Tink's Approach: Supervised Fixes

Tink takes a different approach. When Tink identifies an issue and has a fix, it:

• Explains the problem and the root cause
• Shows you the exact command it wants to run
• Explains what the command does and why
• Waits for you to approve, modify, or skip
• Logs the outcome regardless of what you choose

The Unexpected Benefit

There's a secondary benefit we didn't expect: Tink teaches you. Every fix session is a mini lesson in server administration. You learn what commands do, why they work, and when to use them.

Over time, you're not just fixing problems — you're building knowledge. The goal isn't to replace your judgment. It's to augment it.

Trust Should Be Earned

Automation should be earned trust, not blind faith. That's why Tink starts in supervised mode and lets you gradually increase autonomy as you build confidence in the system. You're always in control.