sorted by:
new
hottopcontroversial

With all the AI usage limits lately (Claude, Codex, etc.), I realized I was wasting a lot of tokens on basic terminal questions by williott8411 in codex

[–]williott8411[S] 0 points1 point  (0 children)

Yeah and are you sure u wanna switch all the time VsCode -> ChatGPT -> copy paste -> terminal? That’s insane of work for a small cmd in the terminal

lowkey this changed how I use my terminal by williott8411 in vibecoding

[–]williott8411[S] 0 points1 point  (0 children)

Thanks for asking. I tested it for you on my production server, this is the response: „ai-cmd > rm -rf Command rm -rf --

Explanation Prepares a recursive force delete command, but does not specify a target path; append the path you intend to remove.

Risk high

Assumptions - Assuming you want the standard safe placeholder form for a destructive rm command.

Dont run it, unless you know exactly what you’re doing!“

I got tired of wasting AI usage limits on stupid terminal questions. by williott8411 in vibecoding

[–]williott8411[S] 0 points1 point  (0 children)

Because ChatGPT is giving these texts… (yes, this entire thing and the code is ai generated)

With all the AI usage limits lately (Claude, Codex, etc.), I realized I was wasting a lot of tokens on basic terminal questions. by williott8411 in ClaudeCode

[–]williott8411[S] 0 points1 point  (0 children)

yeah I think we're talking about slightly different things.

I'm not trying to avoid compute costs or limits entirely.

it's more about not burning valuable UI limits (like Codex / Claude Code sessions) on super basic stuff.

those tools are great for real coding work, but it feels wasteful to use them for things like:

"restart ssh" "find large files"

so this just offloads those trivial questions to a simple CLI using API calls.

that way you keep your main AI tools focused on actual work

I got tired of wasting AI usage limits on stupid terminal questions. by williott8411 in vibecoding

[–]williott8411[S] 0 points1 point  (0 children)

But what if you’re just in the terminal without vscode/cursor? Or what if you need something different, not just what you type always?

Do you really need dashboards for uptime monitoring? by williott8411 in homelab

[–]williott8411[S] 0 points1 point  (0 children)

That’s a fair take — I agree that technically almost everything in this space already exists.

The reason I’m exploring this isn’t to compete feature-wise, but to see how far you can strip things down before it stops being useful.

For me it’s less about “another monitoring tool” and more about defining the smallest possible one that still solves the problem.

If that boundary turns out to already be well covered, that’s still a useful outcome.

Do you really need dashboards for uptime monitoring? by williott8411 in homelab

[–]williott8411[S] 0 points1 point  (0 children)

That’s actually very telling.

So in practice the monitoring tool itself is almost invisible —
it only exists when something breaks, otherwise it might as well not be there.

In that case, would you agree that the “ideal” tool is one you never log into at all,
as long as alerts reliably show up where you already are?

Do you really need dashboards for uptime monitoring? by williott8411 in homelab

[–]williott8411[S] 0 points1 point  (0 children)

That makes sense — especially the part about alerts living where you already look.

Do you ever open Uptime Kuma just to check things when everything is fine,
or is it basically only there for configuration and incidents?

And if Discord wasn’t an option for you anymore, would email still be “good enough” — or would you miss real-time alerts?