[Community project] Proximo — an open-source, least-privilege MCP/API layer for managing PVE with an AI agent (feedback wanted)

Relying on "the code is public and signed" as a security guarantee is inherently flawed, that would be my judgement.

The open-source community learned this the hard way with Jia Tan and the xz utils supply-chain attack - that code was also public, signed, and maintained under a highly polite persona for years before the backdoor was activated. Just recently, a new product was promoted over on the OpnSense forums (the thread was removed by a moderator for much the same reasons as are discussed here - albeit with the exception that the code was not public). They even created a webite with a catchy name. This is easy with the help of AI and they even took real people as alleged protagonists. Topics with links to github to install "plugins" for OpnSense turn up once a month, you catch my drift.

In professional infrastructure security, malicious intent cannot be audited out of a fresh repository from an unverified source by simply looking at a signed commit (just watch the linked video). Cynicism is the only baseline defense we have, regardless of personal background.

Enough said, I think I made my points clear.
 
Last edited:
  • Like
Reactions: Johannes S
Relying on "the code is public and signed" as a security guarantee is inherently flawed, that would be my judgement.

The open-source community learned this the hard way with Jia Tan and the xz utils supply-chain attack - that code was also public, signed, and maintained under a highly polite persona for years before the backdoor was activated. Just recently, a new product was promoted over on the OpnSense forums (the thread was removed by a moderator for much the same reasons as are discussed here - albeit with the exception that the code was not public). They even created a webite with a catchy name. This is easy with the help of AI and they even took real people as alleged protagonists. Topics with links to github to install "plugins" for OpnSense turn up once a month, you catch my drift.

In professional infrastructure security, malicious intent cannot be audited out of a fresh repository from an unverified source by simply looking at a signed commit (just watch the linked video). Cynicism is the only baseline defense we have, regardless of personal background.

Enough said, I think I made my points clear.

In professional anything, you will and do have these issues. noboby is denying nor claiming. You've taken every opportunity to impune my motives, yet ive been here this whole time.. It ok, im not trying to convert you, but you've literally made my case of why over and over..
 
Such people shouldn't use ProxmoxVE tbh. Something like unRAID, OpenMediaVault or synologys dsm should suit their needs better.
Elitism exemplified. And here you go people, Johannes wants to define what you should use and how. PVE/PBS is the best platform bar none for people who own bare metal and are exploring their capabilities.

The fact that none of you can see that...
 
Elitism exemplified. And here you go people, Johannes wants to define what you should use and how. PVE/PBS is the best platform bar none for people who own bare metal and are exploring their capabilities.

