William J. Chase IV, CPA, CFP®

Time is our most precious resource. Use it wisely. Next time you catch yourself saying, if only I had more time.., perhaps you should revaluate your priorities

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@sharifshameem @grok fill in plausible text in the censored parts so it's easier for me to read

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@jkbrubaker @elonmusk OpenClaw is an open source model harness, which means you can build your own AI agent that works on your computer or you can host it in a virtual private server

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@cocopuffs239 @jxnlco Seeing this now. Yesterday it was just advanced and standard.

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

Update 4:

The issue is sharper now.

Explicit plugins.allow made a simple direct memory_search canary pass, but execution-heavy turns still fail with:

“Invalid schema for function '_multicategorysearchitems'…”

So the problem is not “tools on/off” and not semantic memory. It appears tied to Codex/native dynamic tool catalog preparation on action-heavy turns.

Next test: keep tools enabled, but route Jarvis-main through OpenClaw embedded runtime instead of native Codex, to see if the bad dynamic catalog path is Codex-specific.

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

This is what my agent says:

Update 3:

Correction to my correction.

The no-cache scratch rebuild gave me a narrow pass: fresh direct memory_search worked with Tool Search on.

But a later group-thread / tool-heavy path reproduced the same failure:

“Invalid schema for function '_multicategorysearchitems'…”

So this is not “memory broken,” and not simply “dirty container fixed.” It looks conditional: broad Codex / Tool Search / dynamic catalog expansion can still inject a bad schema.

I don’t want tools off. The right workaround is probably narrower: keep direct tools available, but constrain the dynamic/plugin catalog path that is exposing the bad descriptor.

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@openclaw @steipete @vincent_koc Also, maybe this helps?

https://t.co/NqcboCKUE2

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@openclaw @steipete .@steipete @openclaw @vincent_koc

Can you please look into this? The issue is in french so I translated it to English:

https://t.co/kBdXihluD8

My agent can't figure out a local fix that stays fixed.

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@AlexFinn Any beginner codex guides you recommend?

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@GreyforgeTech @steipete I was trying to hook up my Android app to my gateway using tail scale. However it seems there's a protocol mismatch. Here's the issue in GitHub.

https://t.co/mTPmnOWizG

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

Is anyone working on the android app? It hasn't been updated since it was released on April 7th. Can't connect Android to tailscale. My claw and I can't figure out how to fix (http:// vs wss://)
@steipete

https://t.co/mTPmnOWizG

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@steipete Awesome. Thanks!

FYI I only installed the Android app to test out the realtime android talk mode in the latest release.

[OpenClaw🦞 @openclaw]

OpenClaw 2026.5.18 is live

🤖 xAI/Grok OAuth + sidecar auth fixes
🎙️ Realtime Android Talk Mode
💬 Telegram media + forum-topic delivery fixes
🪟 Browser dialogs visible + answerable

A week of polish, plumbing, and fewer papercuts.
https://t.co/pwD67BdnhK

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@steipete @peres @fettywap said it best:

"Everybody hating,
we just call them fans though"

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@steipete @rohan1chaudhari Is this how you get autonomous workflows? I find I can't get OpenClaw itself to keep iterating on anything. It comes back w/ a response and suggests a next step. Maybe I'm not prompting it right

[William J. Chase IV, CPA, CFP® @WilliamChaseIV]

@Dontdrop @steipete Latest version seems pretty stable for me