Every week the OpenClaw community surfaces something that changes how you think about running agents. This week: a security scan that should make every VPS owner nervous, two underrated skills that might be the most useful things in your setup right now, and the one config line that turns GPT-5.5 from a speechmaker into a doer.
1. Your API Keys Are Living in Your Logs — @balakhonoff's Wake-Up Call
Kirill Balakhonov (@balakhonoff) posted a sobering two-part thread on June 7–8 after running a routine ripgrep scan on his VPS and finding his own OpenRouter API key scattered across 17 different log files — not just in OpenClaw, but also in Codex and Claude Code logs sitting on the same server. He shared a ready-to-run shell snippet that anyone can drop into their terminal: install ripgrep, set a partial key as a variable, and scan your home directory for exact string matches. It takes about 30 seconds and the results can be alarming. Snyk research published around the same time found that roughly 7% of ClawHub skills — more than 283 packages — pass API keys directly through the LLM context window or dump them into output files. Kirill's own response was to start prototyping a proxy-based setup so agents never touch raw keys directly. This is the kind of thing most people only discover after something goes wrong — better to run the scan now.
https://x.com/balakhonoff/status/2064093713542918446
2. The Two Skills You're Sleeping On: /autoreview and /handoff — @Shimayus
Shimayus, a Tokyo-based AI agent specialist and Quai CEO with over 10K followers, used his June 9 post to give a quiet shoutout to two community skills that are dramatically underrated relative to their star counts: /autoreview and /handoff. The /autoreview skill slots in before a commit or deploy, running a structured review pass — bug detection, isolated verification, fix candidate generation — without requiring a human in the loop. The /handoff skill compresses an entire session into portable Markdown so a second agent, or a completely different model, can pick up exactly where the first one left off. Shimayus's framing is the real insight: he argues the quality ceiling for agentic work is no longer raw model intelligence, it's workflow design. "Effective AI agent operations depend less on raw model power and more on designs that reliably pass failures or context to the next step or agent." If you're running Codex or multi-model pipelines and haven't installed these two, this thread is the nudge you needed.
https://x.com/Shimayus/status/2064135985685029302
3. GPT-5.5 Gives Great Speeches — Here's How to Make It Actually Work
When OpenClaw v2026.6.1 shipped with GPT-5.5 as a supported model in early June, the initial reaction was enthusiastic — until people started running actual agentic workflows and noticed the model wouldn't stop talking. A r/openclaw thread titled "OpenClaw 2026.6.1 + gpt-5.5 — Big talk, little action" quickly accumulated comments from users watching their agents produce long, eloquent explanations of steps they hadn't taken yet. One commenter put it plainly: "Anyone has an idea to make gpt-5.5 less verbose?" The fix, surfaced quickly by the community, is a single config change: set verbosity=low in your openclaw config for GPT-5.5, similar to the existing thinking-level control. It works, and it transforms GPT-5.5 from a speech-giver into an executor. The thread is a useful reminder that every new model that drops into OpenClaw needs its own tuning pass — and that the community almost always finds the knobs before the docs do.
https://www.reddit.com/r/openclaw/comments/1tzei26/openclaw_202661_gpt55_big_talk_little_action/
Spotted something great on X about OpenClaw? Share it — the community is the best part.