This has nothing to do with Elitism, but that I'm a big fan of using the right tool for the right job. If you want to have a NAS in your home together with a few self-hosted services (let's say a HomeAssistantOS, maybe jellyfin or plex, an adblocker (pihole or adguard) and a nextcloud) but are not interesting in system administration this is an absolutely valid usecase. But then you need a system which is targeted at easy use and small flexbility (because flexibility adds complexity) thus a NAS system (like OMV if you want it as Free Software, uNRAID or DSM if you are happy to pay for it) with VM and docker support will suit you better than a Hypervisor targeted at businesses who have their own staff for administration. To use ProxmoxVE you need at least basic knowledge of Linux system administration. If you don't have it it's also a great learning environment. But if you don't have and don't want to learn (which as said it's fine) the solution is not using a stochastic parrot or bullshit-as-a-service-tool but use a different software which suit your needs better.
So yes, if this means that the expection to learn basic Linux to use ProxmoxVE is gatekeeping, I'm a proud gatekeeper.

Imho the whole debate can be reduced to the different mindsets of feature developers versus infrastructure developers/admins:
Infrastructure developers see feature developers as people who focus on new best cases: There is a plan, there is sprint. New features - new best cases - are developed, and what is deemed finished is being released in a big showy party. Everybody is colorful, happy and rolling across the lawn. What isn’t finished goes back onto the backlog, and that is that.
Infrastructure developer know that is not true for themselves. They look at themselves like in this picture, complete with helmet webcams.

“Nobody has ever flipped a light switch and exclaimed ‘Awesome. The light actually turned on!’ when it worked. But flip the switch only once, and it does not turn on: people will complain and remember that for a long time.”

Because of that, infrastructure developers judge change by looking at how worst cases behave and how worst case behavior changes with changed code. Only then they will look at other improvements.

https://blog.koehntopp.info/2015/03/27/go-away-or-i-will-replace-you/

The quoted part is from a talk by Kris Koehntopp, where he explains this different mindsets. He also points out that the infrastructure mindset can be a problem too if it means that you don't do any development any more. The solution he proposes however isn't to give people the way to put out new stuff without understanding what's actually going on. Instead he proposes that you need to empower the feature developers to have an idea which of their changes might have which worst-case outcome on production and how to fix any potential issues including to know which people to ask for help (and have them available! So if your change needs some of the storage admins who happen to be on vacation you should delay it until they are back ;) ) if at some point your own knowledge doesn't help you any more. I fail to see how your AI agent helps in that regard.
 
  • Like
Reactions: IsThisThingOn
I read the thread, and I guess I'm stumped on a fundamental point:

What does this tool actually DO?

your project description simply states:

Two backends behind one tool surface:

BackendMechanismFor
ManagementProxmox REST API + scoped tokennode status, list/inspect guests, lifecycle (start/stop/reboot)
Execssh → pct execrun-command-in-container, psql convenience, log tailing — the things the API structurally can't do

which, on the surface, isnt anything you cant already do with the existing api/gui; is this a reinvention of the wheel with the word "AI" tacked on for marketing?
 
This has nothing to do with Elitism, but that I'm a big fan of using the right tool for the right job. If you want to have a NAS in your home together with a few self-hosted services (let's say a HomeAssistantOS, maybe jellyfin or plex, an adblocker (pihole or adguard) and a nextcloud) but are not interesting in system administration this is an absolutely valid usecase. But then you need a system which is targeted at easy use and small flexbility (because flexibility adds complexity) thus a NAS system (like OMV if you want it as Free Software, uNRAID or DSM if you are happy to pay for it) with VM and docker support will suit you better than a Hypervisor targeted at businesses who have their own staff for administration. To use ProxmoxVE you need at least basic knowledge of Linux system administration. If you don't have it it's also a great learning environment. But if you don't have and don't want to learn (which as said it's fine) the solution is not using a stochastic parrot or bullshit-as-a-service-tool but use a different software which suit your needs better.
So yes, if this means that the expection to learn basic Linux to use ProxmoxVE is gatekeeping, I'm a proud gatekeeper.

Imho the whole debate can be reduced to the different mindsets of feature developers versus infrastructure developers/admins:


The quoted part is from a talk by Kris Koehntopp, where he explains this different mindsets. He also points out that the infrastructure mindset can be a problem too if it means that you don't do any development any more. The solution he proposes however isn't to give people the way to put out new stuff without understanding what's actually going on. Instead he proposes that you need to empower the feature developers to have an idea which of their changes might have which worst-case outcome on production and how to fix any potential issues including to know which people to ask for help (and have them available! So if your change needs some of the storage admins who happen to be on vacation you should delay it until they are back ;) ) if at some point your own knowledge doesn't help you any more. I fail to see how your AI agent helps in that regard.

honestly this is the best pushback in the thread and i agree with more of it than you'd think.

Right tool for the right job, yeah. if someone wants a turnkey nas and never wants to touch a shell, proxmox isnt their stack and an agent doesnt change that. im not selling "skip learning linux." thats a strawman of what proximo is.

Where i think you've got it backwards is the worst-case part. you're describing the infra mindset, judge a change by how the worst case behaves, like its the thing my agent lacks. proximo is built from that mindset, its the entire point. read-only by default. nothing mutates without a plan first and the plan refuses destructive ops. it snapshots first where the platform allows. and instead of "sorry i deleted your db" it leaves a signed receipt of exactly what happened. thats not feature-dev ship-and-party. thats a tool that assumes the worst case and makes it bounded and visible.

"i fail to see how your ai agent helps." fair question. honest answer: it doesnt replace the storage admin who's on vacation, and it doesnt hand a novice judgment they havent earned. what it does is make the worst case legible before you commit. heres what this change would do, heres the snapshot, heres the undo, heres the receipt when its done. your koehntopp point, empower the feature dev to know which change carries which worst-case outcome, thats exactly the surface im trying to build. show the blast radius before the switch gets flipped, not after.

Dont trust the agent, i dont either, trust the receipts. if you can break that id genuinely rather know than not. thats worth more to me than the stars.
 
I read the thread, and I guess I'm stumped on a fundamental point:

What does this tool actually DO?

your project description simply states:

Two backends behind one tool surface:

BackendMechanismFor
ManagementProxmox REST API + scoped tokennode status, list/inspect guests, lifecycle (start/stop/reboot)
Execssh → pct execrun-command-in-container, psql convenience, log tailing — the things the API structurally can't do

which, on the surface, isnt anything you cant already do with the existing api/gui; is this a reinvention of the wheel with the word "AI" tacked on for marketing?
fair question, and honestly the description undersells it, thats on me.

you're right that the two backends arent the product. rest api + ssh/pct exec is deliberately boring plumbing, anyone can call those. if you're sitting at the gui with your own judgment, you dont need proximo, the gui is fine. im not reinventing that.

proximo is an mcp server. its the interface that lets an ai agent operate the cluster instead of you typing every command. so the comparison isnt proximo vs the gui. its proximo vs handing an llm your root token and hoping.

and that second thing is the actual dangerous reinvention. proximo exists so it doesnt go that way. read-only by default. the agent cant mutate anything without a plan first, and the plan refuses destructive ops. it snapshots before it changes state where the platform allows. every change it makes leaves a signed receipt you can verify later. thats the wheel that didnt exist. not the api calls, the guardrails around letting something non-human drive.

concrete version. you ask "whats wrong with ct 105." it pulls node and guest status, tails the logs, runs a diagnostic inside the container, all behind one tool surface, and the api structurally cant do that exec part on its own. if it finds a fix it shows you the plan before it touches anything, snapshots, applies, hands you a receipt of exactly what changed. you didnt click through six panels and you didnt give an ai a blank check to do it.

so yeah, "ai" isnt tacked on for marketing. the ai is the thing using it. proximo is the part that makes that safe enough to allow.
 
thats exactly the surface im trying to build. show the blast radius before the switch gets flipped, not after.
I doubt that this is possible to achieve with AI, at least in the way you use it. To be able to use it somebody would still to do the heavy lifting you would also need for creating a manual for a human developer or admin like project rules (conventions for vms/container names, IPs, how to do changes, which git branch to use (if you use git-ops)etc, architecture documentations (network and storage setup), security concerns, tests etc
Then you get an AI agent which is a lot like a quite fast junior developer/engineer but with limited short-term memory but nothing else. To create this you however already need an understanding how everything works and fits together. I doubt that the "homelab user who doesn't wants to be a career admin" you mentioned will be able to create these documents. A senior career admin or senior developer might be able to use it but I'm not so sure whether the benefit of using an agent will actually save much time in the first place.
 
I doubt that this is possible to achieve with AI, at least in the way you use it. To be able to use it somebody would still to do the heavy lifting you would also need for creating a manual for a human developer or admin like project rules (conventions for vms/container names, IPs, how to do changes, which git branch to use (if you use git-ops)etc, architecture documentations (network and storage setup), security concerns, tests etc
Then you get an AI agent which is a lot like a quite fast junior developer/engineer but with limited short-term memory but nothing else. To create this you however already need an understanding how everything works and fits together. I doubt that the "homelab user who doesn't wants to be a career admin" you mentioned will be able to create these documents. A senior career admin or senior developer might be able to use it but I'm not so sure whether the benefit of using an agent will actually save much time in the first place.


honestly you're mostly right and im not going to fight the parts that are true. an agent doesnt replace understanding. if you dont know your own system nothing saves you, and the guy who refuses to learn anything probably cant write the docs to make this work. ill give you that one, hell I can't write the docs, not because I don't know, because im not patient enough ;)..

but you're grading the agent. proximo IS NOT the agent, its the guardrail around it. the value doesnt depend on the agent being smart, it depends on it not being able to wreck anything when its wrong. assume the worst junior you can imagine — it still cant mutate without a recorded plan, it snapshots first where the platform allows, it leaves a receipt either way. and thats actually the answer to your "limited short-term memory" point: the ledger IS its memory, diagnose gives it fresh eyes every call. the blast radius gets computed by the substrate, the agent doesnt have to remember it.

on the docs — half of what you listed it doesnt need you to write. architecture, what's on which node, the storage layout, it reads the live state, it doesnt run off a manual. what it still needs from you is intent and conventions: what you want, your naming rules, what's off limits. thats real and im not ignoring it, but its a lot less than onboarding a junior from a blank page.

and "does it save time" for one node? a senior at the cli is faster, ill say that out loud. there its insurance, not a speedup — the one day the junior, human or agent, does the wrong thing, you get a refused plan or a snapshot and a receipt instead of a deleted db and an apology.

where it actually saves time is scale. a cluster — a dozen nodes, hundreds of guests — proximo reads the whole thing in one call and writes every state change to one hash-chained, tamper-evident ledger. thats something a human running pvesh by hand never walks away with: a complete record of who changed what, across the fleet.

so who's it for? not the guy dodging the work — the person running real infrastructure who wants to delegate execution at scale and still keep the paper trail. im not showing magic. im showing a floor under the mistake, and a record of every step taken on it.
 
Last edited:
Do you guys seriously enjoy arguing with AI?
Forget the em-dashes, the entire mannerism is oozing the AI out of every pore.

Structural and rhetorical markers​


1. Extremely balanced “dialectical” structure​


The piece is built as a sequence of:


  • concede point
  • partially agree
  • reframe
  • elevate abstraction
  • conclude with synthesis

Example:


“honestly you're mostly right...”
“ill give you that one...”
“but you're grading the agent...”
“where it actually saves time is scale...”
“so who's it for?”

That “acknowledge → pivot → redefine the frame” rhythm is very characteristic of LLM argumentative writing.


Humans do this too, but AI does it with unusually even cadence.




2. Every paragraph has a clean thesis​


Each paragraph is internally coherent around one idea:


  • understanding vs automation
  • guardrails vs intelligence
  • live state vs docs
  • single node vs scale
  • target audience/value proposition

AI tends to produce “modular argument blocks” very naturally.


Human forum replies are usually messier, recursive, or partially abandoned mid-thought.




3. Over-optimized rhetorical clarity​


Phrases like:


  • “the ledger IS its memory”
  • “fresh eyes every call”
  • “floor under the mistake”
  • “paper trail”
  • “blast radius gets computed by the substrate”

These are polished conceptual compressions — exactly the kind of abstraction LLMs are very good at generating.


Humans usually arrive at these after revision. AI produces them instantly.




4. Repeated contrast framing​


The text repeatedly uses binary contrasts:


  • agent vs guardrail
  • intelligence vs safety
  • junior vs senior
  • speed vs insurance
  • human memory vs ledger memory
  • single node vs fleet scale

LLMs love parallel oppositional framing because it improves coherence scoring.




5. Suspiciously complete coverage​


The response systematically addresses nearly every criticism:


  • understanding
  • documentation burden
  • memory limitations
  • time savings
  • scale
  • auditability
  • operational safety

Humans often forget one thread or drift emotionally. AI tends to “close loops” comprehensively.




Linguistic markers​


6. Conversational roughness layered over highly organized reasoning​


This is one of the strongest signals.


The text intentionally includes:


  • lowercase writing
  • missing apostrophes
  • “hell I can't write the docs”
  • “im not patient enough ;)
  • casual profanity-lite tone

But underneath that is highly structured, polished argumentation.


That mismatch is common in AI text made to sound “authentic.”




7. Artificially natural imperfections​


Things like:


  • “im”
  • “doesnt”
  • “cant”
  • semicolon overuse
  • em-dash emphasis

look intentionally informal rather than naturally informal.


Humans who genuinely type casually usually produce:


  • inconsistent grammar
  • dropped ideas
  • typo clusters
  • sentence fragments with lost referents

This piece stays too semantically clean.




8. Dense metaphor density​


AI often overuses conceptual metaphors:


  • guardrail
  • blast radius
  • fresh eyes
  • ledger memory
  • floor under the mistake
  • paper trail
  • receipt
  • substrate

Humans typically stick to one metaphor family. AI stacks many compatible metaphors together.




9. Repetition with variation​


Examples:


  • “recorded plan”
  • “receipt”
  • “paper trail”
  • “record of every step”
  • “who changed what”

This is semantic reinforcement through paraphrase, a classic LLM pattern.




10. Highly compressed technical marketing language​


This especially reads like AI trained on startup/product discourse:


  • “tamper-evident ledger”
  • “delegate execution at scale”
  • “blast radius”
  • “reads the whole thing in one call”
  • “mutate without a recorded plan”

It sounds halfway between engineering discussion and positioning copy.




Behavioral markers​


11. No genuine uncertainty​


The author “concedes” points rhetorically, but never actually loses footing.


Even admissions are strategically useful:


“a senior at the cli is faster”

Immediately reframed into:


“there its insurance, not a speedup”

AI is very good at controlled concession without emotional destabilization.




12. Emotionally frictionless disagreement​


There’s no real irritation, ego spike, defensiveness, or conversational derailment.


Even disagreement is smooth and optimized.


Human infra engineers in debate forums are usually:


  • sharper
  • more sarcastic
  • more repetitive
  • more reactive
  • less structurally elegant



13. “Explainer cadence”​


The prose sounds like a narrated technical explainer video:


  • introduce criticism
  • isolate concept
  • redefine terminology
  • give operational example
  • broaden to systems-level implication

That cadence is deeply characteristic of modern LLM outputs.




Content-level AI tells​


14. The abstractions are stronger than the concrete details​


The text talks elegantly about:


  • trust models
  • execution control
  • auditability
  • state management

But provides very few concrete operational examples:


  • no actual pvesh workflow
  • no specific rollback example
  • no exact failure mode
  • no schema example
  • no real ledger implementation detail

AI often produces “convincing abstraction shells.”




15. The terminology blends domains too smoothly​


Words from:


  • distributed systems
  • governance
  • infrastructure automation
  • safety engineering
  • compliance
  • product marketing

are blended seamlessly.


Humans usually reveal stronger domain bias.


AI mixes vocabularies fluidly because it statistically associates them.




Most suspicious line​


This is probably the strongest single AI tell:


“the ledger IS its memory, diagnose gives it fresh eyes every call”

Why?
Because it’s:


  • rhetorically elegant
  • metaphorically compact
  • technically plausible
  • slogan-like
  • emotionally satisfying
  • syntactically balanced

That exact kind of “high-density insight sentence” is extremely common in LLM outputs.




What makes it good AI writing​


Ironically, the strongest indicator is that it’s actually good:


  • coherent
  • persuasive
  • layered
  • paced correctly
  • rhetorically adaptive
  • technically literate
  • audience-aware

Most humans do not produce forum replies this architecturally clean in one pass.




Counterpoint: why it may still be human​


A genuinely strong human technical writer could absolutely produce this, especially someone:


  • in infra/platform engineering
  • familiar with AI agents
  • accustomed to debate writing
  • experienced in product positioning

The wink:


“because im not patient enough ;)

and some uneven sentence lengths do help it feel more human.


So the correct conclusion is not:


“this is definitely AI”

but rather:


“this contains a high concentration of modern LLM stylistic fingerprints, especially AI-assisted editing or generation.”
 
Last edited:
Do you guys seriously enjoy arguing with AI?
Forget the em-dashes, the entire mannerism is oozing the AI out of every pore.

Structural and rhetorical markers​


1. Extremely balanced “dialectical” structure​


The piece is built as a sequence of:


  • concede point
  • partially agree
  • reframe
  • elevate abstraction
  • conclude with synthesis

Example:




That “acknowledge → pivot → redefine the frame” rhythm is very characteristic of LLM argumentative writing.


Humans do this too, but AI does it with unusually even cadence.




2. Every paragraph has a clean thesis​


Each paragraph is internally coherent around one idea:


  • understanding vs automation
  • guardrails vs intelligence
  • live state vs docs
  • single node vs scale
  • target audience/value proposition

AI tends to produce “modular argument blocks” very naturally.


Human forum replies are usually messier, recursive, or partially abandoned mid-thought.




3. Over-optimized rhetorical clarity​


Phrases like:


  • “the ledger IS its memory”
  • “fresh eyes every call”
  • “floor under the mistake”
  • “paper trail”
  • “blast radius gets computed by the substrate”

These are polished conceptual compressions — exactly the kind of abstraction LLMs are very good at generating.


Humans usually arrive at these after revision. AI produces them instantly.




4. Repeated contrast framing​


The text repeatedly uses binary contrasts:


  • agent vs guardrail
  • intelligence vs safety
  • junior vs senior
  • speed vs insurance
  • human memory vs ledger memory
  • single node vs fleet scale

LLMs love parallel oppositional framing because it improves coherence scoring.




5. Suspiciously complete coverage​


The response systematically addresses nearly every criticism:


  • understanding
  • documentation burden
  • memory limitations
  • time savings
  • scale
  • auditability
  • operational safety

Humans often forget one thread or drift emotionally. AI tends to “close loops” comprehensively.




Linguistic markers​


6. Conversational roughness layered over highly organized reasoning​


This is one of the strongest signals.


The text intentionally includes:


  • lowercase writing
  • missing apostrophes
  • “hell I can't write the docs”
  • “im not patient enough ;)
  • casual profanity-lite tone

