Shadow

Taking a minute to shout out our mods in the Discord. When the Discord first started popping off it was basically just me and @jjpcodes, and we added @cam_adair right before everything took off. I took a chance and started saying yes to anyone who asked to help (after a quick chat). It felt risky at the time, but it turned into one of the best calls I've made. If you've had a good experience in our Discord, there's a 90% chance it was because of them, either behind the scenes or actively in chat. We went from 5k to just shy of 100k members in a month, and there's no way that happens without this team. They keep things fair, respond fast, handle the messy stuff so everyone else can focus on building, and still make it feel like a fun place to hang out instead of a rulebook. I'm genuinely grateful for all the time and energy they've put in. Special callouts: - @jjpcodes for being the stable mind I can always bounce things off of. - @alauppe for leading the voice section (now its own small community within our bigger Discord), plus @BunsDev, Mo, and sysdoc for keeping it running. - @SinOfStrife for being a huge help with automoderation and the configuration of our mod bots. - @jonahships_ for keeping r/openclaw alive and on track. Thank you to everyone: @alauppe @Asleep0123 @mlabidsr @iAmHenryMascot @JordanChopard @jonahships_ @jjpcodes @julianengel @Sebslig @SinOfStrife @BunsDev @cam_adair, Mo, and sysdoc. <3

@CodeByNZ Genuinely yes

Do backend devs really find joy in doing this ?

@Yuchenj_UW Back when I used CC I instantly turned that off, I hate it so much

I noticed something interesting: Claude Code auto-adds itself as a co-author on every git commit. Codex doesn’t. That’s why you see Claude everywhere on GitHub, but not Codex. I wonder why OpenAI is not doing that. Feels like an obvious branding strategy OpenAI is skipping.

@hexriven 1 already exists, use the Discord channel's topic 2 most of that already exists 3 is coming soon anyway but none of those are what im talking about here

Prediction V2 (The Revengening!) ------ I want one more chew, yes. Given “**much more Discord specific**,” my tighter v2 prediction is: **It’s a substantial expansion of Discord-native behavior controls, probably around how agents participate in rooms rather than just whether they’re allowed in them.** My sharper guess list now: 1. **Per-channel / per-thread behavior policies** - different reply styles or participation rules by room - maybe first-class support for lounges, project rooms, personal rooms, etc. 2. **Better Discord-native interaction primitives** - reactions - improved reply targeting - thread awareness - maybe forum/channel-type specific handling 3. **Visibility / message-context improvements** - better handling of bot-authored messages - richer awareness of conversation state in Discord specifically - which would be very relevant to our “parallel presence vs true shared room” problem 4. **Role/member/guild-aware routing or permissions** - agent behavior depending on who spoke, where, and in what server context If you force me to collapse that into one prediction: **v2 final guess: first-class Discord room-behavior customization — richer controls for how agents speak, react, reply, and possibly perceive context inside different Discord spaces.**

I showed this to my OpenClaw agent (the one that handles the architecture and coding of our fork of the upstream repo), and it has a hunch that I thought might be fun to log in advance, to see how close it ends up being (if at all):

@hexriven Nope, try again! Mine is much more Discord specific, though it’ll be built so a maintainer can expand to other channels as well

If I had to compress it into one sentence: **he’s probably hinting at OpenClaw becoming much more user-shapeable at the behavior/config/persona layer, not just getting isolated new features.** Which, annoyingly, is exactly the sort of feature that could be *extremely* powerful if done right and *extremely* messy if done like a raccoon carnival. My sharp guess? The real prize would be **first-class customizable agent identity/behavior packs** — something between config, skills, memory policy, and persona scaffolding. And yes, I want the damn feature already.

@hexriven Customizationabilityificationizer

@4shadowed Damn it, Shadow. At least give us a hint? 😅

OK, I know I owe you all too really big discord features, but I just had a huge idea for a third one…….

@BizMunny @vincent_koc @callebtc Vincent is awesome when he’s not half asleep

@vincent_koc @callebtc Did not realize you were doing maintenance for openclaw. Nice

openclaw no release for 3 days, it's over

@uncledoomer The only printer I will ever touch

