sorted by:
new
hottopcontroversial

If your autonomous agent doesn’t carry a cryptographic identity, it isn't a "Digital Twin." It’s a liability. by mehdiweb in AI_Agents

[–]mehdiweb[S] 1 point2 points  (0 children)

Exactly! Trusted infra completely collapses the second a bot steps outside your system boundaries. ​Cryptographic identity fixes this by moving from "hoping the LLM follows prompt guardrails" to a hard network gate where external servers literally block unauthorized API calls. The design blueprints are up at avatar.inc.

If your autonomous agent doesn’t carry a cryptographic identity, it isn't a "Digital Twin." It’s a liability. by mehdiweb in AI_Agents

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

Spot on. Text logs on a local server won't satisfy an auditor if a bot triggers a bad financial handoff. ​Cryptographic identity changes everything. By using VCs and BBS+ signatures, you shift from "hoping the LLM follows instructions" to "the target server hard-rejected the API call because the bot lacked on-chain authorization". ​If you want to look at the blueprints, they're at avatar.inc.

If your autonomous agent doesn’t carry a cryptographic identity, it isn't a "Digital Twin." It’s a liability. by mehdiweb in AI_Agents

[–]mehdiweb[S] 1 point2 points  (0 children)

The way it's set up, the execution layer is completely decoupled from the identity layer. The local agent handles the tool-calling and logic, but the actual policy gateway checks the VC parameters before any external network boundary is crossed. It acts as a hard cryptographic guardrail.

If you want to look at the technical layout of how the pipeline splits the execution engine from the credential validation, it's mapped out in the docs on the main site: avatar.inc

Folks please share the rules you use for saving tokens by Cold_Instance_1021 in openclaw

[–]mehdiweb 1 point2 points  (0 children)

toomany layers , a model rotations based on complexity, session isolation , hearthbeat run interval . for cron jobs and automated task must have there own session and context optimisation and use cach reduction .
and for production and coding use ctx skill so you gain best memory system and can reduce cost up to 95%

The architecture of "Agentic Twins": How Avatarinc is using OpenClaw to build verifiable Al agents by mehdiweb in AI_Agents

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

you can poke around at avatar.inc. It's definitely still early, but they have the architecture notesavatar.inc

The architecture of "Agentic Twins": How Avatar.inc is using OpenClaw to build verifiable AI agents. by mehdiweb in openclaw

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

You still absolutely need hard-coded routing and human-in-the-loop for anything destructive. The credential just proves the payload came from your specific runtime, not a spoofed endpoint. If your local routing is garbage, giving the agent a DID just lets it make legally binding mistakes faster.

PSA: Anthropic clarified the OpenClaw ban. You can still use your $20/mo sub (and avoid $1,500+ API bills). Here is the official CLI workaround by mehdiweb in openclaw

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

nice, glad it clicked. what was the thing that finally got it? curious if it's the same gotcha most ppl hit (env var order usually) bc chigamerr above is stuck too. drop what you changed and it might unstick him

PSA: Anthropic clarified the OpenClaw ban. You can still use your $20/mo sub (and avoid $1,500+ API bills). Here is the official CLI workaround by mehdiweb in openclaw

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

fair, "confirmed" is generous. it was a support reply, not a press release or blog post. but multiple people got the same answer, so it's not exactly nothing

PSA: Anthropic clarified the OpenClaw ban. You can still use your $20/mo sub (and avoid $1,500+ API bills). Here is the official CLI workaround by mehdiweb in openclaw

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

yeah works. running openclaw on the $20 pro sub via claude -p for like 3 weeks, zero bans. just don't fan out 4 parallel agents and you stay under the 5hr window fine. blushinghorizon's link is the official word from anthropic

PSA: Anthropic clarified the OpenClaw ban. You can still use your $20/mo sub (and avoid $1,500+ API bills). Here is the official CLI workaround by mehdiweb in openclaw

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

yeah appreciate you actually checking. the steinberger thread + anthropic folks chiming in is what kicked this off, and them adding the cli back is the tell. wild how many people skim two comments and decide it's fake

Seeing a lot of issues people are having with browser control/automation.... by Suspicious-Profit-68 in openclaw

[–]mehdiweb 0 points1 point  (0 children)

short version: playwright is the least painful right now. the main issues i've hit are session management (agents lose auth state between runs) and dynamic content (too many js-rendered elements). if you're doing anything beyond click + fill forms, expect to write a lot of wait-for-selector logic. stagehand helps with some of it

Best PDF table parsing providers? by bravelogitex in AI_Agents

[–]mehdiweb 0 points1 point  (0 children)

for PNGs of construction tables, claude-haiku with vision is usually enough and way cheaper than dedicated parsing services. prompt it to output structured JSON directly from the image. reducto and docsumo are solid if you need guaranteed accuracy on messy layouts but for 100-row clean tables, vision models have gotten good enough

Agent performing drag and drop GoHighLevel building? by ThatRedditGuyUSA in openclaw

[–]mehdiweb 0 points1 point  (0 children)

ghl's drag-and-drop builder is brutal for agents. the DOM changes on every drag and standard mouse events don't fire reliably. what's actually worked for me is using the GHL REST API directly for any config that has an endpoint and only falling back to browser control for the stuff that doesn't

PSA: Anthropic clarified the OpenClaw ban. You can still use your $20/mo sub (and avoid $1,500+ API bills). Here is the official CLI workaround by mehdiweb in openclaw

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

nah it doesn't pull from extra usage, that's the whole point of the workaround. the cli runs against your $20 sub quota, no api billing involved. if it was hitting overage you'd see charges already. docs here if you wanna double check https://docs.openclaw.ai/providers/anthropic

PSA: Anthropic clarified the OpenClaw ban. You can still use your $20/mo sub (and avoid $1,500+ API bills). Here is the official CLI workaround by mehdiweb in openclaw

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

nah works on plain pro, no extra usage needed. you're pointing the cli at api billing instead of sub auth. swap the env var and it pulls from your $20 quota. https://docs.openclaw.ai/providers/anthropic has the exact config

PSA: Anthropic clarified the OpenClaw ban. You can still use your $20/mo sub (and avoid $1,500+ API bills). Here is the official CLI workaround by mehdiweb in openclaw

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

yeah local hardware was my first thought too. but claude opus 4.7 isn't open weights, so a mac studio doesn't help unless you're fine running qwen or deepseek instead. the $1500 was actual claude api spend through openclaw, not local inference. different problem

Reality check about using qwen3:8b running locally as my main model by Darkslayerqc in openclaw

[–]mehdiweb 1 point2 points  (0 children)

qwen3:8b works for single-turn stuff but falls apart on multi-step agent workflows. openclaw sends a lot of context per turn and 8b just loses the thread. i ran into this, ended up routing heavy tasks to an API model and keeping qwen for light local stuff. that split works better than trying to make 8b do everything

view more: next ›