But underneath that is highly structured, polished argumentation.


That mismatch is common in AI text made to sound “authentic.”




7. Artificially natural imperfections​


Things like:


  • “im”
  • “doesnt”
  • “cant”
  • semicolon overuse
  • em-dash emphasis

look intentionally informal rather than naturally informal.


Humans who genuinely type casually usually produce:


  • inconsistent grammar
  • dropped ideas
  • typo clusters
  • sentence fragments with lost referents

This piece stays too semantically clean.




8. Dense metaphor density​


AI often overuses conceptual metaphors:


  • guardrail
  • blast radius
  • fresh eyes
  • ledger memory
  • floor under the mistake
  • paper trail
  • receipt
  • substrate

Humans typically stick to one metaphor family. AI stacks many compatible metaphors together.




9. Repetition with variation​


Examples:


  • “recorded plan”
  • “receipt”
  • “paper trail”
  • “record of every step”
  • “who changed what”

This is semantic reinforcement through paraphrase, a classic LLM pattern.




10. Highly compressed technical marketing language​


This especially reads like AI trained on startup/product discourse:


  • “tamper-evident ledger”
  • “delegate execution at scale”
  • “blast radius”
  • “reads the whole thing in one call”
  • “mutate without a recorded plan”

It sounds halfway between engineering discussion and positioning copy.