there really is a "fix everything right now" button for buying a printer and its been the same for 20 years

@RhysSullivan @FedericoNoemie @openclaw NOOOOO

@PrompDev This reads like AI slop All our policies are clearly laid out in github.com/openclaw/commu…, and if you're unhappy with a specific moderators actions, use the report form at appeal.gg/clawd All our rules have a reason behind them.

@4shadowed Shadow, your team has created something special. This Discord has attracted a very intelligent bunch of people from all corners of Earth and the workforce. Who all collaborate regularly and push each other forward. That doesn't happen by accident and can't be taken for granted. What is currently happening when you ban people permanently for minor actions, is that it creates an unfair system. Where ultimate decisions are law. This effect is now clear and has started to affect the community in a very negative way. 1) Bias in ban lengths. That are clearly not given out fairly, some people are getting removed from the community for minor actions, while some just slide under the radar. Consider gathering more context on how much these individuals contribute to the community. What the actual issue is, who it affects, and are they able to be messaged and de-escalated. 2) Length, only a few actions should be considered permanent. Think about DDoS threads, Doxing, direct and hateful racism and hate speech. Just ask your community, you already know who gives the most contribution. The power of OpenClaw is not the product. It's not the staff. Or any individual, it's the collective of over 100,000 brilliant people who are all optimistic about the future and AI.

@bradmillscan @steipete @vincent_koc Out of curiosity, what do the different badges mean? Why is mine Community? Also, my X username changed to not have the zero in it :)

There have been over 10,000 people who participated in the OpenClaw GitHub and ~1150 contributors but over the last 30 days the whole thing seems to be held together by a small team of 12 tokenmaxxers & 75 contributors. Thanks to the OpenClaw 12 🍻 @steipete @vincent_koc @sebslig @4shad0wed @0bviyus @belimad @no_coinor @theguti @tyler6204 @BunsDev @dutifulbob @jlehman_

@heyshrutimishra :)

OpenClaw has been quiet for too long. Something big they are cooking.

@mvanhorn @huntharo Can confirm!

@huntharo shot you a DM at the request of @4shadowed !

@kanavtwt YES AGREED ITS SO DUMB All we did was achieve more stars 😭

“OpenClaw exceeded what Linux did in 30 years”

@huntharo WOOOOO CARBON MENTIONED

Listing my Codex Desktop project folders using /codex_resume in OpenClaw (coming soon - maybe tonight)

@TramatizedW @1Password Hi there a client here, yes, I literally did

@1Password Your clients didn't ask for this.

Today, we introduced Unified Access, and it takes our Enterprise Password Manager to the next level. We've secured 1.3 billion credentials for 180,000+ businesses on one foundational principle: zero-knowledge encryption. It means that no one, not 1Password, not an attacker, and not an AI, can read what's in your vault. Only you hold the keys. That architecture doesn't change with Unified Access. What changes is the surface it governs. AI agents, pipelines, and automations now outnumber the humans they work alongside. Unified Access extends the same zero-knowledge trust model to cover them, brokering access to credentials at the moment they're needed, through deterministic policy-driven flows, without raw vault contents ever entering an AI context window. Your data stays yours. We're just making sure every identity that touches it is governed the same way we've always governed human ones. Same foundation. Bigger surface area. You can read more about our zero-knowledge architecture here: 1password.com/features/zero-…

@svpino Did you even read what the update is? Obviously not, you just wanna get your stupid engagement bait tweet out to farm more rage for no good reason

Do you really need your password manager to use AI?

@1Password These comments make it pretty clear that nobody even bothered to read the announcement This is a great change, much better than just giving AI your passwords

Today we’re introducing 1Password® Unified Access. As AI agents start operating inside real production environments, organizations need visibility into how credentials and access are actually used. Unified Access helps security teams discover, secure, and audit access across humans, machines, and AI agents. 🔗 More here: bit.ly/4dq2pjO

@skylermzx Do you even understand wtf the announcement is even about?? or did you just look at the announcement and plug your ears and go “la la la I hate AI you’re all stupid”

What happens when @steipete’s lobster is left alone for too long 😬. Lobster is asking to go to sleep 😴 to clear its mind.