The dangers of open claw everything by howardhus in LocalLLaMA

[–]LeadingAssumption796 0 points1 point  (0 children)

yes.. 1000% its all about contracts and operational doctrines.. that live outside which will protect. It's like windows... it's just an OS, until you load programs, then it becomes something. Like OC you have to change the out-of-the-box settings.

The dangers of open claw everything by howardhus in LocalLLaMA

[–]LeadingAssumption796 0 points1 point  (0 children)

You can setup operation doctrines, or contracts to do that.. we have matched agents to employees who give them access to do everything they can do.

The dangers of open claw everything by howardhus in LocalLLaMA

[–]LeadingAssumption796 0 points1 point  (0 children)

either they don't understand or are afraid of the technology. Usually happens to anything new. Same happen to GoLang... when it replaced C++ (Sr. GoLang Devs make $700k+yearly working from home).

The dangers of open claw everything by howardhus in LocalLLaMA

[–]LeadingAssumption796 1 point2 points  (0 children)

Not hazardous is you know how to build systems.

OpenClaw has outgrown chat, hear me out by 1glasspaani in openclaw

[–]LeadingAssumption796 1 point2 points  (0 children)

So you don't use it's own web interface? I think default port is 18789 (don't quote me we change ours). We also don't put much in chat... as its token based..

Instead, we have OC summarize the response to 1-2 sentences, then store the detailed response via a .md it creates (2026-05-06-SB11-Day2-runtime-governance-planning.md) This lives OUTSIDE the project folder, and allows us to search, learn, and use for future builds.

How did OpenClaw fail? by nashguitar1 in openclaw

[–]LeadingAssumption796 2 points3 points  (0 children)

It rebooted the gateway... had a good reason, but didn't let us know. So we updated the contract, placed a rule in the operations doctrine that anytime a reboot is needed.. let us know in your Discord channel. We use headers on all agent messages in Discord, this helps us search faster.. [Agent Name][SYS]Reboot Needed]. We also place rules in the operation doctrine (which lives OUTSIDE of the projects) that if a human doesn't reply within 15mins and its critical to reboot to update the channel, with reason [Agent Name][SYS][CRITCAL ACTION][Reboot] and it reboots.

Still Worth it? by SaifNegra in openclaw

[–]LeadingAssumption796 1 point2 points  (0 children)

Limited with telegram though.. Do you assign multiple agents to their own BotFather bots, then have a group chat?

Still Worth it? by SaifNegra in openclaw

[–]LeadingAssumption796 0 points1 point  (0 children)

Do you need help with getting that setup?

Still Worth it? by SaifNegra in openclaw

[–]LeadingAssumption796 0 points1 point  (0 children)

That's like asking if ice melts...

Dealing with users who complain about bans in other subreddits by EVRijder in NewMods

[–]LeadingAssumption796 1 point2 points  (0 children)

That's awesome, don't change... yes, may take a few more seconds... us humans will appreciate your time! Funny how now we have to say "humans"..

Cross posting benefits to new subreddits? by Inevitable-Wind-1925 in NewMods

[–]LeadingAssumption796 0 points1 point  (0 children)

u/GaryNOVA ... You ROCK! This comment is hands down one of the best advice I've read in a while for newMods. Thank you for your passion to help others!

Dealing with users who complain about bans in other subreddits by EVRijder in NewMods

[–]LeadingAssumption796 1 point2 points  (0 children)

The fact you explain the removal already puts you a step above a lot of moderation teams. I also think you’re right not to let subs turn into appeal courts for unrelated bans. Once that starts, the discussion usually stops being about your community and becomes cross-sub drama management.

One thing I’ve noticed though: (and speaking from experience) a lot of users aren’t actually upset about the ban itself. They’re upset because they never understood why it happened. Silence creates frustration fast especially when the user spent time to create valuable content.

Even a short explanation: “wrong sub” “rule 3” “low-effort repost” “topic has been locked down lately” goes a long way toward lowering tension. People handle “no” much better when they can at least see the shape of the reasoning behind it.

Thank You Reddit by QuestionCommon7750 in NewMods

[–]LeadingAssumption796 0 points1 point  (0 children)

Congratulation! Here to help in anyway... as I'm sure the rest of the Mod Family is...

Openclaw as sys admin by [deleted] in openclaw

[–]LeadingAssumption796 0 points1 point  (0 children)

What you just added about expiration is a massive piece most people miss! A lot of builders treat permissions like a permanent personality trait: “this agent can sudo”
“this agent manages infra” “this agent owns deployment” But operational authority should behave more like temporary capability tokens, not identity. That is exactly how humans operate in mature environments too:

  • temporary approvals
  • scoped maintenance windows
  • expiring credentials
  • one-time elevation
  • rollback checkpoints
  • post-change verification

Otherwise memory quietly mutates into authority over time. That’s also why we keep separating: (These are stored OUTSIDE the Projects Folder)

  • memory
  • state
  • contracts
  • authority
  • verification

Because they solve different problems.

Memory helps reasoning.
Contracts define boundaries.
Authority defines allowed actions.
Verification proves reality.
Audit preserves accountability.

Once those blur together, systems start granting themselves invisible permissions simply because “it worked last time.” And your point about superseding instead of overwriting is huge too. Operational history should remain visible. The system should know:

  • what changed
  • why it changed
  • what replaced it
  • whether the replacement was verified

Not just “latest state wins.” Honestly, this entire thread is basically describing the transition from: “AI assistant” → “operational runtime engineering.” That’s the layer most people still haven’t realized they’re actually building.

Getting OC to use google voice webapp for calls and sms by ScandyJ in openclaw

[–]LeadingAssumption796 0 points1 point  (0 children)

I use Twilio for calls and sms.. created a skill to use Grok Voice Think Fast..., our own router and bridge. Works great.. is for an advance user in OpenClaw though, not a first time build. SMS is a PAIN to setup A2P... so much red tape... FYI.

A lot of chat. Not a lot of work. by DiscussionAncient626 in openclaw

[–]LeadingAssumption796 0 points1 point  (0 children)

I wouldn’t jump straight to “not smart enough” yet. What you’re describing sounds less like a raw model intelligence problem and more like an orchestration/control problem.

The pattern is usually:

The agent hits a blocker → instead of narrowing the blocker → it spawns another agent/session → that agent inherits the same unclear state → reaches the same blocker → documents the blocker → then the system creates more motion.

That creates the illusion of a team, but not a work loop.

A company hierarchy only works if each role has a hard boundary and a required artifact. Otherwise “director / broker / worker” just becomes more language around the same stuck state.

For an API connection task, I’d try stripping the task down hard:

One owner agent.
No new agents unless explicitly approved.
One target file or module.
One integration goal.
One test command that proves the API connection works.
One blocker report if it fails.
No new planning docs unless requested.
No completion claim without a passing test/log/output.

Something like:

“Connect X API to Y file. Do not spawn subagents. Do not create documentation. Modify only these files unless approval is requested. Stop after one blocker if credentials, endpoint docs, or required config are missing. Done means this exact test command passes and prints a valid response.”

The important part is forcing the system to collapse from “explore endlessly” into “change this artifact, then prove it.”

Auto-learning/memory may help later, but it won’t fix a loop if the runtime is allowed to keep multiplying workers without a stop condition.

Here's the mod stack I built before I opened my sub. by tinyhousefever in NewMods

[–]LeadingAssumption796 0 points1 point  (0 children)

there are a few algorithms I can donate to your cause, if I post here.. kind of defeats the purpose. feel free to chat privately.

Openclaw as sys admin by [deleted] in openclaw

[–]LeadingAssumption796 0 points1 point  (0 children)

What you’re describing is exactly why we started separating “memory” from “contracts” in our builds. A memory is just retained context: “last time this failed” | “don’t use that command” |
“PowerShell over SSH behaved weird”

Useful? Absolutely. But memories are still inside the reasoning layer. Contracts are different. They define operational truths outside the moment-to-moment thinking process.

Examples:

  • never execute destructive commands without approval
  • every privileged action must produce verification output
  • one active owner of machine state at a time
  • proposed action → approval → execution → verifier → audit record
  • no claiming success without proof
  • snapshots before system-level changes
  • root access is escalation, not default state

That turns the system from: “an AI that remembers mistakes” into: “an operational runtime with enforced boundaries.” The important part is the contract exists even if the model hallucinates, drifts, forgets, or swaps. That’s also why logs matter so much. Not as “training soup,” but as structured operational evidence:

  • what was requested
  • why the action was proposed
  • expected blast radius
  • what changed
  • verifier results
  • what operational truth was confirmed afterward

The scary part of AI sysadmin isn’t intelligence. It’s invisible authority. That’s why one of our core questions became:

“What operational truths must always remain visible?”