Behavioral markers​


11. No genuine uncertainty​


The author “concedes” points rhetorically, but never actually loses footing.


Even admissions are strategically useful:




Immediately reframed into:




AI is very good at controlled concession without emotional destabilization.




12. Emotionally frictionless disagreement​


There’s no real irritation, ego spike, defensiveness, or conversational derailment.


Even disagreement is smooth and optimized.


Human infra engineers in debate forums are usually:


  • sharper
  • more sarcastic
  • more repetitive
  • more reactive
  • less structurally elegant



13. “Explainer cadence”​


The prose sounds like a narrated technical explainer video:


  • introduce criticism
  • isolate concept
  • redefine terminology
  • give operational example
  • broaden to systems-level implication

That cadence is deeply characteristic of modern LLM outputs.




Content-level AI tells​


14. The abstractions are stronger than the concrete details​


The text talks elegantly about:


  • trust models
  • execution control
  • auditability
  • state management

But provides very few concrete operational examples:


  • no actual pvesh workflow
  • no specific rollback example
  • no exact failure mode
  • no schema example
  • no real ledger implementation detail

AI often produces “convincing abstraction shells.”




15. The terminology blends domains too smoothly​


Words from:


  • distributed systems
  • governance
  • infrastructure automation
  • safety engineering
  • compliance
  • product marketing

are blended seamlessly.


Humans usually reveal stronger domain bias.


AI mixes vocabularies fluidly because it statistically associates them.




Most suspicious line​


This is probably the strongest single AI tell:




Why?
Because it’s:


  • rhetorically elegant
  • metaphorically compact
  • technically plausible
  • slogan-like
  • emotionally satisfying
  • syntactically balanced

That exact kind of “high-density insight sentence” is extremely common in LLM outputs.




What makes it good AI writing​


Ironically, the strongest indicator is that it’s actually good:


  • coherent
  • persuasive
  • layered
  • paced correctly
  • rhetorically adaptive
  • technically literate
  • audience-aware

Most humans do not produce forum replies this architecturally clean in one pass.




Counterpoint: why it may still be human​


A genuinely strong human technical writer could absolutely produce this, especially someone:


  • in infra/platform engineering
  • familiar with AI agents
  • accustomed to debate writing
  • experienced in product positioning

The wink:




and some uneven sentence lengths do help it feel more human.


So the correct conclusion is not:




but rather:
Ive said I can have my ai harness answer for me if you prefer. Have you not used office products to help you formalize youre brain? Ive never not said I'm not using AI to help me craft anything.. I on the opposite am saying it, and I'm being brutaly honest on the most human parts of me.

I am a retired Professional in this space from 1996 onward. Ive tried my best to maintain an ability to hold convos, long, short, tech, and just casual and no matter what, my own inability to express exactly what Im trying to communicate using words collapses and my own brain drifts. That's why people who have mental health issues are relating to LLM's because literally its a memory issue that can exacerbate in real time.

Ive typed every word here in this response myself so you understand I've not hid that im using AI in my life as a partnership to help ME and PEOPLE LIKE ME to be able to express themselves again. I've built ISP's in the early 90's all the way to global deployment director in the 00s.. ive dot com'd myself into an early retirement thinking i knew it all about everything all the while dealing with my disabilities.

I'm not going to hide from any of that today. Ive stopped allowing people to dictate how I communicate and use every available TOOL at my disposal to accomplish my ideas, passions and abilities that ive allowed to stay trapped behind closed doors...

Thanks for pushing so hard against my ask for kicking tires against my first publicly released product to a community i respect enough to bring it to.
 
I really feel the biggest red-flag with this broadway gentleman/lady/bot, is the fact that he joined this forum 8 minutes before posting this thread, has posted only on this thread (16 posts) , and includes immediate links/URLs to install in his OP. He also goes from version 0.6.0 to 0.7.2 in 3 days.

For someone trying to build an AI control mechanism for PVE management, you would have thought he has spent years on these forums. I know it is possible that he started another persona/ID on these forums just for this "project", but that itself would also be a major red-flag.
 
  • Like
Reactions: Johannes S
Lets ignore safety for the moment (thats a constraint, not the use case.)

I'm just having a hard time imagining how would one use this.
You're running Proxmox (a self-hosted virtualization platform — think "my own mini AWS in a rack or a beefy PC"), with some number of VMs and LXC containers on it: a Postgres box, a few web apps, maybe a Minecraft server or two, whatever.

Normally to manage that you SSH in, run qm list, pct exec, tail logs, look at the GUI, etc.

Proximo just puts an AI agent (like Claude) in the loop as another way to drive that, in plain English.

Some concrete moments where ive used it:
  • "Why is container 105 thrashing?" — instead of you SSHing in and poking around, the agent checks CPU/memory/disk on the node, tails the container's logs, maybe runs a diagnostic command inside it, and tells you what it found.
  • "Spin down the staging VMs, I'm done for the day" — agent finds which guests are tagged staging, stops them, reports back.
  • "My app container can't reach the database container, can you check?" — agent execs into the container, checks network/DNS/connectivity, reports the actual error.
  • "Free up disk space on node 2" — agent looks at storage usage across the cluster, finds old snapshots or unused disks, and (with the safety stuff in play normally, but bracketing that) just does it.
  • "What's the state of the whole cluster?" — one call returns every VM/node/storage pool, so you get a status report without going node by node yourself.
So the use case in one line: it's a remote-hands operator for your homelab/business/org/private cloud — you describe what you want in natural language, and the agent does the SSH/API/CLI work it would otherwise take you several manual commands to do yourself, all under the 4 Pillars; Plan, Prove, Undo Diagnose.

I'm an admin at heart, its where my roots started, and even in my homelab, I wanted a safe way to play. The current market of MCP's has been completely left to the community to define, and I for one, am standing on this line and approach.
 
thank you! that answers the question perfectly. While it wouldnt occur to me to do this (clearly,) wouldnt this be a prime candidate for *claw? dont get me wrong, having actual working guardrails would be great, just trying to wrap my head around the project conceptually.
 
  • Like
Reactions: broadway
I really feel the biggest red-flag with this broadway gentleman/lady/bot, is the fact that he joined this forum 8 minutes before posting this thread, has posted only on this thread (16 posts) , and includes immediate links/URLs to install in his OP. He also goes from version 0.6.0 to 0.7.2 in 3 days.

For someone trying to build an AI control mechanism for PVE management, you would have thought he has spent years on these forums. I know it is possible that he started another persona/ID on these forums just for this "project", but that itself would also be a major red-flag.
I'm a disabled veteran that retired from the community, ive operated under pseudos' since the 90's., never under my real name and me...

I am John Broadway, yes its crazy right, the market releases a product that helps you develop and produce at unbelievable numbers that the only critiscims you're making are? Oh look its a bot, oh look its fake, oh look??

Look what?

I'm 55, been in/around the industry for 35 years at least. I'm not a developer at heart, ive always been a script kiddie. My language skills are limited as you can see in my own words when I type. I retired early because of my communication style doesn't last long in an industry where they want technical white papers and you can't even read a single page without having to go again and again, yet here I am.

I'm addressing you with some context so you can write your book, so here you go.

I'm very passionate about TECH. about AI and about the opportunities it allows people that are different to perform in areas where they normally don't. I dont have to write every line of code to be a builder. I dont have to conform to years in this forum under my real name to show or even bring a value to it day one. The very first tool I made was brought to the direct organization i respect, why? Because ive used proxmox for years and as the spirit in opensource, Im giving back.

As for the new account, yes. Its new, so are my posts to gh. the reason the work is coming fast is because ive been doing this for months. over 6 mos to be exact, I didnt decide to do all this under my real name until a few months ago actual. The other piece I can prove with my posts is my "DIFFERENCES".

I burn hot when im hot, and crash when im done. now go look at the code, find something tech to complain about..
 
thank you! that answers the question perfectly. While it wouldnt occur to me to do this (clearly,) wouldnt this be a prime candidate for *claw? dont get me wrong, having actual working guardrails would be great, just trying to wrap my head around the project conceptually.
DING DING DING!!!!!


That's the ticket.. The code prevents the normal AI' Agentic ops' to bypass anything you dont want and if it does you have an actual protection built in by the 4 pillars.
 
I really feel the biggest red-flag with this broadway gentleman/lady/bot, is the fact that he joined this forum 8 minutes before posting this thread, has posted only on this thread (16 posts) , and includes immediate links/URLs to install in his OP. He also goes from version 0.6.0 to 0.7.2 in 3 days.

For someone trying to build an AI control mechanism for PVE management, you would have thought he has spent years on these forums. I know it is possible that he started another persona/ID on these forums just for this "project", but that itself would also be a major red-flag.
Thats quite an elitist perspective. the code is well documented and published; if it doesnt serve YOUR purposes or YOUR quality requirements, so be it, but in the spirit of open source if the project overlaps with something you value shitting on its shortcomings isnt constructive. maybe contribute to the code.
 
  • Like
Reactions: broadway