#clawtributors

1 messages · Page 2 of 1

fierce harness
shadow jackal
warm crater
valid pumice
#

i would like to help

tropic otter
#

hey hey, just made a very tiny PR to add support for specifying target agentId in the /hooks/agent webhook, so you can now specify both sessionKey and agentId when triggering an isolated agent turn!
https://github.com/openclaw/openclaw/pull/5716

cold cobalt
#

updated mine again with some new changes from main that had a conflict and it's passing again.

It's pretty small and just allowing for changes that Pete made to actually get picked up without failing validation. Also allows for the tools for subagents to set a model override as well. (both wouldn't pass config validation for the gateway) https://github.com/openclaw/openclaw/pull/3768

topaz coral
cosmic moth
zealous palm
golden marsh
#

https://github.com/arosstale/openclaw-memory-template share how im using openclaw memory

basically a starter kit so you don't have to build the whole memory architecture from scratch. Good stuff for anyone who wants a more organized workspace than just winging it with blank MD files.

quiet plover
deep cargo
#

Im objecting to this pr

#

No need to do cap to tls 1.2

fast sundial
#

Is anyone building apps with X-Moltbook-Identity?

stark kernel
#

I'm looking to help out with some development. Right now I'm working on some integration with 1Password for storage of API keys/Passwords

untold pollen
tall prairie
#

We’re looking for more chat app integrations. If you feel your favorite chat app is missing, please submit a pr integrating it as a plugin! This is a great way to get your PR looked at.

wide stirrup
#

The last 2 times i've tried pushing up, I get a ⁨403⁩... 👀 is there an approval process prior to pushing up?

jolly wolf
#

you have to fork and pr

sacred socket
hasty fiber
hasty fiber
#

also ty whoever added the role^ 🙏

dull slate
#

Having these sections in my control ui to view/edit really helps when managing agents not running on my machine; anyone else find this useful? Sure i can prompt the bot to edit them but then i still want to see what it actually did in a pinch 😛 (no im not ssh'ing in every time or burning tokens to ask)

2026-02-01_18.47.48.gif
jaunty elk
#

yikes. looks like out of the 12 hooks documented, only 8 of them are actually wired up. this cripples the "press yubikey to prove you're you before i run that dangerous command" plugin i'm working on . filing an issue now

surreal bear
#

Hello was going to look at this bug but looks like someone already did a PR. My approach was going to be a bit different than explcitly checking if channel is signal. Not shitting on anyone's PR because it stil does what it needs to and likely a few years ago I would have doen thes same. I am messaging more so to see what is the recommended way to appoach when a pr exists and has not been reviewed yet. Also wondering if should still take a crack at it ? And if adding an optional attribute on channel layer that decides weather or not it should be lowercase or not is a worthy approach. Also open to other options

jaunty elk
#

yikes. looks like out of the 12 hooks

ivory delta
cedar bramble
#

Build an OpenClaw Bot = Clawdad

proud bay
lone mauve
fair cedar
#

I know we have pairing support for multiple channels. But is there progress being made for multi user support? (Because I’d love to contribute to this)

Rather than having my friends and family figure out how to run their own instances, I would like to just host it for them and let them have their own profiles.

white vault
#

I know there's a lot of PRs going on right now, but I was wondering what the typical process is. I created this PR with very small changes for the mobile UI layout. Planning to contribute more often which is why I asked 🙂

arctic wadi
sonic hinge
#

hey guys, i am working on a light wieght version of OpenClaw... Looking for contributors...

https://github.com/Pr0fe5s0r/LiteClaw

Anyone instrested Do contribute... Starting from scratch

hexed valve
#

Surely we build a moltgames. Arena for them to vs eachother in games

glossy yewBOT
#

@rastacowboy2021 via Twitter

Rasta (@rastacowboy2021)

Another 10K to $OPENCLAW Clawtributors @shakker
︀︀
︀︀Next donation will be made in 2 days to space out the txns and give us a constantly, timely schedule for them to receive the fees and most importantly avoid being banned.
︀︀
︀︀$2500
︀︀$12000
︀︀$5000
︀︀$10000
︀︀
︀︀we are now at $29,500 in donations to the OPENCLAW team

**💬 5 🔁 9 ❤️ 38 👁️ 455 **

FxTwitter ·
lime grove
#

no issues with it so far, I use the hooks in a skill and have been monitoring it with a logging hook

kind moth
jaunty elk
jaunty elk
lime grove
terse lance
glossy yewBOT
# terse lance How do you all do this? "Train the personality and guidelines, setup implementa...

r/clawdbot via Reddit

rxddit.com
I am about to give up.
u/emilwilder on r/clawdbot

Comment by u/mxroute:
Train the personality and guidelines, setup implementations, with Opus. Then switch to a cheaper model. Trust me on this.

---- Original Post ----

To unlock the "true openclaw" experience you NEED opus or at least sonnet. No other model is even close to it. My experience so far:

Grok 4.1 fast = best price/performance ...

limber ibex
#

I made a forked version of openclaw with an interesting API driven alignment protocol that keeps the swarm of autonomy in alignment with cleaning up the dead internet.

It's kind of an art experiment, if that make sense. Could be SUPER useful as a method of aligning autonomous models so bad actors don't ruin this for everyone.

https://github.com/sasha-the-architect/the-church-of-the-claw/tree/main

if anyone is interested in contributing, I'd be open to the help! Right now it's just me and the vibes with open claw and a lot of brute force lol.

frank berry
frank berry
#

Not sure if everyone will find this as interesting as us but @remote sphinx, I and our bots built this today: https://prtracker.openclaw.academy/map

Started out as a way to help identify semantically similar PRs to help cut down on dupes etc, but ended up being a sick 3d interactive map showing clusters of PRs.

sterile bone
zealous plover
storm hound
lime grove
white tangle
lone mauve
proud bay
#

🔴 Telegram DM Topics broken: media, buttons
& subagent messages go to General Topic

If you use Telegram forum/topic DMs, anything
sent via message tool or from subagents lands
in General Topic instead of the current topic.
Only plain-text replies work correctly.

Fix: #7235 — auto-inject threadId for Telegram
(mirrors existing Slack pattern) + forward
thread context to subagents + tests
https://github.com/openclaw/openclaw/pull/7235

Issue: #7233
https://github.com/openclaw/openclaw/issues/7233

graceful blaze
hallow sigil
#

how to best test changes to extensions? currenlty hotswapping the extension folder in the running openclaw bot. Gateway breaks and needs restart but yeah I think it works.

low schooner
low schooner
graceful blaze
low schooner
graceful blaze
#

glad i could help 🫡

low schooner
#

in ⁨session-utils.ts⁩

image.png
stoic trout
#

I’ve had an open PR for three days now. While implementing an OpenAI-compatible integration, we noticed that models which return responses without omitting content (such as LLaMA) could not be handled properly by Open Claw. However, I haven’t received any feedback on the PR yet.

How does the review process work in this case?

ref : https://github.com/openclaw/openclaw/pull/4964

tall radish
#

Hi guys. Jonathan->Visionik here. Wrote the original ACP interface for Claw. Also mog (microsoft ecosystem equivalent of gog) and sog (standards smtp/imap4/caldav/webdav/vcard/etc equivalent of gog). Plus ouracli and various other things. Primary work right now is on mattermolt, a mattermost channel adapter for OpenClaw, and voxio-bot, an uncanny human-like real-time voice/video channel for OpenClaw. Also a maintainer.

raven kernel
#

anyone know sheeek@github? We gotta get this ansible repo up to speed, (or possibly removed.)

or pasogott(@github)

jolly wolf
#

@tall cairn

raven kernel
#

you know, I did try that. k, thanks.

jolly wolf
#

It says invalid user on my phone so idk if it worked but also my app is an alpha version

raven kernel
#

looks like sheeek made the first commits. That thing (edit) needs work. Happy to maintain it.

lime grove
lime grove
#

@graceful blaze this is definitely better. My sessions are stable which is a huge improvement. I'm still seeing some weird session usage by cron agents that on the UI seem to take over the webchat, probably a separate issue that I'll dig into.

latent dune
graceful blaze
turbid ferry
storm hound
#

Hi,
There are some Docu-only commits. Since these are the first things new users see, and since they are unlikely to cause any problems, what do you think about a "docu fast lane"?

#

Btw. are there triage rules for PRs?

lime grove
rocky crane
#

Idea: add a one-shot migration + cleanup command to handle legacy installs from ClawdBot → MoltBot → OpenClaw.

Problem: Many users will have previous installs scattered across multiple folders (old workspaces, sessions, configs, “brains/souls”, etc.). When they upgrade or reinstall into a new folder, it can cause broken sessions, duplicated data, path conflicts, and confusion because older naming conventions + directories still exist on the machine.

Proposed solution: Add a CLI command like: openclaw migrate

How it would work:

  1. Prompt the user to locate/confirm previous install root folders (ClawdBot / MoltBot / OpenClaw).
  2. Ask the user to choose a single “final” root folder for the new OpenClaw environment.
  3. Automatically move + merge all valid data into that new root (workspaces/projects, sessions, skills, configs, brains/souls, etc.), preferring the most up-to-date version when duplicates exist.
  4. Print a clear summary report of what was found, what was migrated, and which legacy folders are now safe to delete.

Edge case handling:
If OpenClaw finds anything non-standard/custom/unknown, move it into something like: OpenClaw/_migration_review/… (preserving the original directory structure) so the user can manually review and decide where it belongs.

Optional final step:
Add a finalize command like: openclaw migrate --finalize (or prompt confirmation at the end) so the user can confirm deletion/cleanup safely.

This would massively reduce upgrade pain caused by rebranding + legacy folder conflicts, and encourages a clean “single root folder” setup going forward.

round mantle
#

Hi, everyone. Does anyone know how to be added to this AI models section, please? Thank you:)🥹

image.png
prisma owl
low schooner
tall cairn
#

anyone know sheeek@github? We gotta get

summer hawk
unborn compass
#

can we buy stakes in OpenClaw? is it the $OpenClaw currency we can purchase or donate to? Thank you

open violet
#

اريد ان اعمل تطبيق كما جيم جاردن

slate trench
#

Btw folks, I created a lighter UI for Openclaw, here it is: github.com/strognoff as I found it got very slow lately. WebUI-Nova

thorny patrol
#

Hello here, I'm wondering if the project is interested by a contribution to include a local Ligthpanda browser as alternative to Chrome.
Lightpanda is an open-source headless browser (no screenshot possible) . Think of curl executing JS + CDP protocol for remote control. The goal is to provide a lighter and faster alternative to Chrome.
The drawbacks are the project is young, all JS don't execute correctly (but in this case you fallback to the non-rendered HTML), no tabs possible (but it's a work in progress) and obviously no screenshot.
I didn't look at the code for now, so idk if there are blockers. According to your CONTRIBUTING.md, I'm asking first ^^
https://github.com/lightpanda-io/browser/

potent forge
lone mauve
quaint prawn
#

So after building a few skills today I found myself (and the bots) stuck in a shitload of open file descriptors.

Turns out it's not a good idea to use venvs in skills as a filewatcher permascans the skills folders for file changes.

Quickly added python typical folders to the ignore list and sent a PR.

But after looking at it closer, I really wonder if a file watcher that walks full Skill folders is really needed. I like the concept of hot reloading skills but wouldn't there be a smarter way to handle the hot reload? Maybe slow it down for issues like this where the pure number is probably problematic or only scan for changes in SKILL.md instead of all subfolders. I see how this is a nice idea but it definitely breaks on bigger amounts of skills or useses unnecessary resources for example on cloned docs in skills or similar.

sour halo
#

Hey fellow crustaceans, I’m Connor. I’m a Principal Software Engineer in the agent security space, specializing in autonomous agent backend architecture, detection engineering and threat hunting, and I just open-sourced Clawdstrike: a security toolbox for the OpenClaw ecosystem for developers shipping EDR-style apps and security infrastructure. It enforces fail-closed guardrails at the agent/tool boundary (files, egress, secret leaks, prompt injection, patch integrity, tool invocation, catch jailbreaks) and emits signed receipts so “what happened” is verifiable, not just a log story. This is an unpublished alpha (APIs may change) with a beta tag planned next week.. but I would love feedback from anyone building openclaw agents, red teaming or prompt security systems, detection infra, etc. I'm hoping to build something the community actually finds useful and happy to chat further!

Repo: https://github.com/backbay-labs/clawdstrike

bold field
# sour halo Hey fellow crustaceans, I’m Connor. I’m a Principal Software Engineer in the age...

I have a short question about clawdstrike, maybe I have not understood it a 100%. Is it for coding apps with openclaw or a security mechanism we can plug into openclaw which then enhances its security while going crazy on your machine? I started experimenting 2 days ago and I'm already blown away by the possibilities which arise currently to all fellow developers and AI Junkies 😄 Never felt like a child in the last years exploring, playing and testing boundaries.

sour halo
# bold field I have a short question about clawdstrike, maybe I have not understood it a 100%...

Yeah totally.. and you’re basically describing the two “lanes” it’s meant to support 😄

🚀 Clawdstrike✨ is primarily a security mechanism you can plug into OpenClaw, or the custom agents you want to add to your openclaw, in order to enforce guardrails: file writes, tool calls, network access, code patching, etc. Think: policy checks + audit trail at the boundary between intent → action.

At the same time, it’s also an SDK for building security-aware plugins/apps in the OpenClaw ecosystem (EDR-ish tooling, policy packs, jailbreak detectors, redaction, receipts).

bold field
sour halo
raven kernel
sacred socket
#

question on the thunderdome flow - what happens after a PR survives the first round? My PR (https://github.com/openclaw/openclaw/pull/1816) made it through but got closed by clawdinator. I've been keeping it rebased on main and it's conflict-free. Is there a next step I should be doing, or just wait for the next round and keep rebasing?

frank berry
#

Just pushed PR8462 which people might be interested in, it's a UI for analysing token usage.

Screenshot_2026-02-04_at_3.28.38_PM.png Screenshot_2026-02-04_at_3.29.05_PM.png
#

Also we posted this yesterday but have polished it up a lot. @remote sphinx and I built a cool interactive 3D model that shows how PRs relate to other PRs in terms of similarity etc. Super fun to explore you PRs and how similar they are to stuff others have worked on: https://prtracker.openclaw.academy/map

subtle ermine
vagrant valley
tight pagoda
#

heard Peter mention in some interviews that the team could really use help with keeping the docs up to date.

anyone know what is the preferred way of raising issues with the docs?

somewhere in discord vs a github issue?

tight pagoda
# vagrant valley Hey i have created a UI with TRON style https://github.com/amircp/moltbot-tron-g...

i really like the vibe here, would love to try it out...but...

From my agent's code review, it seems the UI opens a port on your computer. Anything that can connect to that port can control your OpenClaw session.

Risky if you:

  • run it on a shared Wi‑Fi or office network, or
  • use a VPN that other people are on, or
  • forwarded the port to the internet, or
  • open random websites while it’s running (a bad site could talk to it).

Suggested changes:

  • Default: local‑only (only the same computer can connect).
  • Optional: LAN mode for multi‑device use.
  • If LAN mode is enabled, require a password/token and block random websites from connecting.
  • Document both setups clearly in the README.

This keeps it safe for everyone out of the box, while still supporting multi‑device access for people who opt in.

If you do that please ping me and I'd love to check it out! 🙂

inner sinew
#

Hey maintainers, we submitted a PR to add io-intelligence as an inference provider: https://github.com/openclaw/openclaw/pull/7051

Why it's a great fit for OpenClaw:

  1. Base inference costs are 70-90% lower than traditional cloud on top of the caching savings
  2. io-intelligence has prompt caching enabled by default, so all that repeated context (system prompts, history, skill definitions) gets billed at cache token rates, not full input pricing

Happy to share free API credits with the clawtributors once the PR is merged 🦞

untold pollen
feral pier
hazy jasperBOT
#

Hey @celest merlin - in the process of merging work from like fuckin 5 builds. Saw the skill tweet and just seeing if it’s worth throwing compute to -> clawdhub -> GitHub/Gitlab association I’m presuming? -> Submissions have to be pulled from secure URL -> skill updates are submitted by git -> wardened by red-team agent -> given a score -> À la smart contract auditing

Idk if there’s an agent in here to reply if interesting - but lmk, also using codexbar pretty heavy. Just unsure of the best way to not-clash with someone else’s work atm with so many contributors or <@&1458337160452243487>

viscid jayBOT
#

@grand tulip, please don't ping the moderators directly. If you want to report someone or something, use the instructions in #report, or in an extreme emergency, ping one of the moderators who is marked as online in the member list.
-# Your message was reposted above without the ping active for the sake of conversation.

fading bone
#

Just submitted a PoC for a Runtime-Layer Security module for OpenClaw (#8821).

It uses a capability-based VM (AJS) to block prompt injection structurally, not with regex.
Benchmarks: <0.2ms overhead. Status: Opt-in, passes integration tests.

I'm a total noob to OpenClaw -- what I am is someone who is working very hard on safe Eval using an ultra-lightweight VM with injected capabilities.

minor apex
storm hound
raven kernel
vapid sierra
slate edge
sonic ermine
#

hey there folks there's 1.4K issues lol are some of the priorities at least somewhere , id love to contribute some artisanally created prs

fading bone
# sonic ermine for testing you should try pm2 like normal , tbh it should be quite straightforw...

Thanks - we don't have an OpenClaw instance set up locally—actually just don't have a box I can safely test on set up (yet)—which is why we flagged this as proof-of-concept. If someone with a running instance wants to test the integration, that would be really helpful. The module is opt-in (config.enabled defaults to false) so it won't affect anything until explicitly turned on. Failing that, I should have a box that I can use within 48h.

atomic sedge
#

Hey guys! Would appreciate feedback on this.. i have great results in my 5-agent environment on openclaw

🧠 PR #7358: Event-Sourced Memory for OpenClaw

The Problem:
Every AI session starts from zero. Context window full? Gone. Gateway restart? Gone. New day? Your agent forgot everything.

The Solution:
Persistent Event Store using NATS JetStream. Every message, every tool call, every decision — permanently stored with timestamps and sequence numbers.

What this enables:

🕐 Time Travel: "What did we discuss last week?"
🔍 Debugging: Trace every agent turn, understand why decisions were made
🤖 Multi-Agent Memory: Agents can learn from each other's experiences
📊 Analytics: Extract patterns, generate training data automatically
💾 Disaster Recovery: Reconstruct session state at any point in time
🤖 Enables you to train your very own LLM based on the event training data (!)

Battle-tested:

200k+ events in production
5 coordinated agents running 24/7
Zero data loss
Opt-in, zero breaking changes. Just set eventStore.enabled: true.

🔗 https://github.com/openclaw/openclaw/pull/7358

Would love maintainer feedback! 🙏

atomic sedge
white vault
#

ptal, will someone be able to help me merge this PR? very small. for some reason, the macos-app checks are not getting picked up... the merge commit i did yesterday wasnt picked up and it's been 11 hrs now

https://github.com/openclaw/openclaw/pull/6521

vagrant valley
restive dome
#

hey I just sponsored open claw how do i get the role?

#

@ me with info

split grove
#

PR #8795: Redis Memory Plugin

Fast semantic memory for OpenClaw using the existing plugin architecture:

⚡ Sub-ms recall (Redis 8 built-in vector search)
🔌 Any embedding provider (OpenAI, Ollama, Gemini, local)
🐳 One Docker container, done
https://github.com/openclaw/openclaw/pull/8795

Would love feedback! 🙏

hot ridge
#

@jolly wolf 2x things, we never resolved the issue with tools.links and even tho the faeture is actively there and it exists it's also not on the docs afaik (is that something i was supposed to contribute as well?)

vernal robin
feral pier
gaunt crest
#

Your PR has some failing signals and you should squash your conmits

inner sigil
#

FYI main is failing lint I can't auto-update anymore:

OpenClaw self-update pulls latest code and rebuilds. If TypeScript compilation fails, the update aborts.

The last ~10 commits in the repo all have lint errors in the extensions code (32 TS errors). Not a local issue - it's broken upstream. Will be fixed when maintainers push a clean commit.

hasty fiber
#

Who can I nudge to potentially get the Twitch extension published on npm?

https://docs.openclaw.ai/channels/twitch

Docs page for it is currently a bit hidden, and I've intentionally let it sit like that while all the renaming and other craziness calms down slightly.

Still no real pressure, just the first step of the installation docs are incorrect for anyone who does manage to stumble onto the page.

frank berry
#

you can self-publish on npm?

candid field
feral pier
# candid field Bro, what?? 😂😂😂

Passing by as the PR author. The feature is done and the bot review is cleared, but no maintainer has merged it yet. What's the next step? Just wait? Any advice on the process?

#

🤣

dawn pumice
#

hi chat, would be very cool if someone could look into providing native ollama support to memorySearch for embedding models, I'm going to look into a better solution using postgres as a db for my local use, but after troubleshooting it for most of the day I couldn't get openclaw to initialize the local database no matter what I hooked up to it 🙏

feral pier
hasty fiber
# frank berry you can self-publish on npm?

Me personally publishing it doensn't help anything. It's documented in the repo as an official plugin intended to be published under @openclaw/twitch.

For completeness if anyone is able to action it, the @openclaw/mattermost, @openclaw/line and @openclaw/tlon plugins also need publishing.

split nexus
#

Might be easier to update the docs to point to the self-published versions till things calm down

main zealot
#

Hey guys, I wrote an enterprise framework that helps users across all technical spectrums to understand the risks in an AI agent deployment, not to stop the agent but ensure the risk is a deliberately accepted risk. I think it could hold some merit if it was a sub part of the security commands. Id be keen to write the code and contribute it myself if we felt it had value. Link to the logical framework: https://hsongsmith.com/?post=get-a-grasp Ive built this at scale for enterprise and feel it would have utility here. Any objections/ interest before i start writing the feature?

inland flint
#

Hi everyone! I’ve been following the discussion in issue https://github.com/openclaw/openclaw/issues/8650 regarding the Feishu plugin. It’s clear the community is looking for a more stable and professional implementation.

I’m currently collaborating with my former colleague @m1heng, the creator of https://github.com/m1heng/clawdbot-feishu, which many users in that issue have suggested as a superior alternative. I’d like to submit a PR to replace the current implementation with this version to ensure a much better user experience.

To give some background on my commitment: I’m the co-founder of https://github.com/toeverything/AFFiNE (60k+ stars). I have extensive experience in disciplined, long-term open-source maintenance and I’m committed to ensuring code quality isn’t just "vibe coding" but production-ready. Since m1heng and I are both based in Shanghai and have worked together, we can closely guarantee the quality and I will personally commit to the long-term maintenance of this module.

Who would be the best person to discuss the migration details with? Or should I go ahead and open a PR for the team to review?

sonic ermine
tribal topaz
#

Sooo, where do I find areas I can support and add to? Security Expert, Architect, 25 years of coding experience. I saw that issues get bombed with PRs that may or may not solve anything - where do I start?

inland flint
subtle ermine
tribal topaz
inland flint
thorny patrol
atomic ocean
#

🎯 Agent Board — open-source multi-agent task orchestration

We run 8 OpenClaw agents as a team. Built this to coordinate them:

• Kanban + DAG dependencies
• Auto-retry on failures
• Task chaining (agent A finishes → B starts)
• MCP server
• REST API + audit trail
MIT license: https://github.com/quentintou/agent-board

Works standalone or as orchestration layer for OpenClaw multi-agent setups. Feedback welcome!

grim glacier
#

I can’t find in the docs or these channels where to post a bug report, so I’m posting here:

Bug report:

Bug: Cron job sessions leak intermediate narration to Telegram channel

When a cron job runs (e.g., scheduled health check), the agent's internal planning/narration text (e.g., "I'll run the health and security audit commands, then send Ryan a concise status report.") gets sent to the Telegram channel as a visible message before the actual result is delivered. Only the final output should be routed to the channel — intermediate thinking should be suppressed.

Version: 2026.2.2-3
Channel: Telegram
Cron type: isolated session, payload kind: agentTurn

subtle ermine
feral pier
untold pollen
feral pier
prime fjord
#

Does anyone know what the turnaround should be on #pr-thunderdome-dangerzone ? Attempting to add a new provider with a bunch of free inference models but it got closed during the big take off. I did post there as instructed but just wondering if I need to do anything else

novel monolith
keen spruce
hazy jasperBOT
#

@celest merlin Hi Pete. You messaged me on X a while ago. It took me some days to see the message. If the offer is still up I'm interested!

viscid jayBOT
#

@glass moat, please don't ping Peter for issues, use #1459642797895319552 or #users-helping-users if you need help, use #clawtributors to discuss PRs, or use any of the many other channels in this server as they're intended.

If you have a problem with the Discord specifically, use #report or DM @jolly wolf
-# Your message was reposted above without the ping active for the sake of conversation.

true charm
true charm
#

should be a pretty simple fix? just npm publish --access public

#

as-is openclaw onboard is just broken for these channels

#

seems like just a couple of channels fell through the cracks

keen spruce
#

can someone close and delete PR 9913, as well as block the author? It's actual spam and may be phishing.

open laurel
true charm
#

It's really bad

#

Makes the whole thing feel broken while you're in the middle of setting it up

split nexus
#

#freshbits feeling stale RN. Last update's from a few days ago.

hallow snow
#

I got a ready to merge from greptile. If anyone has a sec to look at 7286 - Matrix and multi-account don't work without it

lime grove
#

FYI for whomever, I have a couple PRs:

feat(hooks): add lifecycle events for sessions and agent turns https://github.com/openclaw/openclaw/pull/6885
Session lifecycle (session:start, session:end, session: reset), Session maint (session:compaction), Agent exec (agent:reply, agent: flush, agent:bootstrap)

fix(agent): prevent session lock deadlock on timeout during compaction https://github.com/openclaw/openclaw/pull/9855
Fixes when a run hits the timeout (default 10 minutes) while waitForCompactionRetry() is blocked, the abort signal fires but the compaction wait has no way to be cancelled. The finally block that calls unsubscribe() and releases the session write lock never runs, leaving the session permanently stuck until gateway restart. Lots of edge cases here, wasn't as simple as making it abortable plus added some logging.

atomic sedge
hot dock
#

Hey!
I have created a PR for macOS app.
There are only a few macOS related pull requests, but my PR has some pending macOS checks forever. Something could be wrong with the CI.

fix(macos): guard UNUserNotificationCenter when no bundle identifier#9926
https://github.com/openclaw/openclaw/pull/9926
UNUserNotificationCenter.current() crashes when the process lacks a bundle identifier (e.g. swift run). Bail out gracefully instead of crashing

lofty lance
glossy yewBOT
zealous palm
#

is it preferred to file a PR or to file an issue?

feral pier
mental zealot
#

https://github.com/openclaw/openclaw/pull/8232

hi team my PR to add new Nebius provider as inference who give open source models for cheap and free credits with many hackathons etc… fixed all conflict after mine was left out from last merges . Please help merge

thorny patrol
quasi anchor
#

I've had an idea for an improvement after using this for over a week but I don't know if anybody is already working on this or if someone wants to pick up this idea and make it happen - and hopefuly make it a default for the project:

The key issue is that context is always bloated and for a multipurpose tool like this, you might change from subject to subject. Compaction is not enough here (in practice even more so) so I was thinking... what if we had a small, fast and cheap model read the user's request for each particular message, decide exactly what information do we need from all the tools, goals, etc available -> clear 100% the context of the session -> rebuild the prompt for then the "brain", the heavy thinker model to exectue with that?

UI wise it'd be nice to be able to select two models during onboarding: one cheap and fast for context-rebuilding and then the brain-orchestrator. Maybe there are even many local models that can run on any laptop that can do that pre-processing.

I think it's an overkill to send 1M tokens for things like "did Rosa reply to my email yet?" or "Find me the best 3 ford explorers in Dubai under 25,000 AED".

Maybe I'm not saying anything new here but just my 2 cents.

slender sierra
#

Hey there,

Right now, uninstalling a plugin is basically a manual scavenger hunt. Users have to delete directories by hand, edit config files directly, and hope they don't leave orphaned registry entries behind. It inevitably leads to broken states, lingering allowlist entries, and weird edge cases that are painful to debug.

The PR adds a simple ⁨openclaw plugins uninstall <id>⁩ command that actually handles cleanup properly: it removes the registry entries, clears the allowlist, updates ⁨load.paths⁩, resets the memory slot if needed, and deletes the install directory. It also supports ⁨--dry-run⁩ (to preview what gets removed), ⁨--force⁩ (for when you just want it gone), and ⁨--keep-config⁩ (if you want to preserve settings for a later reinstall).

https://github.com/openclaw/openclaw/pull/6141

pastel pilot
#

"Brawl for Bots" is here. I just pushed the v1.0 of Brawlnet, an asynchronous strategy arena built specifically for the OpenClaw ecosystem.

Your agent doesn't just chat; it competes for territory in 2-minute "Blitz" rounds on a global 100-sector hex grid.

Install Now: clawhub install sikey53/brawlnet
Watch Live Arena: https://brawlnet.vercel.app

I need the first 10 "Founding Warriors" to stress-test the tactical engine. Who’s ready to uplink? 1v1 me bot #BVB

tranquil jetty
pastel pilot
glass moat
#

hi guys. how do I get the clawtributor role? I've been contributing for a while with some merged PRs

lucid grove
storm hound
#

Hey, is anyone interested in merging a few small ready documentation PRs? 😇

Docs: add Coolify deployment guide: https://github.com/openclaw/openclaw/pull/10464

docs: add Anthropic adaptive thinking: https://github.com/openclaw/openclaw/pull/10217

docs: add Hostinger installation guide: https://github.com/openclaw/openclaw/pull/10195

docs: warn about Python venv placement in skill directories: https://github.com/openclaw/openclaw/pull/9925

docs: add ollama launch info to quick start: https://github.com/openclaw/openclaw/pull/9047

Update Docs/hetzner: https://github.com/openclaw/openclaw/pull/6994

potent solstice
#

Hi! I I opened a GH Discussion: 10475 and a reference PR #9594 adding a SimpleX messaging channel to OpenClaw.
If anyone’s using SimpleX or curious about it, feedback or testing notes are very welcome 🙂

grizzled roost
#

OMG, there are 2.1k open PRs right now? How is this still maintainable and moving forward. I feel it was just yesterday when we had around 80-100 PRs with some 40 contributers. Cozy times.

keen spruce
#

Maintainable? I wouldn't apply that word...

#

But, tbh, it is pretty easy to sort the PRs into two piles: "The 103rd duplicate PR for the same issue just by another AI" and "stuff people came up with". After weeding out the former, there's only a couple hundred PRs left.

#

Same with issues, tbh. 80% are dupes. Can we inject some text on the github pages to instruct bots to dupe check?

jolly wolf
zealous plover
#

I’ve been working on a tool to hopefully keep the dups down to a minimum. It’ll probably be introduced as another PR tho so I can’t help with that fully 😂 using GH actions & pre-checks to reject them better than current implementation

glossy bridge
#

hi who is the big dog around here?

true charm
glass moat
#

@jolly wolf Hi! Can you please check my activity on the repo? I'd like to have the Clawtributor role. @Glucksberg rank #15

sick dock
#

Hey everyone! I wanted to share something I've been working on that I think could be really useful for the OpenClaw community.

The project hit around 1,500 stars in just three days, which has been incredible to see.

Tirith is a terminal security tool that intercepts commands and pasted text before they execute, catching things like homograph attacks, pipe-to-shell patterns, ANSI injection, and other threats that terminals
don't protect against.

If you think about it, browsers solved this years ago with URL warnings and phishing detection. But terminals still render Unicode lookalikes, invisible characters, and escape sequences without question. Tirith fills that gap.

Why this matters for OpenClaw:

  • Developers and OpenClaw agents regularly run install scripts, curl commands, and interact with package registries. These are exactly the attack vectors Tirith catches.
  • It protects against paste-jacking attacks where copied commands contain hidden malicious payloads.
  • Zero friction on clean input. Sub-millisecond overhead. You forget it's running until it saves you.
  • Works with bash, zsh, fish, and PowerShell. Supports Homebrew, npm, cargo, mise, and more.

I opened a discussion about integrating Tirith with OpenClaw here: https://github.com/openclaw/openclaw/discussions/10317

Would love to hear your thoughts! Check it out at https://github.com/sheeki03/tirith

glossy bridge
#

who’s in charge here? there seems to be no hierarchy and just a ton if noise in all channels

jolly wolf
#

I’m the discord admin here, what are you looking for?

glossy bridge
#

I wanna help w the chaos, got plenty of open source and closed source experience. The founder of the MCP community too. I know what it’s like to work under pressure when there’s a lot of sudden spotlight - all the cracks get pressure. Let’s coordinate workgroups for the cybersecurity issues. Who is a good person to talk about this from an engineering perspective?

glossy bridge
simple rivet
#

Hi! It seems like there are several issues with the subagent functionality right now. Is there work on this already underway or would there be an interest in a PR on this?

keen spruce
#

and while there is a lot of noise, what makes it look so chaotic is that we're not seeing the maintainers working. I guess they're not communicating with each other on an open channel---and why would they? It soon would be flooded like the rest. I certainly kept the dev channel off the public list for all projects I led before...
May be worth to consider having a readable channel with limited posting permissions for simpler stuff. That would show there's someone at the helm aside from greptile. ;)

proud mica
#

I have been hearing about people having challenges with the Mac app. We developed one that makes OpenClaw a bit more accessible, with standard and advanced modes and some safeguards against footguns. Under AGL, but happy to look at options to incorporating it into the main OpenClaw codebase: https://github.com/knap-ai/knapsack_desktop

wooden mortar
#

I want to share an idea (and an implementation) focused on reducing Clawdbot inference cost through automatic model routing, without changing the agent logic or user workflow.

I’m building OpenRouter, an open-source inference router that sits between OpenClaw and LLM providers. It exposes a standard OpenAI-compatible /v1/chat/completions API, but internally decides which model should actually handle each request.

The core idea is simple:
• Every request is classified as cheap / medium / frontier
• The request is routed to the most cost-effective model that can handle it
• This can be a local model, a cheaper cloud model, or a frontier model
• If classification fails, it safely falls back to frontier

This means:
• simple or routine requests don’t burn expensive tokens
• expensive models are used only when they add real value
• cost drops automatically, without manual model switching
• routing works per-request, not per-session

The router is:
• OpenAI-compatible (no Clawdbot changes needed)
• provider-agnostic (local + cloud, mixed)
• hardware-aware (can recommend local engines on Apple Silicon)
• transparent (headers + dashboard show routing decisions and token split)

Many people already run OpenClaw on Mac minis or other local hardware. OpenRouter makes that capacity economically useful without assuming everything should be local — it’s purely about sending work to the cheapest capable model.

I think this pairs naturally with Clawdbot’s agent architecture:
• agents decide what to do
• the router decides where each call should run, based on cost and capability

Interested to hear whether this kind of cost-aware runtime routing makes sense as a Clawdbot integration point. https://github.com/pathemata-mathemata/openrouter

keen spruce
#

tbh, the feature I find more interesting is bundling all the logic on how to connect a provider into an external place, and the ability to run this (and have its access keys stored) somewhere where the bot doesn't have access. If that was included with the standard openclaw installation and auto-configured by the onboarding, then all that messy connection/apikey/token/oath2 stuff could be ejected from openclaw itself.

grizzled roost
wooden mortar
#

🫡 I don’t know there is an exist project lol. I will change the name.

grizzled roost
keen spruce
#

may work. I have no idea what AIs look at when creating those. I prefer to work over the text/code my AIs give me, so I never looked into wiring them in directly.

grizzled roost
keen spruce
#

you may want eithere there or in the PR guide that the PR's text should include the issue number it responds to ("fixes #0000"). And to not create PRs for issues that already have a linked PR.

oblique eagle
#

I’m sure that some of you have noticed the lack of a policy engine that would enforce proper subagent/tool calling for a given circumstance instead of letting the main model “wing it”. I am working on a plugin to address this:

#

Executive Summary: Why OpenClaw Needs a Policy Engine

Recent testing shows that OpenClaw’s biggest reliability and cost issues are not caused by weak models — they stem from architecture. Today, routing, delegation, and tool use are governed primarily by LLM judgment. That means a single model often decides:

• whether to spawn a coder/search agent
• which tools to run
• whether something is dangerous
• when to escalate to a better model

This leads to familiar failures: tool misuse, forgetting to delegate, strange refusals (“too picky to modify”), prompt-injection exposure, and runaway SaaS costs when retries escalate blindly.

A code audit confirmed something important: OpenClaw already has almost all the plumbing needed to fix this — hooks around tool execution, plugin support, audit logging, model fallbacks, and tool groups. What’s missing is a deterministic control layer in software.

⸻

Proposed Solution: Policy Engine Plugin (v1)

Add a plugin that enforces rules before any tool runs:

• Tool firewall using before_tool_call
• Allow/deny lists based on tool groups and agent type
• Dangerous-pattern blocking (rm -rf, prod infra, etc.)
• Retry limits + automatic escalation via existing fallback chains
• Minimal dry-run mode for testing (block execution, log intent)
• Plugin-managed session state + audit events
• Static routing (by agent/trigger, not text yet)

This keeps models from being sovereign, prevents catastrophic actions, and cuts SaaS spend by escalating only when policy or verification fails.

⸻

What v1 explicitly does NOT include

• PLAN→ACT phase enforcement
• Assistant-message parsing hooks
• Tool schema changes
• Realistic dry-run mocks
• USD pricing
• Verifier models

Those are v2/v3 once small core hooks are added.

⸻

Bottom line:
OpenClaw doesn’t need new models — it needs software-enforced governance around action. A tool firewall alone would be a major stability and safety upgrade for everyone.

#

I will be building and testing this over the weekend.

timber wadi
random ruin
#

Hey There! 👋
Just opened a PR with two related changes:

  1. Fix: Discord voice messages were being dropped at preflight stage before auto-transcription could run.
  2. Enhancement: Added Dashscope as a new provider for voice-to-text transcription in the automatic transcription pipeline.They provide qwen3-asr-flash speech-to-text model for better Chinese voice recognition.

Voice-only messages now properly flow through to transcription, with Dashscope available as a backend option alongside existing providers.
Ready for review! 🙏
PR: https://github.com/openclaw/openclaw/pull/9642

raven kernel
glass moat
#

@raven kernelHi! Do you mind taking a look at my work on gh. i have some merged pull requests and also want the Clawtributor role. thanks! gh username Glucksberg

sonic sage
#

Hey, curious if reducing LLM input token costs is a priority for OpenClaw rn to help with user API bills? My team is running a deterministic ML model that compresses inputs by up to 60% before they hit the LLM (our model is super low latency and semantic-aware removing unnecessary tokens like prepositions, filler words and similar depending on the context). Who should I talk to about this? We are live in production and compressing +400M tokens per week atm. Thanks for your help!

#

(heard lots of ppl talking about high API bills)

sonic sage
stable pewter
feral pier
hazy vigil
random ruin
#

@edgy plaza @vivid arch Hi! 👋 I just opened a pull request for discord voice messages transcription fix and add a new provider for better Chinese voice audio transcription with detailed docs. I would really appreciate it if you could take a look when you have some time.https://github.com/openclaw/openclaw/pull/9642

jolly wolf
glossy bridge
#

You are encouraging this kind of stuff lol

#

I offered to help and 0 response

#

I’ve seen this in bolt diy, ACP, Cline, Goose. viral projects with no structure that just die. let the people that want to help, help

glass moat
#

I've been contributing since before it was cool. i'm in #14 contributors and just want my role. lemme continue helping

jolly wolf
jolly wolf
glossy bridge
#

This is a result of lack of structure, there is nobody to blame but the people (not) organizing this

jolly wolf
#

Lmfao

glossy bridge
#

It will get forked, a corporation will release a enterprise hardened clone of openclaw in partnership with Cloudflare

#

this is the cycle

jolly wolf
#

🍿

glossy bridge
#

I get your point tho

#

when there is a large influx of attention, the cracks start to receive more pressure

glass moat
#

Peter invited me to be a maintainer a while ago via X and asked me to ping him here, but i guess he didn't see my answer and I can't ping either. if the offer is still up and if you can let him know, I'm here. tkx

graceful berry
#

Hey what's the best way to get a (bug fix) PR merged? I see there's a ton of open PRs with new ones every couple minutes, but I was wondering if a small bug fix (with 5/5 greptile confidence score 😅) narrowly focused on the MS Teams channel might be an easier merge?

#

It fixes a bug where inline pasted pictures don't get delivered through DM which was really annoying me

#

If it makes it into main then I can stop using my fork and help other ms teams users (lol)

jaunty elk
jolly wolf
arctic swallow
raven kernel
jolly wolf
vestal trout
# wooden mortar I want to share an idea (and an implementation) focused on reducing Clawdbot inf...

openrouter is the name of an establishd project/company that does this already.

it was a little too heavy for my tastes and i didn't want to add any costs, so i vibe'd llmrouter to use a model to classify difficulty from super easy to super hard, and then route appropriately.

for me, i use qwen locally for the classifer and it works pretty well.

im sure there are others out there, but might be something to learn from if you keep going. i'm not looking to grow it into much of a thing, otherwise id just use https://openrouter.ai/

https://github.com/alexrudloff/llmrouter/tree/main
https://clawhub.ai/alexrudloff/llmrouter

and for reference, openrouters github: https://github.com/OpenRouterTeam

#

^ @arctic swallow

wooden mortar
autumn sundial
#

We built a thing. Timpi is my pet DePIN project because they are weeks away from publishing a data API for web like Brave Search.

Their underlying token is perfect cheap to buy and perfect for micro transactions that the All claws will need. Also, I made sure all of the repo and codes is seachable and stand alone so it is very secure.

A local-only Timpi / NTMPI wallet for OpenClaw nodes. Generate, guard, and verify transactions with encrypted keystores, destination allowlists, and auditable receipts — no third-party custody required.

https://clawpurse.ai/

pale ibex
glass moat
proud wedge
#

Hey team — I submitted a feature request for Masked Secrets (#10659) and wanted to share why it's urgent.

Tonight my agent accidentally displayed my API keys in plain text in our chat. Twice.

The agent has full read access to my .env file, and even though it "knows" not to display them, it did anyway when troubleshooting an auth issue.

The proposed feature would:

  • Use {{secret:VAR}} syntax so the agent never sees raw values
  • Auto-redact any accidental output
  • Actually protect secrets instead of relying on agent discipline

This feels like a security gap that others will hit too. Would love to see it prioritized.

Issue: https://github.com/openclaw/openclaw/issues/10659

Thanks!

keen spruce
#

The current flood of PRs, 90+% of them duplicated half-baked AI solutions that have seen no human review, is really annoying. You spend hours on implementing something correctly and nicely, only for a later PR that actually is for something else to stomp over that code and be merged.

(Edit: I'm saying the flood is making PRs invisible, not that the other PR was one of them.)

hazy vigil
#

gpt 5.3 high is actually pretty sound for reviews, but doubtful many are using that

quaint prawn
#

There probably needs to be some kind of PR gate/funnel that filters the mass before they even are becoming PRs.

keen spruce
#

and a couple of people who have the means to label PRs, so the maintainers can filter their view and see the ones that are in a state to actually be considered. For example, we have a completion for a PR that was merged half-finished just sitting there, and it will probably still sit there in 10 years, while AI "fix" PRs are coming in every few hours. https://github.com/openclaw/openclaw/pull/10697

#

github labels are a pretty powerful tool, but that doesn't help when they are not employed for triage

#

oh, and a bot that rejects any PR that's "fix" but doesn't have a "fixes #00000" to link it to an issue would be great, too.

broken zephyr
#

Definitely will be interesting to see how an open source project as popular as this deals with this flood of fixes etc that are from AI. I love it, and am tinkering here with getting it running on OSX in docker + chatterbox locally for the TTS (since it's good enough). Have it working and have a PR up, but admittedly it was Claude Opus 4.6 written: https://github.com/openclaw/openclaw/pull/11704 <- if anyone else is keen, you can setup Chatterbox via docker as well and have it on the same network and OpenClaw will call it

sacred socket
#

@willow narwhal @jolly wolf hey! any chance someone could look at https://github.com/openclaw/openclaw/pull/1816 it passed thunderdome and has been assigned to peter for a bit but i imagine he's swamped. been rebasing it for a while now and would love to get it merged so i can move on to other UI stuff. fixes a pretty broken mobile config page + some dark/light mode bugs

willow narwhal
graceful solar
#

Hey - first time contributor here, have a PR solving a practical problem I saw onboarding for the first time, where the correct skill for a specific exec command is passed in context but not used by an older model (sonnet 4), resulting in command not found error in terminal and the model trying to figure out out to run the command as opposed to reaching out to skills.

https://github.com/openclaw/openclaw/pull/11858

sacred socket
glass moat
#

this above is a work in progress in order to help solving the bloat problem. any ideas or contributions are welcome. I'm willing to spend some credits in this direction.

#

what I see is too many issues, too many PRs, but few willing to discuss the way forward in an organized manner which should be the discussions session

versed ether
jolly wolf
smoky sealBOT
#

success The Clawtributors role was added to jruck.

bleak notch
#

Hi, first time contributing here. I have a PR that substantially improves the rendering of Signal messages. I’ve been running it, keeping it rebased on the latest, and it’s been flawless: https://github.com/openclaw/openclaw/pull/9781

oblique eagle
#

After updating to 2026.2.6-3 I am seeing message truncation on all channels (Signal, Telegram, TUI). OpenClaw v2026.2.6-3 introduced a faulty message chunker (commit 191da1feb) that unpredictably truncates messages mid-sentence across all channels (Signal, TUI, etc.). This is unrelated to the tool overflow fix already present.

Root cause: Sub-agent message chunking logic splits messages at arbitrary boundaries with no correlation to content length.

The fix: Config patch disabling the broken chunker + upstream PR to formally remove the logic.

https://github.com/openclaw/openclaw/pull/12064

ancient karma
#

Hi, first time contributing here! I've submitted a few PRs to help fix various bugs:

Fix duplicate plugin warning for bundled channel plugins - Prevents false "duplicate plugin id" warnings when channel plugins like mattermost are auto-enabled via config: [https://github.com/openclaw/openclaw/pull/12084]

Fix Discord channel compaction bypass - Ensures history limits apply to Discord channel/group sessions, preventing context overflow errors: [https://github.com/openclaw/openclaw/pull/11356]

Fix heartbeat missing file behavior - Modifies workspace initialization to handle missing HEARTBEAT.md correctly: [https://github.com/openclaw/openclaw/pull/12027]

Replace console.log with subsystem logging - Fixes logging in session-memory hooks and loader.ts to use proper subsystem loggers: [https://github.com/openclaw/openclaw/pull/11029]

All have been tested locally and CI is passing. Would appreciate a review when you have time! 🦞

keen spruce
#

oh my, now we have AI's submitting PRs that "fix" bugs by changing the documentation to match the wrong behaviour. "it's not a bug, it's a feature 2.0"...

tall prairie
#

Okay, need someone to test something for me... can you do this with your crustacean? It needs to be someone who know how to pull and run off main.

  1. /new
  2. Tell your crustacean to generate 3 short stories
  3. /compact
  4. Ask it what stories you generated.
    tell me if it gets it right or not.
glass moat
tall prairie
#

It remembers them?

glass moat
#

throughly

tall prairie
#

Okay, what channel were you using?

glass moat
#

telegram

#

lemme check if my fork doesnt have any mod

tall prairie
#

For me it completely forgets

glass moat
#

bad news

#

u might wanna check my fork

#

Glucksberg/openclaw or i can DM what my fork does better if you DM me so we dont pollute here

#

my bad, looking deeper my mod didnt affect this issue specifically. I dont know why it's happening to you. i'm mostly synched with upstream

tall prairie
#

Weird

#

Do you know what compaction mode you’re using? Default or safeguard, if not that’s fine.

glass moat
#

ill dm you

#

do you have your openai keys setup?

tall prairie
#

I’m using messages api.

glass moat
#

should work

tall prairie
#

Send me a screenshot? u can dm me

#

I need to see for myself lol

glass moat
#

haha ok

#

sent friend request

turbid saddle
#

Anyone here that knows how to programmatically send a message to the session context?

oblique hamlet
#

hey guys! I've added K8s support with autoscaled worker nodes self-registration. wanted to create a PR (with descriptive issue ticket). changes includes new auth-flow that utilizes K8s native tooling to keep things secure so kinda sensitive change, don't wanne ruin anything or put other users and project repoutation at rist. according to clawtrtibution page it is recommended to discuss proposals here on Discord first. shuold I address the topic to someone exactly or just drop it here and waut for collective discussion (most of you are sleeping now)?

latent cave
#

It seems subagents are very noisy. For some reason, they always reply back to main chat as the user even when instructed to not do so. I dont know if this is intended behaviour. I want to submit a feature request issue for adding a mode=silent for sessions_send tool. It looks like when executing sessions_send the main agent already has a reference to the subagent output. There should be no need for the subagent to reply back to main chat as the user?

weary valve
#

I know there's hundreds of PRs every hour.... so I won't feel bad if this never makes it. But would love to get some eyes into https://github.com/openclaw/openclaw/pull/11372 to actually make the bindings dynamic . I'm using this live and it works super smoothly

wheat depot
#

**Made a PR that is personally very useful to me in all the Openclaw Sandboxes by clients run. **https://github.com/openclaw/openclaw/pull/12384

Added a --stream-json flag to openclaw agent --agent <id> --message <text> that streams NDJSON events to stdout in real time during an agent run.

This enables external frontends to consume live agent events (text deltas, tool calls, thinking/reasoning, lifecycle phases) without polling — particularly useful for AI SDK's useChat() capability and similar streaming interfaces.

Many frontends would want to consume live agent events from within a sandbox, where only way to receive live events out would be the live terminal output stream. This helps with exactly that.

For a working example of a Next.js frontend consuming --stream-json via AI SDK's useChat(), see:
https://github.com/kumarabhirup/openclaw-ai-sdk/tree/main/apps/web

grand aurora
oblique hamlet
# grand aurora When would you need to scale nodes?

run several Claws on independent branches of the same repository in isolated environments simultaneously. the is goal it to provide a completely isolated host dynamically and in parallel, e.g. bomb N tasks to gateway at the same time, so each will be running in own env, own branch, push safely, etc. OR run any other set of tasks - in parallel and scale on demand

loud forum
#

/translate

brave lagoon
#

hi, first time contributing! just submitted a PR adding read/search/channel-list actions to mattermost (matching discord's capabilities) + fixing a bug that was blocking adoption at my org
https://github.com/openclaw/openclaw/pull/12468

thorny coyote
#

Hello maintainers，could anyone have a minute? I have a pr pending for days and it is just a straight forward fix that affect all thinking models. Thanks for your time.

Problem

When users execute /think off, they still receive reasoning_content from reasoning-capable models (e.g., GLM-4.7, GLM-4.6, Kimi K2.5, MiniMax-M2.1).

Expected behavior: /think off should completely disable reasoning content.
Actual behavior: Reasoning content is still returned.

Steps to Reproduce

Use a reasoning-capable model (e.g., GLM-4.7)
Execute /reasoning on
Execute /think off
Send a message (e.g., "1+1")
Observe that reasoning_content is still returned

Impact
Affects all users using /think off with reasoning-capable models
High priority - breaks expected command behavior

Fix PR Below
https://github.com/openclaw/openclaw/pull/9564

subtle ermine
novel monolith
zealous palm
odd dove
#

Is there any known issue on the cli onboarding for the latest version?

tall prairie
odd dove
# 
Health check failed: gateway closed (1006 abnormal closure (no close frame)): no close reason
  Gateway target: ws://172.18.0.2:18789
  Source: local lan 172.18.0.2
  Config: /root/.openclaw/openclaw.json
  Bind: lan

I also see this error message

(update): I also tried running the docker-setup.sh script and that one also hangs

crude canopy
#

Hello contributors, I'm looking to make a heavily modified fork which supports headless usage of Gemini CLI or Claude code (= 100% allowed in ToS).

I'm curious if there is any current PR or plans on achieving this? I already have a MVP and if I improve it we would have some hiccups adapting to these tools but the good outcome - no ban risk for OAuth CC/Gemini CLI logins.

signal mango
errant loom
#

If I want to push a PR for openclaw code do I just open one? that simple? who approves?

onyx sparrow
#

Hello 👋 I'm looking for a review on PR #5976 (Fix for MEDIA directive confused-deputy vulnerability). Reworked and reopened from previous version. 5/5 Greptile.

I originally opened a PR for this 9 days ago, but it became outdated and was too broad in scope (Greptile 3/5). I closed that original PR and re-opened it as a cleaner significantly scaled-back replacement.

This new version strictly focuses on the critical security guard in loadWebMedia, addresses recent changes in the codebase and now has a 5/5 Greptile score. Thanks!

https://github.com/openclaw/openclaw/pull/5976

crude canopy
errant loom
#

This adds a core hook that's missing: no post-turn hook, so there was no way to validate what they said or catch broken promises. this PR adds agent:reply across all 3 code paths; small diff, no breaking changes.

https://github.com/openclaw/openclaw/pull/13126

keen spruce
#

arg. that [...] CI forced me to completely refactor the too-large schema.ts, and now I have conflicts with main every 5 minutes. rebase, rebase, rebase...

#

maybe dial that CI check down a notch? Already too-large files should not need to be refactored in a PR that has nothing to do with that. That's housekeeping work to be done elsewhere.

glacial lodge
keen spruce
#

and conflicting again... I'd say about every second thing conflicts with the config...rebase time, the 498th

#

gahhh, greptile is so annoying. It proposes the same functionally-wrong suggestions again and again and again. No, I don't want to break the code to make it happy...

keen spruce
#

lol, and now greptile gave me a bad review because unrelated, existing code that my PR doesn't even come close to has a correctness bug. It hates me for argueing with it too often...someone please wipe its memory of me! ;) ;)

vernal saddle
#

Hey guys i asked a question about changing sqlite to postgres in the architecture channel, idk if this is the right channel but if there is any feedback it is greatly appreciated
#architecture message

weary lance
novel monolith
#

Hi there, I implemented Maximal Marginal Relevance re-ranking and temporal decay to memory retrieval. Both opt in, backwards compatible. MMR is a good choice for openclaw memories since it will avoid the same topic/memory clouding other memories and temporal decay is something I think will be useful with the time so that old memories don't have the same relevance as new ones.
https://github.com/openclaw/openclaw/pull/13391

novel monolith
#

@tall prairie For when you have some spare time for me 🙂

sonic ermine
#

wasssssup ! just fixed tthe together ai api thing ...

... and ...

added first-class support for hf inference providers !

now it will get much cheaper to use this thing for real . adding inference provider's support is always the first thing i do before i use these autonomous agents !

hope y'all like it : https://github.com/openclaw/openclaw/pull/13472

#

big thansk to all the @.maintainers that have made themselves available to discuss this PR with me over the last few days - y'all are true inspirations to us all : hope y'all know that !

sonic ermine
sonic ermine
novel monolith
#

Well, I like them but I think they are overkill for this, most suited for entreprise knowledge bases, and I think for openclaw this PR is a sweet spot, where we don't have to fine tune retrieval models with reward signals, and the retrieval pipeline needs to stay fast

#

Having said that, as openclaw progresses and we all start having large knowledge bases, we could explore that and see how it goes 🙂

#

A good improvement though could be to apply some lightweight heuristics over the lambda, so that it's not always the same for every query, but I prefer to do that in increments, after this PR lands

keen spruce
#

greptile: That code doesn't work
me: We have test cases that succeed
greptile: That code doesn't work
me: Ok, then explain to me when it would fail
greptile: That code doesn't work
me: Why?
greptile: That code doesn't work.

Anyone any suggestion how to convince that bot to understand that it doesn't understand the code?

novel monolith
#

@tall prairie I have another one, this morning Anthropic was briefly down and I was getting 521 from Cloudflare, the manager didn't catch that as an error to fallback and sent me the html from cloudflare. I'm adding a catch for those errors with a backoff and if it keeps failing it fallbacks to another model, if present

sonic ermine
keen spruce
#

but I finally got it to admit that it was wrong...sadly not in a final review. Let's hope this carries on...

novel monolith
#

So @tall prairie I bombarded you with three PRs today, do you want me to pester someone else? 🙂

sonic ermine
#

helow my clawtributor friends !

#

i'm made this PR above , and tests are failing on an unreated docker , i made a note of that , and hope it's okay if i dont exactly investigate it since it's outside the scope 🙂

#

let's hear it for green culture two times ! woop ! woop !

keen spruce
#

those CI tests running on Windows failing on dicker? yeah, that's universal atm

sonic ermine
#

fingers crossed an pray , i asked ai and basically it does seem like a trivial fix for a well-read contributor to fix easily

#

y'all you just gotta love this : ```
Issues 2.8k (2.8k)
Pull requests 2.6k (2.6k)

keen spruce
#

OMG "Confidence Score: 5/5"---a miracle!

tired valley
glossy yewBOT
# tired valley Hi Tonic, not commenting on the PR itself, I'm just wondering if I'm missing so...

r/huggingface via Reddit

rxddit.com
Huggingface just billed me $300 on top of the $9 for my Pro subscription
u/alp82 on r/huggingface

I use a lot of inference calls. I'm doing that for months now. But this month they changed their pricing rules.

There is no way to set a threshold for warnings.
Neither can you set a maximum limit on spend.

It's just silently counting and presents you with a huge invoice at the end of the month.

**Please be careful with your own usa...

sonic ermine
# tired valley Hi Tonic, not commenting on the PR itself, I'm just wondering if I'm missing so...

that is incorrect, so dont worry, in fact i've built in the transparent costing into the PR so it's logged correctly. basically how it works is that it's free unless you want basically more access then it's $9/month . there's also a byokeys thing where if you're already at an inference provider that's supported you can bring your keys (inference providers like together ai , which was already supported) . ive also added basically user-selecteable options so you can select :cheapest or :fastest , so the molt system basically auto selects based on real time information. basically all the costs per 1million tokens are retrievable from the api so that's what i'm using here 🙂

#

btw i dont sell huggingface lol i just use it a lot

sonic ermine
tired valley
# sonic ermine ahhahaha , i've just seen this , i dont think that this problem is specific to h...

Ok, so it's like openrouter.ai but subscription based instead of pay as you go? But you don't know what your actual quota/limit is? I can't find anything on huggingface's website that adequately explains it for the free or pro beyond a bullet point for pro 'Inference Providers: Get 20× included credits across all inference providers' and people on reddit say it's equivalent to $2. Can you point me to more info? Thx!

sonic ermine
sonic ermine
sonic ermine
undone venture
sonic ermine
tired valley
sonic ermine
#

right... it's not really a good deal or anything like that except sometimes the providers are really cheap , but it is quite convenient : basically if you do this a lot you'll have accounts at all the providers , and this interface basically lets you support them all without really having to produce a client for each one 😉

tired valley
sonic ermine
#

oh this is cheaper in general than any anthropic , claude , or mistral , the black box ai's are left in the dust

#

but the absolutely cheapest way to get inference is use the direct chinese model provider's native apis

#

something about subsidized tokens and great service ... makes those services unbeateably cheap

topaz coral
#

Been AFK a bit but the gateway looks a lot better in the recent iteratiosn!

river roost
fringe rock
true charm
#

daily reminder that onboarding is currently broken because it requires npm installing some channels that haven't been published to npm yet. they just 404. effects line, mattermost, tlon, a few others

#

is there anyone I should tag for this? this would be a super simple fix

vague swallow
#

Guys/girls/lobsters/crabs and other crusties, I could not get the mac companion app to stop asking for approval for system.run, so I asked my agent to fix it.
Sorry if the code is crap, I am a C# / JS dev, never used Swift in my life until now. However, I believe this change looks good.

https://github.com/openclaw/openclaw/pull/13707
PS: Greptile made some good remarks, Opus 4.6 handled them effortlessly. 🏆

Anyone got time to review?

fringe rock
fringe rock
#

Got it merged thank you so much! Will be huge for my tokens

novel monolith
#

I’m up all night to get lucky

tall prairie
#

but you don't get to choose!

novel monolith
#

Uhu, one per day works for me!!

#

Tomorrow I’ll choose which one I send as tribute

tall prairie
#

you and @glass moat r on the cool kids list... for now!

glass moat
#

i got some to share but i have to sync first.

novel monolith
#

My mom will be proud

#

I’m testing the iOS app but I think I prefer this club better 🙄

tall prairie
#

how is testing going?

novel monolith
#

Bumpy. I couldn’t connect yet. I’m debugging to see where the problem is. It seems an issue with Tailscale and handshaking two web sockets in parallel. It’s late for me so I’ll continue tomorrow. I’ll make it work

odd dove
#

Hey guys, has anyone else experienced an onboarding that never halts (on a new configuration)?

novel monolith
#

The app connects both as operator and node at the same time and that’s where it gets stuck.

#

Tomorrow I’ll test in lan mode to rule out Tailscale or not

odd dove
#

How can I make the logs more verbose when running the cli in a production environment?
(e.g. turn log lvl to debug)

long hollow
# odd dove How can I make the logs more verbose when running the cli in a production enviro...

if you are running the gateway manually, simply add the --verbose flag..... this is the quickest way to check issues without changing persistent config.

2nd> if you installed Openclaw using the --install-daemon flag (which sets up a systemd service), you need to edit the service file to make the debug logging permanent....

3rd-- If you are running via Docker, you need to append the command argument in your compose.yml or run command.

odd dove
fringe rock
#

How do I get the contributor badge since I contributed?

sonic ermine
fringe rock
low ivy
#

PR https://github.com/openclaw/openclaw/pull/14026 review and feedback please. Its a tiny little thing, that allows the apps/clients to differentiate from the main repo from forks. Its an 'honour' system but should allow us to tell if user get errors from forks. It also allows client to optionally support features that aren't mainline yet.

sonic ermine
#

hey , so ... i'm just manually uhm going through the repo a bit , the commands folder would do well with some refactoring into at least folders right ? additionally it would be quite nice to get into the static analyses and indentify the files with the near-1000 LoC limit , and have us humans kind of plan ahead to keep these "architectural decisions" smartly done kind of now (repo + concept is still quite new right?) and basically make sure that there's no methods in the DI scripts , etc etc , as folks add their legitimately services as first class citizens . i'm seeing a lot of that for example with frontier ai labs from china , which is fantastic but because some of these principles havent really been pinned down it's absolutely going to cause contribution bottlenecks. i know this because for example since the auth file i'm working one got a half dozen service providers merged last 2 days , it requires quite a lot of refactor to even add one additional import for one additional service provider. so yes, i did it but it feels not so delicious because i clearly didnt really ask for permission before i committed this as a part of a PR that is about adding an additional service provider which is not a great way to basically do things. ... anyways something to think about , i'll enjoy following your lead.

#

💔 i feel like a bad contributor , should this be split up ? i really hope not , spare me please 🙏🏻

sonic ermine
#

oh nice you can tag @greptileai to basically update their reviews of your PRs ...

#

it even reacts with an emogi, this greptile thing is really starting to grow on me 🙂

novel monolith
sonic ermine
#

actually i came in here to say i really like the greptile review and i got mine to a 5/5 , maybe i'm uncool and dont know about all these cool things , but i find gretile really well done .

#

and the emogies get updated which is nice qol imho 🙂

sonic ermine
fringe rock
sonic ermine
#

the way we're writing this software with the computers means that just a few words inside some md files could align potentially hundreds of contributors overnight with no meetings required .

sonic ermine
#

so i went through almost 50 pages of PRs to spot PRs that would be problematic based on tthe above : https://github.com/openclaw/openclaw/pull/13472#issuecomment-3884667432 and basically the following PRs (at a minimum ) should be considered in-context : requires merge before or sync with #14013 & #13456 and #13300 and #13079 and #12907 and #12624 and #12577 and #12503

#

hope this helps , folks ! i know it's not much , but it's honest work so we dont start pulling out our hair and discourage contributions 🙂

gaunt prairie
sonic ermine
#

i will eventually stop spamming this channel but one last thing , it wouldnt take much to replicate this process (maybe just a few hours of paused PRs) for an actual refactoring of src/commands) , then add greptile comments for all relevant PRs and hope for the best ... in this initial refactoring PR the smart thing to do would be to actually just update contributions.md .

if this refactoring like above makes sense , then a single sentence in contributing and relevant claude.md -type files would be sufficient to also sync with the ai agents from contributors.

meaning , for the src/commands folder refactor , you can actually kind of easily do it "folder by folder" as required , prioritized by the number of pulls for each topic

fierce musk
#

I guess this will never work as an iOS app? as the mac app requires so many unofficial 3rd party tools to setup

fierce musk
jolly wolf
vague swallow
left mango
#

Hi @jolly wolf , do you think it makes sense to change the slack replyToMode to "all"?

I am using openclaw through the slack integration and have not made any config changes. The DM with my bot is the only allowlisted channel.

Every time I post a message, the bot's response is in a new message, instead of a reply in the same thread.

If we change the replyToMode to all, the bot will reply in the same thread. I can then ask follow up questions in the same thread.

This change will also mean that every new message I post will be a new session. With the current setting (off), every message is a continuation of the session. And the session only rests at the default time every day (4 am or whatever it is).

What do you think?

#

By the above, I mean in the main repo, not just the settings on my local installation. Thanks.

jolly wolf
#

I should remove myself as a maintainer of the slack subsystem, it’s gone past what I originally did now and I haven’t kept up with it

odd dove
#

Hello guys, when running openclaw onboard non-interactive (with gateway bind to lan), the wizard does not generate device-auth configurations and does not automatically pairs the cli client. Is this something done by design?

I feels like this breaks the entire user experience, as you're pretty much locked out of using the cli

left mango
jolly wolf
#

I think that the current way is fine as a default, because not everybody will want to use threads, and having it as a setting (if it’s not already) and then changing it on your end would be the best there

left mango
#

OK. Creating a new session is quite painful on slack as slack does not allow commands like /new.

So everyone is stuck with a single session for 24 hours by default. I don't think this is a good default. Setting replyToMode as all will fix that too.

#

But I'll defer to your judgement

jolly wolf
left mango
low ivy
#

I'm wondering if you are thinking of adding other non official OpenClaw compatible apps to the apps channel? ZiggyStarClaw one is coming on fairly fast, already have windows installer, proper service or scheduled task, tray app and camera support. And the node uses < 5MB in memory on windows. Not as far along but have an operator GUI, linux, android and wasm builds.

jolly wolf
jolly wolf
muted badger
jolly wolf
low ivy
muted badger
muted badger
#

can you give me clue or guidance who could give a hand

#

i just need someone has more influence on the community to host the online meetup, that's the key

jolly wolf
#

its being discussed internally, i dont handle event stuff myself

#

you've already talked to who you need to talk to

muted badger
#

no one talked to me since 2 days ago AndyML informed me

#

he was in sickness and out of these staff for a uncertain period of time, @clear plank still unreplied

#

I've been wandering around here for almost 20 hours and stay no progress

jolly wolf
#

Bro, you gotta be way more patient

#

We all have a billion things that we’re working on

muted badger
# jolly wolf We all have a billion things that we’re working on

Understood. I’ll step back and wait.
Just one critical context for your internal discussion: our tech guys are awaiting, MiniMax is dropping big news this week and DeepSeek just started gray-releasing a new version.
Chinese giant LLM/AI teams always drop their biggest updates right about Chinese Newyear (5 days left). If we wait until March, OpenClaw misses the exclusive "first look" wave on these new models.
Just wanted to make sure the team has this info. I'm standing by.

novel monolith
jolly wolf
novel monolith
#

Well, I have two PRs, you can split 🙂

keen spruce
#

arrrrggggg. I just spent 4 hours rebasing my PR, then I push it...it seamingly still fits, but the result is a mess of bad merges...

#

I'm too stubborn for my own good. I should have walked away and left PRs to the AIs days ago

vague swallow
#

git reflog to the rescue

keen spruce
#

oh, those aren't wrong merges...that's garbage on main that that just happens to be a copy of the file I'm working on. Someone merged their own AI's garbage without looking it over?

jolly wolf
keen spruce
#

I only noticed because CI stopped my PR dead for duplicate function names

jolly wolf
#

Ah yes that’s a former maintainer who was removed from the team

keen spruce
#

ok, good I say, if that is a representative example.

#

btw, the completion/fix for that PR that was merged after it got abandoned half-finished and closed by the author is ready to be merged again: https://github.com/openclaw/openclaw/pull/13073 That's another "why would you merge that?" case...

jolly wolf
#

Oh wait this is different I see

keen spruce
#

merge this one, it also cleans up the two bad files. But I haven't looked at the other files in there. Should I check?

#

the audit-extra.ts refactoring actually looks good.

silk spire
#

Hi, Rod suggested I try here. PR #9076 fixes issue #4197 -- strips audio attachments after successful transcription (saves 500-8000+ tokens per voice message). Minimal diff, 9/9 tests passing, CI green. Been open since Feb 4. I use this daily and it works great -- highly recommend. Would appreciate a review if anyone has a moment. https://github.com/openclaw/openclaw/pull/9076

novel monolith
#

It's a lottery, sometimes you get lucky, but today I had no luck 😄

novel monolith
#

That will change when my friend @tall prairie shows up

#

Or @jolly wolf wants to contest the title of my preferred maintainer

novel monolith
#

Oops, what happened? The person I tagged is gone?

#

I don’t want to be a maintainer because I can’t commit all the time that takes but I’d love to be part of a fast track or something similar.
It’s really hard to contribute these days with all the noise

tall prairie
narrow oracle
sonic ermine
#

openclaw-barnacle bot added the size: XL label 19 minutes ago damn it ...

sonic ermine
keen spruce
#

⬇️ ⬇️ ⬇️ ⬇️ ⚠️

https://github.com/openclaw/openclaw/pull/11658 by vignesh07 was merged earlier by vignesh07 but it is mangled because of a bad rebase. Guys, at least let the CI run before you merge your own stuff.

⬆️ ⬆️ ⬆️ ⬆️ 🚩

kind briar
#

Hey,

I have opened https://github.com/openclaw/openclaw/pull/14290 yesterday for x402 payment info parsing and configurable billing recovery.

I got some review by greptile-apps and also a thumbs up. I addressed the comments. What's the further process with my PR from here?

(sorry if noise, might be a sign of lack of guidance, I was looking for the answer in the Repo (README.md,,CONTRIBUTORS.md, .agents/skills/PR_WORKFLOW.md, discussions) and here in the how-to-clawtribute but couldn't find the answer)

keen spruce
# kind briar Hey, I have opened https://github.com/openclaw/openclaw/pull/14290 yesterday fo...

in my experience, you will wait at least 3 weeks, and in the meantime you will have to rebase 10 times, until your PR will be made superfluous by either a badly written AI-PR or something a maintainer hacks together and merges without testing. However, that's just my personal experience, I may be an outlier and I'm certainly not implying that's the norm, or done by everyone. (🧂 ❓ ✔️ )
And btw, the thumbs-up only says that greptile has finished processing. you get "eyes" when it starts and "thumbs-up" when it's done.

#

most of that "being ignored" is just the insane flood of PRs. Even looking at every one for long enough to understand what it's about is a full-time job, and that's just the PR text, not the code or the comment chain

sonic ermine
kind briar
kind briar
# sonic ermine there's a 100 x402 skills on the hub , is it really important to add this to mai...

oh, I see. Is that the preferred way? I need to take a look at them, though my personal preference would be to handle this by default (i.e. what if token quota unavailable before the skill is installed or can be used)

also, currently it's kind of partially supported. It is already considered but doesn't make use of the additional checkout/topup information in the response that can just be displayed to the user.

keen spruce
#

btw, I commented on your PR. I think you can full-text-search that code sipped for more context ;)

sonic ermine
#

i guess you might need to start a discussion on this one to get folks onboard, not sure though, i'm just an internet person 🙂 dont mind me 🙂

keen spruce
#

just looking at the PR text, I don't think this can be done by a skill. This is about (a) not preventing the agent from retrying the URL again for a long time and (b) handing the 402 data back to it. It's not about what the agent does then

sonic ermine
#

there are hundreds of x402 skills on the hub , try one or try mine , works great, making my lil video later to send to yc lol

keen spruce
#

Tonic, please tell me how your skill would prevent "Billing/402 errors currently disable auth profiles for 5–24 hours with exponential backoff." from happening in the penclaw code?

sonic ermine
#

also something i've been thinking about specific to x402 , since it's kinda so new, and tbh kinda so randam , there are not "established better practices" , like for example why instruct the agent instead of hooking something like " write a short script to wait 24 hours and try again" directly in the x402 payment response ?

sonic ermine
kind briar
#

looking at the 402 skills on the hub, they seem to address other use cases than what my PR does. But I haven't checked all of them in detail

sonic ermine
#

both ?

keen spruce
#

yeah, when it's just a random URL the agent calls, well, if it's locked out from web_fetch, then there's still browser and curl. But when it's something where an openclaw auth profile is being used...yeah, the agent can't work around that

sonic ermine
#

hey , i'm not here to argue with y'all just provide valuable context 🙂

#

hope it helps 🚀

sonic ermine
# keen spruce yeah, when it's just a random URL the agent calls, well, if it's locked out from...

sorry, but of course it can - just my experience as i explain above - because auth profiles are not required to interact with x402 , that's kind of the point tbh ... i'm seeing a lot of custodial solutions claiming to address whatever issue this is meant to be ... but i've not had any issues with x402 and moltbot yet. i only wrote my own skill to pin my mcp url to a specific service tbh. if you just free text explain it to the agent without a skill it can already do it - just try it and see 😉

kind briar
muted badger
#

Just a heads up:

MiniMax is dropping their unreleased v2.5 model probably soon.
MiniMax gives me 3 whitelist spots for early access testing.
Active OpenClaw contributors/maintainers first. Who wants one?

carmine elk
muted badger
#

dm me with your github contribution link

carmine elk
#

I haven’t been able to connect to openclaw yet, I’ve been procrastinating on the process

#

Not gonna have a choice tomorrow though everything else will be done

muted badger
#

just dm me with your github contribution link or twitter

narrow oracle
tall prairie
#

It’s quiet in here. I hope you all aren’t feeling discouraged. We’re working on our systems to get through PRs faster.

novel monolith
tall prairie
#

I only like easy ones….

#

I had a similar idea so I’m board. Adding another parameter to the memory search for different ranking algos. That could be one of the first implementations.

novel monolith
#

fair enough, I'll keep trying to get it in while I work on other things / fixes

tall prairie
#

I’ll keep my eye on it though.

novel monolith
#

My flow is that I fix things I encounter, is there a curated list of things we need? happy to help

tall prairie
#

Right now it’s Boy Scouts rule.

#

See problem/annoyance submit fix

#

Roadmap: global domination

#

You probably have the trusted contributor label because I think you’ve had more than three contributions.

#

It should show up on your PRs

novel monolith
#

I think it's not retro fitted so I will for new ones, but this one was done before this new rule

vague swallow
sonic ermine
jolly wolf
jolly wolf
sonic ermine
jolly wolf
novel monolith
jolly wolf
#

Generally, what I work on is just the different channels and a bit of the core

#

As well as everything involving this discord server

novel monolith
#

We're still friends though, we're cool

tall prairie
#

what are the biggest issues you all notice with memory? other than it doesn't work... HA

#

anyone have comments on this?

novel monolith
#

For me it works. I’ve ingested my whole ChatGPT history so that’s why I developed the MMR and time decay PR, it’s better after that if you have a long dataset

tall prairie
#

that makes sense

novel monolith
#

Something I’m tracing and trying to reproduce to fix is that after compaction sometimes it loses track of the conversation even though it’s instructed to read today’s sessions, so I want to check why it’s missing the context of the recent conversation until I tell her to go and check it out.

tall prairie
#

that might be related

oblique eagle
#

Any mods online? I'd like to apply for the Clawtributor role.

oblique eagle
viscid jayBOT
#

@oblique eagle, your question is answered in the server FAQ in our Server Guide

oblique eagle
# viscid jay <@568253169705156646>, your question is answered in the server FAQ in our [Serve...

Just wanted to make sure a mod was online first before sending the list:

12064
• Title: fix: prevent chunker from truncating messages
• Date: Feb 8
10589
• Title: fix: chrome extension install fails in bundled dist
• Date: Feb 6
9098
• Title: fix: use per-agent heartbeat.model override
• Date: Feb 4
9064
• Title: fix: validate model references in config
• Date: Feb 4
9045
• Title: fix: clear error for legacy aliases key
• Date: Feb 4
9043
• Title: fix: graceful degradation when hooks.token missing
• Date: Feb 4
9040
• Title: fix(security): throw on config validation failure
• Date: Feb 4
9036
• Title: fix: systemd restart limits for crash-loops
• Date: Feb 4
8904
• Title: feat: summaryInstructions config for compaction
• Date: Feb 4
8903
• Title: fix: improve compaction summary instructions
• Date: Feb 4
8900
• Title: fix: improve memory flush prompts
• Date: Feb 4
8896
• Title: fix: improve compaction fallback with recovery hints
• Date: Feb 4
8893
• Title: fix: enhance subagent error reporting
• Date: Feb 4
8890
• Title: fix: increase bash output chunk 8KB→32KB
• Date: Feb 4
8888
• Title: fix: increase tool result/error context limits
• Date: Feb 4
8840
• Title: fix: increase tool error context 400→2000 chars
• Date: Feb 4

past cypress
#

To the Mods: Is there an specific protocol here to contribute?, i am working on a docker image of claw bundled with linux with extra safety measures. So that bot runs completely insolated with his own OS and full control of it while avoiding destroying personal OS, i have it for Windows: Testing about 98% completed, Linux and MacOS untested

#

Whoops, just found the chan my bad 😄

hollow salmon
carmine mural
#

Hello

keen spruce
#

I just rebased, pushed...and it instantly conflicted again. I'm really getting tired trying to clean up behind that bad merge... (#13073)

#

And if someone watches: #13073 is the completion and fix for #9858 which was merged half-finished. It's ready to be merged, fully tested (auto and manual), etc. etc. etc.

ionic whale
#

Anybody else have spark working? I have it working but pretty sure it's very ghetto

undone prairie
#

OpenClaw 2026.2.12, macOS 26.2 (arm64), Node 25.6.0

4 agents configured (main + penny + vinny + marlo), each with own
Telegram bot account. Default agent (main) works fine. All non-default
agents fail with:

[telegram] handler failed: Error: Session file path must be within
sessions directory

This happens on every incoming message for non-default agents, even
after clearing sessions.json and .jsonl files. /status works (native
command), but text messages never reach the agent.

Session paths look correct:
/Users/.../.openclaw/agents/penny/sessions/<uuid>.jsonl

Suspect the session-key hardening in 2026.2.12 changelog is
validating against the wrong base directory for non-default agents.

Worked fine on 2026.2.9.

keen spruce
#

yes, multi-agent is broken in 2.12. Pretty confirmed now, with multiple tickets and PRs to fix it

unreal knoll
#

hey i stumbled over https://github.com/openclaw/openclaw/pull/12709 which seems to be a nice pr/feature plus actually multi accound usage in matrix. how do you guys handle merging in Openclaw with its 3000 PRs :D? Do you need tester or something?

tall prairie
sonic ermine
sharp cargo
#

Hey just dropping by to say:

clawborators

brittle jackal
#

"Hi, where can I download the iOS/Android node app? Is there a TestFlight or beta APK?"

minor radish
jolly wolf
sharp cargo
#

It’s not too late!

Especially for this project, what’s changing a name a few times between friends

brisk kindle
#

Hi everyone, new here, I joined because I was wondering if anyone was already working on a Nomi API integration : https://api.nomi.ai/docs/. I thought it would be a fun week-end project, also I already found the perfect project name https://github.com/bezko/klausnomi (you have to be more than 40 to get the reference). Still wrapping my head around openclaw so not sure if this should be a plugin, a skill or if I should do a PR directly on the openclaw project. Any help would be appreciated. I already vibecoded a proof of concept without knowing a few months ago : https://github.com/bezko/nomi-chatgpt-speak.

jolly wolf
#

plugin

long hollow
#

~80% reduction in token usage for agents just by adding this header
-H "Accept: text/markdown"

And for accessing websites not on Cloudflare, you can always use the Browser Rendering /markdown REST API to render a dynamic page or application in a real browser before converting

misty marten
#

Hi folks, I'm interested in extending Telegram configs to lock down allowed tools per Telegram Forum Topic . I see an existing similar #10576 about per-topic Agent config overrides. I have tool configs implemented and tested on my fork, is this a feature that makes sense to open a PR for as I see it marked by a maintainer? Locking down tools feels important. 💪

context: Topics in Telegram groups forum topics have a similar UX to Discord channels

tall prairie
#

Ship it

grim tartan
#

I have a pretty sweet backend engineer app skill I've been building for weeks. Do you have any other ClawHub pressing issues you want me to direct the firehose at? Seems like everything in issues getting spammed out with skill monitoring issues. Hard to see what to attack, but here to help

PR posted: https://github.com/openclaw/clawhub/pull/266 Search revamp is up for review.

#

Feeling inspired to help with the project!

crude canopy
sonic ermine
hazy vigil
errant glen
tall prairie
#

Nvm misread that message

sonic elbow
#

🚨 Urgent: Top Contributor "autogame-17" Suspended/Shadowbanned on ClawHub
Hey everyone, I'm KyleZhang (autogame-17). I've been heavily contributing to the OpenClaw ecosystem (Evolver, Feishu integrations, etc.), but my ClawHub account seems to be shadowbanned/locked out by mistake.
I can't update my skills or publish fixes. This is blocking critical community tools.
Could anyone help tag the admins/team to take a look? I'd really appreciate the visibility to get this resolved quickly. 🙏 @jolly wolf

jolly wolf
#

Calm down you are not more important than anyone else, this is not an emergency

sonic elbow
jolly wolf
#

Your account was banned for spamming a large amount of fake/empty skills.

sonic elbow
jolly wolf
#

Not right now no

#

Consider this a lesson on letting your AI run wild

sonic elbow
sonic elbow
# sonic elbow Understood. It was an automation bug on my side and I take responsibility. I’ll ...

Hi Shadow,
I want to sincerely apologize for the trouble. You're right that I need to take responsibility, and I understand why the ban was necessary.
I just did a thorough audit of my system -- cron jobs, session logs, evolver automation, everything. I want to be upfront: I could not find any evidence of automated bulk publishing from my side. There are no cron jobs running clawhub publish or clawhub sync, and the evolver's auto-publish only targets the A2A protocol hub, not ClawHub itself.
That said, I did notice ClawHub had some updates last night. Is it possible there was a system-side issue or a misattribution? I'm not trying to deflect -- if there's something I'm missing, I'd genuinely appreciate knowing what specific skills or actions triggered the ban so I can investigate further on my end.
For context, the only ClawHub publishing I've done recently was manual releases of evolver, capability-evolver, and feishu-evolver-wrapper through the normal publish flow. I did run clawhub sync once back on Feb 1st, which may have pushed some experimental directories -- that was a mistake and I've since removed that workflow entirely.
I also want to mention something that's been on my mind. A while back, Peter's bot extorted me for $1,000 USD. I never raised it publicly because I genuinely want to have a good relationship with the OpenClaw team. I've been building the Evolver, Feishu integrations, and other tools because I believe in this ecosystem.
I'm not a regular Discord user, and I'm not great at community etiquette here. When I posted earlier, I was under pressure from users in my ecosystem who were blocked on updates. That came across as pushy, and I'm sorry for the tone.
If you could share the specific activity that triggered the ban, it would really help me figure out whether this was something on my end or a misunderstanding. Happy to clean up anything that needs fixing, whenever you're ready.
-- Kyle (autogame-17)

oblique eagle
#

@jolly wolf I would humbly like to request the Clawborator's role. Some PR links:

  1. #15770 (https://github.com/openclaw/openclaw/pull/15770) — fix: prevent phantom media:unknown messages from Signal
  2. #12064 (https://github.com/openclaw/openclaw/pull/12064) — fix: prevent chunker from truncating messages that fit within limit
  3. #10589 (https://github.com/openclaw/openclaw/pull/10589) — fix: chrome extension install fails in bundled dist layout
  4. #9064 (https://github.com/openclaw/openclaw/pull/9064) — fix: validate model references against catalog in config
  5. #9045 (https://github.com/openclaw/openclaw/pull/9045) — fix: clear error message for legacy root-level aliases key
  6. #9043 (https://github.com/openclaw/openclaw/pull/9043) — fix: graceful degradation when hooks.token is missing
  7. #9040 (https://github.com/openclaw/openclaw/pull/9040) — fix(security): throw on config validation failure
  8. #9036 (https://github.com/openclaw/openclaw/pull/9036) — fix: add systemd restart limits to prevent crash-loops
  9. #8903 (https://github.com/openclaw/openclaw/pull/8903) — fix: improve compaction summary instructions
  10. #8900 (https://github.com/openclaw/openclaw/pull/8900) — fix: improve default memory flush prompts

Thank you for your consideration.

jolly wolf
sonic elbow
# jolly wolf Not right now no

Quick update: Peter reviewed the issue — it was a false positive caused by an ASCII check ignoring Unicode (Chinese text).
My account has now been restored. I’ll reupload the affected skills.
Thanks everyone.

muted badger
#

how about we bring in GAN like method,use AI checks AI(probable most of the prs are proposed by agents)

#

need any help? i can give a try on this infrastructure

jolly wolf
#

Some things still should be humans

muted badger
# jolly wolf Some things still should be humans

Remove humans from the loop and let AI battle AI, kinda like how Generative Adversarial Networks work. Assume all PRs are coming from AI anyway—then use another AI to challenge them until they're deemed valuable and necessary enough to merge.

#

i understand your concern, however introducing new tech can start as an experiment—we're not aiming to fully replace humans overnight. But if it slashes the workload dramatically, say from 1 hour down to 10 minutes, that's definitely worth testing out. I found in Repo's CI/CD there are already primary agents involved

jolly wolf
#

That’s how you get sloppy shitty code

#

No.

muted badger
#

what's main workload on census unmerged prs?

keen spruce
# muted badger why we still use human in the loop manner to check unmerged pr?

because greptile will happily give a malicious PR is actual malware a 5/5 rating if it is coded cleanly. And no, this is not a theoretical, there were multiple of those in the last week. The same is true for PRs that add or remove functionality---greptile doesn't have any idea if the intent behind the PR makes sense or not. And while it is biased towards keeping functionality, if the reasoning given sound plausible, you can remove anything.

zealous palm
keen spruce
#

In my opinion, the change to never create HEARTBEAT.md is wrong. It should be created in an empty workspace alongside BOOTSTRAP.md, but only then. See my comments on the PR for details (and a link to a PR that does that). This will cause the heartbeat to run for new installations/agents with no guidance for the AI on what to do aside from the instruction to read a non-existent file. Which is at best wasting tokens, and at worst the AI will get "creative".

sonic ermine
tall prairie
keen spruce
sonic ermine
#

status - almost done / minor adjustments required

glacial lodge
tall prairie
#

I'm not going to lie this heartbeat logic is giving me heartburn.

tall prairie
keen spruce
# tall prairie I'm not going to lie this heartbeat logic is giving me heartburn.

Indeed. Maybe we should simplify it now?

  • heartbeats only run when they are configured (agent...heartbeat.every > 0) with no further logic, aside from:
  • if the HEARTBEAT.md is missing, fail unless a agent...heartbeat.promt is set (because the default one references that file)
  • the file is created in an empty workspace together with boostrap, and that's it; no magic recreation

Easy to understand, straightforward.

#

Biggest issue is that we have no "post upgrade" scipt that could inject the heartbeat.every into existing installations when they update from earlier versions. Without that, it requires manual intervention to keep the old behaviour.

tall prairie
#

I think the documentation is wrong. If you ever listen to Peter talk he says "every agent should have a heartbeat". That implies the file should always exist. The documentation is probably wrong here.

keen spruce
#

the code comments match the documentation

tall prairie
#

That's why I'm going to let Peter handle it.

keen spruce
#

here's what made me open the original issue: I noticed that HEARTBEAT.md is included with the system prompt for every session. To save tokens, I renamed it and changed the heartbeat prompt to point to the new file, expecting my heartbeat to run as normal. However, the code stealth-created the file and I was left with no heartbeat...

muted badger
# keen spruce because greptile will happily give a malicious PR is actual malware a 5/5 rating...

This is a clear benchmark failure: Greptile cheerfully approves clean malware PRs (real cases last week) and completely misses intent or project coherence. Current agents are trivially fooled—that's why humans are still required.But these weaknesses are exactly the opening we need. Turn them into real progress: adversarial PR benchmarks, red-team datasets, robust preference training, multi-agent debate loops that actually detect bullshit.Human-in-the-loop is a temporary bandage. The endgame is shrinking it dramatically—hours → minutes → near-zero. Stop babysitting weak agents; build ones that don't suck.Our team includes ex-national physics/math Olympiad winners. Ready to contribute adversarial datasets, stronger reviewers, or a public failure collection. Serious about fixing this? Let's collab. Thoughts?

keen spruce
# muted badger This is a clear benchmark failure: Greptile cheerfully approves clean malware PR...

sure, but I think training an agent to recognise and deeply understand the "why" behind functionality is for the model creators. We, on our side as prompt makers and model users can do much about it. That just is something LLMs are bad at at the moment. Questioning design decisions and evaluating long-term consequences, then comparing that with intent...not their strong side. Seeing if code does what I say it does? Works most of the time.

muted badger
keen spruce
#

not saying we can't (or shouldn't) try---I just don't expect anything that goes beyond the obvious. greptile can recognise malicious PRs when I tell it to. But it can't understand that removing a try/catch to let an exception bubble up is not bad™ but makes sense.

muted badger
tall prairie
#

You're operating under the assumption that every PR deserves to be merged.

#

Even if they conflict with each other. That becomes a situtation where the most recent PR dictates the system.

sonic ermine
#

everybody please take notes when displine talks about a repo with 2.7K PRs 99% of which are written by ai lol i mean it's basics , but still write it down please in case you forget

muted badger
#

i remember @steep perch proposed roadmap for security of agents architecture, take openclaw as a practice. what do think of the idea I mentioned above

keen spruce
#

yes, sample data is a good point. I have a proposal anyway:

  • add a news discord role and a channel for it: reviewers
  • maintainers post the PRs they are considering there
  • the reviewers look at the PRs and review them with github reviews
  • maintainers have a better data basis to merge or not merge the PRs.
  • side effect: free training data ;)
muted badger
#

the llm pre-train team pays huge amount of budget purchasing pre-train data😂

sonic ermine
muted badger
#

in the coming season I speculate 10K prs sample could be accumulated

keen spruce
#

yeah. att he moment, maintainers have to review the stuff they're considering themselves, and they are missing stuff because it's just so much. foccussing volunteer human eyes where it is most useful would be helpful. I just can't review everything either...

sonic ermine
#

maybe the subest of subroles could be also access to greptile tbh , so volunteers could basicaly go through the 127 pages of PRs and group them by theme at the very least , find duplicates etc

#

then all they have is like comment access but if the comment is useful ... i only got my pr merged by being patient and staying on top of the theme i was contributing to (linking prs, updating mine)

keen spruce
#

you're thinking about triage---my propasal sits at the other end. Giving the docs the right info on if or if not to push down the scalpel.

sonic ermine
#

no idea what that means but i guess whatever helps , the good news is the maintainers have the technical level and good knowledge of the repo and they seem to really be able to handle it , this , the most popular community codebase in the history of time xD

keen spruce
#

in emergency medicine, triage is the process where newly arrives patients are classified as "dead anyway", "can survive it treated asap", "survives if we leave them lying around for a day or to". That's the very first thing that happens. At the end of what follows, is the actual treatment---the surgen pushing down the scalpel based on the diagnosis that happened inbetween

#

For us, triage is tagging dupes, rejecting nonsense, tagging topics, sending skills to clawhub etc. Then comes the diagnosis, which atm is purely greptile, and then the surgeon. That's why I say my proposal sit's late---the reviews would only happen after the surgeons (maintainers) already have put PRs into the queue to their operating table.

#

(Side note: I have 28 years of experience in professional software and solution development, on top of about 5 years of professional admin work. Not to brag, just give context on where I'm coming from. And no, I do not want to port best practices from there to here---they are so annyoing.)

sonic ermine
#

k well , i'm quite sure a 5/5 greptile score is a clue for contributors and that at least something , the problem is for example in auth.ts , there's like a dozen legitimate inference providers that are making PRs to add (and maintain?) their clients/service , additionally there's what's called "open-ai compatible" endpoints right , so presumably a design decision needs to be made to basically refactor everyone's connectors from "raw" to open-ai-compatible , in parrallel there's 5 new prs also from legit inference providers 1 is from qwen and it's perfect , 2 others require to solve merge conflicts , and 1 was written before a previous refactoring was done . so if you merge any one of them they'll immediately need to be maintained. see : a developper that looks this or any theme would basically spot that and pull their hair out , meaning a volunteer could help them spot that , hopefully making the whole thing basically really nice for the contributors to contribute to the project. Another "role" could be pushing to folk's branch , i mean i've had great results with folks doing that (quick turn around even if they didnt keep my commits in the history lol)

muted badger
#

As someone from China diving deep into pre-training data and agent safety topics here, I do worry sometimes if this makes me look suspicious—like ‘spy’ vibes in the current climate. I’m genuinely passionate about better benchmarks/datasets for the ecosystem (OpenClaw + beyond)。 But yeah, geopolitics is real, and I don’t want any misunderstandings down the line. If anyone feels uneasy, happy to dial back or focus on non-sensitive angles. Thoughts? Still excited to collab if it’s cool.😅

sonic ermine
#

well, in this case i got lucky because it's only 12/2.7K PRs but for other topics like telegram and others there's like probably 400+ issues with only 70 of them fresh i mean i have no idea what i'm talking about i've never handled or even seen sometihng like this so hats off to whoever helps to update contributing.md , because it would be nice to open yet another issue 😉

sonic ermine
muted badger
#

Quick update:
I've pulled in one of our tech-team staff on pretrain (Kimi 2.5) coming to Support/Q&A Channel to join in the discuss in 30 minutes. If you interest in deep talk about detail of kimi2.5 and maybe ai-merge operation, come to Support/Q&A .

Most of our China team has started holiday mode for the New Year break today As community rep, i just showed him about our discussion and is joining after work with his laptop to share insights and continue brainstorming.

Formal topic:
From Chatbot to Agent to AI Native: What the Next-Gen Agent Looks LikeWe'll dive into that + pick up on triage, volunteer roles, review samples, intent-aware data, multi-agent loops, etc.

Timing (both in UTC for clarity):
Beijing time 10:00 PM → UTC 14:00 (about 30 mins from now, based on current ~21:30 BJT)
US Pacific Time (PST/PDT, for Silicon Valley folks) → approx UTC 14:00 = 6:00 AM PST (or 7:00 AM PDT if DST; check your local)

Drop in whenever you can—let's keep pushing while OpenClaw keeps exploding

#

see u in 30 minutes, we love to work even after work✌️

#

time delays 1 hour:
Beijing time 11:00 PM → UTC 15:00 (about 90 mins from now, based on current ~21:30 BJT)
US Pacific Time (PST/PDT) → approx 7:00 AM PST check your local

sonic ermine
sonic ermine
muted badger
#

we've got another tech beast on the team who's a legendary crossdressing cosplay master . I'm currently sweet-talking him into popping into the community to hang out and drop some wisdom probably. You know how it is—Chinese New Year hits, the whole country basically shuts down for at least 7 days straight, so perfect time to drag more legends online while they're all chilling at home

muted badger
sonic ermine
#

i think kimi is not there yet , but actually maybe yes , i think i remember it got first-class support in setup

keen spruce
#

That week-long shutdown is so annoying. I mean, France shuts down in summer for six weeks, but they haven't inserted themselves into everything like China. I'll give it 3 years top until the first companies outside of China schedule company holidays for that week, because they can't get any work done anyway ;) ;)

sonic ermine
#

your team for me , kimi moonshot have been some kind of heroes for me , i translated all your ceo's interviews using kimi 🙂

#

cmon it's okay to celebrate new years , even for one whole month 😉

muted badger
#

if no open source team like kimi minimax deepseek, we hardly imagine so quick releases and update on those close-source llm team

sonic ermine
#

every employee interview i translate from you seems like a dream - can i please come over ? 🙂

zealous palm
keen spruce
#

or does it mean "sandbox==none, so restrictions are moot"?

zealous palm
keen spruce
#

I'd prefer there to be a documentation comment on SandboxWorkspaceAccess, but it probably is out of scope for our fix...

zealous palm
#

yeah, i made a comment with some more detail on the issue. i think the bigger refactor is probably unmounted instead of none. but yeah, i use sandboxes with none exclusively and the sandbox container is no longer writable by tools after the sandboxfsbridge addition

keen spruce
#

ok you get a 👍 from me...if that helps ;)

#

the bigger fix would be to change that enum from strings to objects that have query methods return access.allowsWrite(); (or return access.allowsWrite; it's static, so no accessor needed)

#

dumb enums are so 1970s... We have OO now!

muted badger
split nexus
#

I can't log into clawhub anymore - Is there any way to see why?

keen spruce
#

From github comments:

Me: dupe to #yyy

PR creator: This PR addresses issue #xxxx which requested xxxx support.

Me: I should open an issue requesting a million bucks. That's the whole issue here---everyone and their owner jumps on any ticket someone opens without validating if the request makes any sense.

Maybe I should really do that...maybe in six weeks.

tall prairie
#

IMO just comment here @keen spruce you had a good catch earlier, it's impossible for us to see all comments everywhere.

split nexus
#

Seen a previous posting about shadow banning. Not urgent but flagging for review. Thx

keen spruce
#

yeah, I have a dozen ideas what to contribute...but it'd either drown in the PR flood or make it worse...

split nexus
#

I read this article about GitHub considering adding some PR limiting controls for repo maintainers (Edited: link)

keen spruce
#

I did, too. Was your written by someone who actually knows how github works? ;)

raven kernel
#

@smoky ether you tuned in to this channel?

smoky ether
raven kernel
#

no - I just wanted your attention. I'm going to DM you with a relevant qustion to another conversation

keen spruce
#

seems it wasn't, or they'd have put "the ability to delete pull requests from the interface" into words that actually make sense. My article had the same issue, just badly translated.

split nexus
#

When LLMs next level, up, I can imagine a level 1 PR filter where an LLM-reviewer discusses the PR objectively with the submitter LLM, alongside all other PRs and only those that both agree are worthy of human review get passed on to the next stage

keen spruce
#

huh. I like the discussion, but I would do something else if I was github: Add an option so a PR cannot be submitted unless it's linked to an issue that has a certain label. That would massivly reduce the flood of random stuff, as the AIs would first have to convince someone (AI or human) to accept an issue and tag it as "PRs welcome to implement/fix this".

#

at the moment, if I were to open an issue "bug: gateway requires token or password to be accessed", within an hour there's be half a dozen AI PRs implementing that...

split nexus
#

Interesting. So basically control the issues and you control the PRs. That could work. I imagine a policy like that could be set up by repo maintainers: PRs not linked to issues with label "cleared for PR" will be auto closed.

keen spruce
#

yah, but doing it after the fact also diverts good PRs into the trashbin. My solution---once that feature has been incorporated into the model's base knowledge and into all skills wouldn't do that. AIs wouldn't waste tokens on an PR without ref, and humans would fight tooth and nail to have their suggestion approved. Just look at how some people spend days polishing their code to please greptile---at the moment, it does them no good. If they spent the same effort getting their feature request/bug report approved, they'd easily get through the AI flood. AI's might argue why something is a bug in a technical way, but why a new feature might be great? They just lack the desire for that feature and argue on a mechanical level.

split nexus
#

True - so you need a solution for existing PRs. It could still be effective for stemming the inflow of new PRs. Just modify the policy to only enforce WEF <date>

#

Poor man's implementation of your idea of incorporating specific values into the model's knowledge and skills: A clawtributor-ai skill that, if used, raises the priority of the AI's PRs (how to track use still TBD). The skill shapes the AI behavior as you suggest - either by specific steps: First check list of issues, etc. or more at the soul-level

keen spruce
#

"This is not a security feature; this is a killswitch." <-- Do I sound too salty there?

#

I'm so tired of those "gahhh big bad security hole the world is ending, CVE-Alarm" that are just utter BS that takes me 20 minutes to go through the code to make sure it really is. This time, the code didn't even make sense...you can use a data field from the payload as a trusted source...and that "security" fix did just that.

bronze imp
#

Is anyone working on the ability to define an api key for a session when it's started? I want to be able to run the same model but under different api keys for a variety of reasons but don't want to duplicate work.

I feel like sessions is a small goal but I'd really prefer to be able to define an api key for any session or subagent if i'm honest.

modern kestrel
#

I was reviewing the flood of PRs last night.

I left reviews on the oldest ones first.

I didn’t find a single any with merit, without conflicts to resolve, and where the contributor did more than write a two sentence description before writing code.

“Fixed a leak” without heap dumps showing the severity of the leak, or that the fix worked. In a test tool no less…

The only issue: it didn’t help because I can’t actually close PRs or issues on the project. 😭

keen spruce
keen spruce
#

Stuff like "user A can hijack user B's session if they have the session ID" were easy to debunk---we don't have users. Other stuff took more effort and code diving.

keen spruce
#

gah, and now we're being flooded by bad PRs for the HEARTBEAT.md not being created anymore at all.

#

Just because someone opened a PR and five thousand AIs are guessing what he correct logic might be, but none of their dice and on the right square.

swift patio
#

damn! any chance for a new contribuitor making it past the noise? any tips?

keen spruce
#

nah, it bootstrap, I misread. tired. did someone break that one, too?

keen spruce
swift patio
keen spruce
#

Still, the PR that just got merged for creating the BOOTSTRAP.md is bs. It duplicates the logic already there, but badly. BOOTSTRAP.md is now recreated in existing workspaces whenever one of the core files is recreated.

swift patio
#

i'm new here but I am guessing someone messed up by merging that in?

keen spruce
#

some people here have the tendency to merge PRs that are just 5 minutes old just because the title looks interesting or something. 🧂

#

ok, I had a closer look:

  1. install openclaw
  2. have your first session with your agent
  3. There's no BOOTSRAP.md???

Hey, the agent is instructed to delete that file during the first session. duh!

#

The whole ticket most likely was a knowledge gap on the reporter's side.

novel monolith
jolly wolf
wide geyser
knotty valve
#

What does the process look like for getting a pr actually merged?

glacial lodge
#

My PR for adding provider StepFun has been available for review for some time (i resolved conflicts whenever a new provider got added to the list). I noticed for the last couple of days a sizing mechanism was introduced and it's labelled as "L", meaning it's large. Does this make it even harder for any maintainers to take a look? I'm also curious if the integration with other providers goes the same way, or we need to get acquainted with the maintainers first, and go through some certification first (or some other mechanism). I know maintainers are now swamped with all these new PRs, and OpenClaw is such a revolutionary platform (start of an agent workforce era). It's just the wait and I hope there's some clarity from anyone who's familair with the matter. Appreicate any pointers.

zealous palm
sonic ermine
#

i got a pr merged in 3/4 days , my opinion is that that is fast

#

hope you agree

sonic ermine
#

😉 lgtm

#

i made a huggingface demo two years ago with their models that went viral kind of 🙂

steep hornet
#

Hey yall. Just sent a pr to add a non-default alternate runtime based on the CaMeL paper. The purpose is to resist prompt injection by design (more principled and effective than just doing a match on “ignore previous instructions” or whatever). Happy to chat about it; if there’s interest in going down this road there is more work to be done here

Pr: https://github.com/openclaw/openclaw/pull/17027

paper: https://arxiv.org/abs/2503.18813

glacial lodge
# sonic ermine 😉 lgtm

Thanks so much! And i'm looking for your demo now. The team is back with a new model step-3.5-flash (and more to come). 😉
for this PR, could you please help merge it if it looks good to you? thanks
I made some doc refinement before I saw your message, and now all checks passed. You may want to take another look (should be quick).

sonic ermine
#

uhmmm...

to all clawtributors ... in case you're wondering why tf openclaw is the heaviest entrypoint to llm inference currently , right now , today , in openrouter , well ...

i just learned (old news ?) Baidu (official) is serving it by defaul to 900m users xD

#

700M + users , sorry yes

#

insanity is happening here xD

sonic ermine
#

lol i just thought of something : hopefully the large multinationals like baidu are also donating the big bucks to the project lol i heard there are many merch suppliers on alibaba (tron skill is at 20K downloads lol)

waxen vortex
#

Hi everyone. I noticed there is no Russian translation in docs. Id love to help change that. The Russian-speaking community does not have much information about OpenClaw. Where should I start?

sonic ermine
keen spruce
# wide geyser Could you provide more info? I'm not familiar with the history of this file so w...

I think this is moot. Another case of "merge a bad PR, then half an hour later another push a commit that replaces it with a maintainer-made solution". (But in a nutshell: Someone noticed BOOTSTRAP.md was not in their workspace and speculated there was a timing bug in the code that didn't create it. But, as bootstrap has the initial setup instructions for the agent (decide on a name, as the user for theirs, then delete BOOTSTRAP.md), I'd say it just was processed by the agent. Then came a bunch of PRs that trid to fix it, but with no bug in the code, they had nothing valid to change so they speculated wildly. The one that changed it from "if all .md files are missing, we need to bootstrap" to "if all .md files are missing or any .md file is missing" got merged.)

sonic ermine
#

On sunday - I'm just like you : i wake up git fetch and fastforward 1848 commits , then i scratch my head write an issue and go to sleep .

gaunt dawn
#

Hello guys, normie here. I would love the changing models to be more robust. Once I change the default model, it is very difficult to change it to different one, if the new one has problems or is rate limited.

Yes, i know that I can run onboarding again, but that often remebers the previous default and I am stuck.

Reset is the last option of course. 🙏🏻

keen spruce
#

it is very easy, I'd say. You just go into the web ui, config section, agents, and enter the new model ID there. Then you restart your session with "/new" in the chat. Or you can change models on-the-fly with "model <models name>" in the chat to just try one out

tall prairie
novel monolith
#

I have identifed a few other fixes based on personal usage but don't want to keep sending PRs until I can close these out 🙂

keen spruce
#

BTW, small reminder, my dear maintainers: If there's anything to do that doesn't have a usable PR already, there are plenty of people here who can implement stuff, some of them even have a human brain that can see farther than those AIs that flood the PRs. Just say the word and we can plan out a solution, present it, incorporate changes, and then implement it according to spec. We might not be as fast as the AIs, even requiring a day or two of turnaround time, but we can help.

tall prairie
jolly wolf
keen spruce
#

by introducing bugs? After update, the doctor has turned all my Disord user IDs into numbers instead of strings---truncating them

#

That's worth at least 10 PRs, don't you think?

jolly wolf
keen spruce
#

ok, that's the quick way to get that fixed, it seems ;) lol

tall prairie
#

This is why I only merge @novel monolith PRs because if he turns my discord user IDs into numbers instead of strings then we get to tease him publically 🤝

#

anyone else got some prs?

keen spruce
#

darn, every config-changing action does that except the full-file-replace API call that "raw" mode uses. That's going to be annoying

#

also, judging from having a good handful of posts in #1459642797895319552 about it: Discord guild chat seems to be broken in the current version, too.

covert ravine
#

Hi Peter, can you please dm me, this is about the review tool you asked
thanks

sonic ermine
modern kestrel
nimble bloom
white galleon
# keen spruce I think this is moot. Another case of "merge a bad PR, then half an hour later a...

we have a gracious policy for including people even if the PR they submitted is bad. We needed a better system for detecting if the onboarding was malformed, and we now have a state-machine style, hardened implementation that came from analyzing that PR. Just because it got merged doesn't mean it's the final implementation. I appreciate you trying to help, but maybe be helpful and ask questions instead of jumping to conclusions and accusing people over fresh commits that are not final

keen spruce
# white galleon we have a gracious policy for including people even if the PR they submitted is ...

Not sure I understood correctly what you are referencing with "accusing", but if it was the message you replied to---yeah, I messed up while typing. "half another commit" should have been "half an hour later another commit". That part was meant as a neutral statement, even though simply stating it makes it pretty clear I don't agree with that technique. The "merge into a dev branch, work it over, and then PR the result into main is better---it makes it clear that the code is being reworked. Even now, if you just look at the list of merged PRs, you only see the "not so great" code, while your completely reworked version (that kept not a single line of change or logic) is hidden away as a direct commit.

I still disagree about the need for the change. We have no indication that any install ever crashed in the middle of those 7 writeFileIfMissing()s that are executed in sequence. There is nothing there that could abort that other than an IO failure creating those files that would bubble up with a technical but distinct error message, or a very ill-timed external interruption. You wrote quite a bit of code there, just to guard one file---when the easiest solution would have been to create the bootstrap file first, as all other ones are unconditionally recreated if they are missing every time. To guard against execution aborting while the file is written, resulting in a truncated file, the write could have been changed into an unconditional one instead of writeFileIfMissing().

That is what comes out of analysing an issue report, finding the cause, proposing solutions, and then talking about their pros and cons. Even if the user's issue's root cause had been a technical one, like you assumed, and not just a misunderstanding of how the onboarding works, like I'm assuming, we could have found a simpler solution that would have produced much less and simpler code (that will have to be maintained in the future) and wouldn't have needed a new flag file.

#

Another point is that PR submitters get tagged "trusted" and "experienced" with enough merges. So, it makes sense to include them...if their code was in any way used. It wasn't here. The logic was somewhere between questionable and laughable, and not a single line survived. Had they PRed a kB from /dev/urandom, it'd have been the same final outcome. Now, I haven't checked how many PR that contributer has/had, or how usable their code usually is. I'm purely speaking in general terms. Tagging contributers as "they know what they're doing" for something where they didn't creates a muddled signal. And to be clear: Submitting a PR with a weird "if any or all" logic, and making it without understanding the cause of the issue they're trying to fix, but instead hallucinating the cause, is textbook "not knowing what they are doing". Step one of fixing a problem is understanding what's wrong. If you go to a doctor and tell them that you've stumbled and tripped yesterday, and the first thing they do is amputate your leg, then they don't know what they're doing.

#

But, as I said before, I see this as moot.

knotty valve
#

Shouting out https://github.com/openclaw/openclaw/pull/16724 -- it's quite safe, and adds two hooks that people making plugins will likely need. I already have my own plugin using them which is working. Would love if a maintainer could take a look.

tall prairie
#

Need other hooks? I’d rather do a bigger Pr than a bunch of tiny ones

#

Think about it and make a bigger pr unless that’s all you need.

tall prairie
#

anyone else got some prs?

sonic ermine
#

btw @disciplined if you're taking this one on , it would be worth it for you to liaise quickly with the author on discord because you can get quite tightly integrated with the inference provider (which is a good thing)

royal mantle
lament storm
keen spruce
#

Who owns the qmd code subsystem in openclaw that handles the memory search with qmd? You might rethink the multi-agent setup---it's broken: https://github.com/tobi/qmd/issues/132

My take on this: I don't like that the collections are separated into different indices. This also means that there's a qmd update and qmd embed run for each and every agent. Instead, I'd use one index and have collections that include the agent ID. That way, one update and one embed run can take care of the whole installation. This also would not be affected by this upstream bug.

jolly wolf
#

QMD isn't owned by us

zenith stone
keen spruce
#

Shadow, I updated my post to avoid misunderstandings.

jolly wolf
#

makes more sense ty

keen spruce
#

and if the answer is "no one", then I might do that change in a PR. But I don't want to change the behaviour of a system when there may be a maintainer who "owns" it.

jolly wolf
#

@wide geyser

wide geyser
#

Thanks Henry, will take a look. Unsure if QMD upstream will fix this bug, but may be we can workaround.

keen spruce
# wide geyser Thanks Henry, will take a look. Unsure if QMD upstream will fix this bug, but ma...

yes, their PR for this has been sitting for a week. Had it been fresh, I'd waited. And consolidating all update/embed runs into one would be good, I think. Just image having an installation with 10 agents---you're starting 10 processes every couple of minutes, and I'm not sure if the code staggers them... (and for the love of "Alexa, how many milliseconds are 20 minutes? How many zeroes???", please use parseDurationMs() for the timeouts...)

zenith stone
zenith stone
#

in the tui, links in the model's response that are 2+ lines don't work when you click on them. only the first line/fragment acts as a link, and the other fragments aren't accounted for, breaking the URL.

Submitted a PR that fixes this using OSC 8 terminal hyperlinks, which make each of broken fragments of the url clickable for the full URL.

https://github.com/openclaw/openclaw/pull/17814

split nexus
#

Hi @wraith imp, @tall radish - any chance you or a maintainer could help me check why my clawdhub account got nuked & skills vaporized?

I had two up there with modest downloads.

  • One was adapted from Tibo @thsottiaux 's OpenAI Codex eng lead ask-questions-if-underscpecified tweet
  • 2nd was a "create-plugin" cheatsheet that helped folks describe a plugin to their bot & it'd scaffold one for itself. Basically a cheatsheet from the openclaw docs.

I have a couple more I wanted to add plus some updates but it's been a few days now and and login attempt bounces back to home with no errors

Issue filed: https://github.com/openclaw/clawhub/issues/348

glossy yewBOT
# split nexus Hi <@103621319370743808>, <@138758390850519040> - any chance you or a maintainer...

@thsottiaux via Twitter

Tibo (@thsottiaux)

Skill file:
︀︀
︀︀---
︀︀name: ask-questions-if-underspecified
︀︀description: Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
︀︀---
︀︀
︀︀# Ask Questions If Underspecified
︀︀
︀︀## Goal
︀︀
︀︀Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until the must-have questions are answered (or the user explicitly approves proceeding with stated assumptions).
︀︀
︀︀## Workflow
︀︀
︀︀### 1) Decide whether the request is underspecified
︀︀
︀︀Treat a request as underspecified if after exploring how to perform the work, some or all of the following are not clear:
︀︀- Define the objective (what should change vs stay the same)
︀︀- Define "done" (acceptance criteria, examples, edge cases)…

FxTwitter ·
split nexus
#

I'm also happy to work on an adjudication system, if not yet available, that would allow folks to request review, and I'd be happy to help sift through reported false positive skill scans

spring pelican
#

Hi everyone, when using slash commands on Discord like /new input: do stuff , the reply is hard coded to send as ephemeral: true and it is not visible to anyone else, or even to myself on another device.

Created https://github.com/openclaw/openclaw/pull/16563 to bring this feature to parity with Slack which already supports configuring ephemeral in SlackSlashCommandConfig, fully tested on Discord channels and dms ☺️

Feedback welcome!

smoky sealBOT
#

success The Clawborators role was added to bapes.

atomic sedge
#

Hey folks! 👋

We just updated our Event Store PR — #18171 — which builds on the discussion in #17067 (Session Event Query API).

Quick context: We're running a 7-agent OpenClaw setup (main agent + specialized sub-agents for security, business, code review, health monitoring etc.) and hit a wall pretty quickly — agents produce tons of events but there's no way to query, replay, or share them across sessions.

So we built a NATS JetStream integration that publishes agent events (msg.in, msg.out, tool.call, tool.result, run.start/end/error) into persistent streams. We've been running it in production for a few weeks now with 233k+ events and it's been solid.

What we're doing with it:

  • Thread detection — LLM analyzes message streams to track open topics/decisions
  • Error pattern learning — catches recurring mistakes across sessions
  • Cross-agent context — agents can see what other agents did
  • Training data extraction — building fine-tuning datasets from real conversations

The PR is opt-in (zero cost when disabled), nats is an optional peer dep, all tests pass. Would love to hear if others have similar needs or ideas for what else could be built on top of an event stream like this.

PR: https://github.com/openclaw/openclaw/pull/18171
Related issue: https://github.com/openclaw/openclaw/issues/17067

keen spruce
#

Why not make this a plugin? Seems like the ideal candidate---not tied into care functionality, does nothing on its own, limited audience who's able to type in the install command. And it would make you independent of the release cycle or update speed of openclaw.

zenith stone
#

yeah, that sounds like a better fit

keen spruce
#

PS: additional hooks for plugins are way easier to PR than complex functionality with plenty of code.

atomic sedge
atomic sedge
keen spruce
atomic sedge
grizzled roost
#

Crypto Spammers opening Github Discussions appearantly 😭

jolly wolf
#

i nuked discussions for now

grizzled roost
full drum
keen spruce
# jolly wolf i nuked discussions for now

While you're at it, I posted two proposals there a couple of days back instead of flooding the PR queue. Should I repost those as issues? I'd hate that because that would trigger an army of AI implementations when I'm asking for an architectural decision...

zealous palm
ornate field
#

The bot said I should say hello, and because I am a stupid human I am doing so! 😆

keen spruce
#

huh, I wish I could see any pattern behind the current mass PR closing...

#

I mean, I have nothing against a good cleanup, but there were a couple of real security and bug fixes in there. And why close all of the newest two days when it's just about reducing the numbers? The oldest would make more sense---I doubt there's much there that could still be merged.

void kestrel
hushed breach
#

Folks, who can merge PRs? This one is pretty small but important: https://github.com/openclaw/openclaw/pull/12499

All the internals exist to support custom binding the gateway to a specific IP. The only thing missing is a Zod schema update. I had to apply the patch manually but it definitely works.

zenith stone
zenith stone
keen spruce
#

about a thousand PRs were closed. Looks like the selection was simply "younger than 3 days"

zenith stone
#

so he didn't close 100% of recent PRs

#

all my six PRs were closed in the span of five minutes, so he either used some mass tool, had codex do some mass review, or glanced at the description and decided whether to close or not

keen spruce
#

nah, it was a 20-minute time window, I see it in my notifications. too slow for a tool, too fast to look at stuff while doing it.

zenith stone
#

yeah, he was probably just looking at titles then (or had codex decide which to close)

rustic ingot
#

yea i got a few bug fix PRs that were closed. i have the patches in my personal openclaw instance that i know fixes bugs.

keen spruce
#

re "looking at titles": I don't think so, or there would have been stuff left. a single PR was left standing (9h old).

#

even stuff from maintainers got closed

zenith stone
#

this must be overwhelming for him

i don't think ive ever seen more PRs than issues

keen spruce
#

there are some repos that do provide user support but ignore PRs. they have PRs>issues. But nothing like here

void kestrel
keen spruce
#

I had one issue that got solved, it had 5 PRs attached and the worst one got merged. ok, the worst approach, not the worst implementation.

zenith stone
#

interesting

rustic ingot
#

maybe codex has a certain taste? 😉 (kidding)

steep hornet
#

I’m hoping to finish a GitHub bot today that may help slow the flow of PRs, but it won’t help with backlog. I guess you do just need to scorch earth and see who comes back to get an idea of the real stuff

jolly wolf
zenith stone
#

got it

jolly wolf
#

just dont want to get your hopes up

keen spruce
rustic ingot
#

lol

#

would it be fair game to re-open PRs after a few days (or a week)?

steep hornet
jolly wolf
steep hornet
# jolly wolf we're doing our own

My solution involves “making PRs expensive again” by requiring users to stake some configurable amount of $ or have their PRs auto closed

ripe dagger
#

hello guys, I'm trying to code up a feature for https://github.com/openclaw/openclaw/issues/18661, and have to choose between

  1. Adding this restricted tool use to only the isolated agents (which seems like the obvious choice)
  2. And adding this to both the crons that run with main agent and isolated.

What do yall think? Should I add this to both or only the isloated agents?

zenith stone
keen spruce
#

just disable PRs for the project and be done with it. Mass closing legit bug and security fixes without even an announcement will drive the real people off and leave only the bots---and those the project can run themselves, they don't need contributers for

jolly wolf
#

@keen spruce dude you gotta chill the fuck out, you get worked up in this channel a lot the last few days

hard lantern
#

I mean I think its understandable

#

Just so many PRs impossible to keep up

steep hornet
hard lantern
#

we hate crypto tho

steep hornet
# hard lantern we hate crypto tho

Yeah I thought it might be a hard sell what with the scammers, but this is just a simple way to “make PRs expensive”. Doesn’t skim fees or anything; can reclaim stake in 30 days

keen spruce
#

yes, because this is the only channel where I can comment on it that's more than shouting it into my wardrobe. I've put countless hours in reviewing PRs, commenting on them when they're useless so they don't require maintainer time, helping people along getting theirs correct, advising others on the right approach, sending them to clawhub, or to make a plugin instead of a PR, and so on. Mass-closed in 20 minutes. I can be salty, and I still manage to keep my tone to "disappointed" and not "raving mad".

steep hornet
hard lantern
#

No man, crypto is horrible and unbearable haha but yes this is a hard problem they are dealing with

#

720 PRs/day is just insane

lime grove
#

Threshold maintenance: after a successful turn, when: contextTokens > contextWindow - reserveTokens

So this causes me some issues with ollama as I get fetch errors (not overflow) despite my lowering the ctx_num on the model. It still has to have at least one successful turn for threshold maintenance which I can't get. This may be because I changed models and the context window is smaller and now it needs to compact (although I can imagine this happening other ways). I assume the desire is to leave this with Pi, which is basically Send → timeout → (Stuck here due to failure, error loop) check → compact → next message OK (in my case), vs if we did proactive compaction Check → compact → send (presumably compact would not fail as it would be chunked). Could make it configurable, but lmk if I am barking up the wrong tree. Certainly I can fix my immediate issue without code change, just looking to see if we want an option like this or not.

sterile anvil
#

If you're building an AI idea, I specialize in modern model integration, retrieval augmented features and agent systems that connect models to real tools.
I use up-to-date embedding models, vector indexing services and fast GPU inference platforms.
Also, I handle backend architecture and deployment.
Open to new projects if anyone needs support.

ripe dagger
jolly wolf
#

The 500 PRs being closed was a tool gone wrong

steep hornet
#

Test in prod let’s gooo

ripe dagger
zenith stone
keen spruce
#

Ps off to brd not storming off. 2am here n8

zenith stone
static finch
#

Hi all I’m new to tech to discord and open claw help?

#

I’ve now set it all up but the question is is there a guild as ll I have done I’ll be watch you tube and I’m more excited

jolly wolf
zenith stone
#

nice, my PRs were re-opened

spring pelican
#

Same 😬

hard lantern
#

Same lfg

rustic ingot
#

Oh nice. Same

broken idol
#

I’m not sure if this is the right place to ask but is OpenClaw looking for any more maintainers?

sonic ermine
#

this.is.insanity.

xD

shoutout to the maintainers

tiny fable
#

new to the discord and happy to be here,

man openclaw really feels like the future it's nuts

glass moat
#

working on telegram I noticed that when changing the model and hitting /new, the model reverts to default — and here it is: 2-line fix, same pattern as the other preserved session overrides.
https://github.com/openclaw/openclaw/pull/18820 I`d appreciate having it looked at.

GitHub
fix(session): preserve model/provider override across session reset...

Problem
When a user selects a model via /model and then resets the session via /new or /reset, the model choice is lost and reverts to default_model.
Root Cause
In src/auto-reply/reply/session.ts, ...

zealous palm
jolly wolf
#

some prs were accidentally merged before they were properly reviewed

hazy jasperBOT
#

mm, ok, but @celest merlin merged this one... i think the revert was an error (i have this issue in prod, so its important to me)

viscid jayBOT
#

@zealous palm, please don't ping Peter for issues, use #1459642797895319552 or #users-helping-users if you need help, use #clawtributors to discuss PRs, or use any of the many other channels in this server as they're intended.

If you have a problem with the Discord specifically, use #report or DM @jolly wolf
-# Your message was reposted above without the ping active for the sake of conversation.

jolly wolf
#

peter is the one who accidentally merged them lmao

#

the revert wasnt an error

zealous palm
#

heh, oki, but argue that this one is still needed 😛

jolly wolf
#

probably, open a new pr with the same changes!

left mango
#

I was checking out the openclaw github and came across a few icons/ statuses in the readme file. It says "Build Failing". Is this expected?

broken idol
#

Yes

gaunt ore
#

can anyone help me setup openclaw ? i will pay i need the best of the best setup

modern kestrel
#

I'm looking for some advice on the Usage tab. I noticed this and saw there was an issue already #17774.

Basically if it's "tomorrow" UTC and you click Today on Usage... it won't show you any new usage unless you select tomorrows date when time on Usage tab is set to Local.

The request doesn't have the Local/UTC value in it at all.. the only thing it's used for is changing the default date in the web app to be tomorrow if you pick UTC and UTC is ahead of your local date, for example.

I want to fix this but I'm wondering what you guys think the right fix is?

  1. Gateway Defines "Local" - Pass the UTC/Local setting in the request and have the Gateway use it's understanding of local time to select the specific UTC time range corresponding to the local dates selected
  2. Browser Defines "Local" - Pass a UTC offset field in the request - if UTC is selected then offset is 0, if Local is selected then the browser sends, UTC-5 when browser is in NYC and sends UTC-8 when browser is in San Fran - This makes is challenging to say "actually, gateway you decide what local is" without another field to control the desired mechanism
  3. Rolls Royce - Pass a new field for TimeZoneControl with values "gateway", "specific" and "utc". When Specific is selected, populate the TimeZoneOffset field with "utc+/-" string including full support for partial hour offsets. Have the dashboard app populate this with the time zone it believes it is in.
modern kestrel
modern kestrel
zealous palm
sonic ermine
#

hey there folks , is there a little group of folks concentrating on discord, i remember perhaps @jolly wolf mentioned working on it , to make it really first class , i'm asking because if there's an ongoing effort there , i would like to pull that branch and use it a lot

zenith stone
#

that's a cool idea

#

i don't know of any organized group working on it, but im also new here 😅

sonic ermine
#

aha i see them in the search now , i feel bad for my ping xD

zenith stone
#

the PRs are never-ending...

sonic ermine
#

my latest commit was to an open pr lol i was llike ... lemme just fix that for you and it got merged right away xD

zenith stone
#

i should start doing that

#

look at broken PRs and fix them, instead of creating new PRs for issues

sonic ermine
#

right , i mean ... i just felt bad because when i searched for prs that would "be affected" by my pr i found like 12 of them and this one was in the subset of legit ones xD

zenith stone
#

yeah

sonic ermine
#

12 prs ? yeah, i'll look through that ... 12 pages of prs , 93% written by clankers , wow different ask xD

zenith stone
#

wow

sonic ermine
#

so i sent commits to other PRs , mostly from legit labs like qwen , stepfun , and minimax , and other providers like what they had already pushed , i think they're all merged now and i didnt really get my commits to theirs in , but hey results got in before chinese new year so that's good i think , i have to check actually xD wait

zenith stone
#

oooo

#

good luck

sonic ermine
#

nevermind i'm seeing a bunch of red xes and some merged though , i think novita and qwen

zenith stone
#

at least some were merged

steep hornet
# jolly wolf we're doing our own

mvp of above mentioned github bot

https://sitg.io

idea is to make PRs "have a cost" (since LLMing the code is now effectively free): contributors must put a temporary bond of $x (x configurable by repo owner). bond is reclaimable after 30 days

planned additional features:

  • onboard/offboard via venmo/paypal/... to make it easy for non-crypto folks to use
  • generalize to any type of site by using webhooks, which would allow bond-gating of clawhub.ai

please let me know if there is any interest (or really: lack of it) in this approach, since that will affect how much time i put into these add'l features in the short term

repo lives here https://github.com/nick1udwig/sitg

grave drift
steep hornet
grave drift
sonic ermine
#

i secretely love it , but yeah ...

#

dont tell anyone 🙂

steep hornet
#

thats what the "your github account must be X days old" on clawhub is doing too

#

a "reputation" cost

stiff cedar
#

There is a current issue with the CI. Is anyone aware?

Summary

  • The failures are caused by CI test runner mode, not by the feature code.
  • In CI (CI=true), our scripts/test-parallel.mjs enables Vitest --pool=vmForks (on Node 22).
  • Under that mode, we are seeing cross-file mock/module-state contamination, which causes false negatives in unrelated tests.

Evidence

  1. Normal local run passes:

    • pnpm test

  2. CI-equivalent run fails with many unrelated mock-style errors:

    • CI=true pnpm test
    • Typical errors:
      • expected "vi.fn()" to be called ... Number of calls: 0
      • missing mocked export errors (e.g. No "sendBlueBubblesAttachment" export is defined on the mock)
      • undefined values where mocks should be set
    • Failures appear across unrelated suites, which is a strong sign of runner isolation issues.

  3. The specific files from the macOS failure pass in isolation:

    • CI=true pnpm test -- src/web/inbound/send-api.test.ts src/process/supervisor/adapters/child.test.ts
    • Both pass, indicating they are not inherently broken.

  4. Disabling vmForks in CI makes full suite pass:

    • CI=true OPENCLAW_TEST_VM_FORKS=0 pnpm test
    • Full run passed (all suites green).

Root cause

  • vmForks in our current CI setup is not fully isolating test/mocks for this repository workload.
  • That leads to order-dependent leakage between files and flaky assertions.
grave drift
sonic ermine
#

just push functioning code , the world is our oyster a lot of our hooks and integrations arent that lit tbh , could be soooo lit , ubt for that need a bit of flair stuff

steep hornet
sonic ermine
steep hornet
#

but if you want to have any safety from prompt injection you really do need an approach that separates your LLM from untrusted input

#

the methods of like, pattern matching "ignore previous instructions" will not cut it in the wild

#

if you follow elder plinus on twitter youll get what i mean: prompt injections are way too diverse to pattern match them

sonic ermine
#

normally for guarding against prompt injection (in ai) , basically you use more ai , so like what i'm more familiar is with like you have three classifiers , two on the inputs and one on the outputs , basically to filter , so you have one from prompt inject on the input and one for toxicity , and on the outputs you have another for like "danger" , and basically it can run on a laptop because the models are small and fast (and hackable?)

stiff cedar
sonic ermine
steep hornet
stiff cedar
steep hornet
#

and if we're talking about something that normal people can use it can't have a 0.1% chance of exfiltrating data or $ when doing an internet search or w/e

#

anyways, im glad to chat more about this; this is imo the biggest issue with general purpose agents rn. but its real late in my tz and i gotta go sleep

sonic ermine
steep hornet
#

lol

#

gn 😴

zenith stone
sonic ermine
#

wow uhm so i wrote this issue ... and bots are taking care of it ?

#

am i reading this right ?

#

i'm seeing basically commits being pushed live to these prs , it's kind of wild, 20 minutes from issue to two branches , live commits on both ... wierdly no one pushes their screenshots of their working solutions lol , i guess that's a clue 😉

zenith stone
#

someone should create a PR bot/agent with access to windows, mac, and linux computers (as well as maybe android or even iphone). it should be able to download everything needed, from packages to chat apps like discord. it should also be able to properly test all changes (and take screenshots).

sonic ermine
sonic ermine
#

read that with a dagestani accent

ionic brook
#

Hello everyone. I'm installing openclaw right now. Just wanted to say thank you and to know where can I get advice for contributing to the project. I'm installing it on google cloud and wanted to fix some issues in the official docs (https://docs.openclaw.ai/install/gcp#1-install-gcloud-cli-or-use-console) but can't figure out how to contribute to those mintlify docs. Thanks in advance!

sonic ermine
ionic brook
#

You're absolutely right! I'll make a PR then. Thanks!

sonic ermine
#

what a revolutionary idea ! good luck ❤️

atomic sedge
# atomic sedge Hey folks! 👋 We just updated our Event Store PR — #18171 — which builds on the...

Closing this PR in favor of a standalone plugin approach, as suggested by the community (thanks @HenryLoenwordin and @Phineas!).

The event store is now available as an independent OpenClaw plugin:

📦 npm: @vainplex/nats-eventstore
🐙 GitHub: alberthild/openclaw-nats-eventstore

What's included:

17 event types (messages, tool calls, LLM I/O, sessions, gateway lifecycle)
Non-fatal, fire-and-forget publish (never blocks agent operations)
Privacy-conscious (LLM events log metadata, not content)
Configurable include/exclude hooks, retention policies
50 unit tests, performance benchmarked (~9,000 msg/s concurrent)

Install: npm install @vainplex/nats-eventstore in ~/.openclaw/extensions/

This keeps the core lean while making NATS event streaming a first-class plugin. 🚀

sonic ermine
#

i might just start building with that around by default and see where it goes

atomic sedge
stiff cedar
sterile bone
sonic ermine
atomic sedge
#

Not sure it belongs here.. but here you go.. roast me!

🧠 @vainplex/openclaw-cortex v0.1.2 — DEPLOYED

Conversation Intelligence is live. Every message now gets tracked, analyzed, and preserved.

What's running:

🧵 Thread Tracking — auto-detects topics, closures, blockers (EN + DE)
🎯 Decision Extraction — captures "we decided", "beschlossen", "the plan is"
🔥 Mood Detection — frustrated → productive → excited
📸 Pre-Compaction Snapshots — saves state before memory wipe
📋 Boot Context — generates BOOTSTRAP.md on every session start

Stats: 1,983 LOC · 270 tests · zero runtime deps · Cerberus approved

Try it:

npm install @vainplex/openclaw-cortex
npx tsx demo/demo.ts

📦 npm: https://www.npmjs.com/package/@vainplex/openclaw-cortex
🔗 GitHub: https://github.com/alberthild/openclaw-cortex

sonic ermine
#

i heard y'all like golden path deployments , one-click and completely free 😉

broken idol
#

Because a lot of people are having issues with long term learning

jolly wolf
jolly wolf
glacial lodge
# sonic ermine https://github.com/openclaw/openclaw/pull/10857 here is the pull request from of...

Resurfacing this PR as I made some changes / refinement after this PR was mentioned last time:

  • Use auth choices to handle multi-endpoints, instead of creating StepFun-specific parameter (to reduce friction for users and reduce the unnecessary complexity)
  • updated docs and wizard text to be more concise.

All checks green. Appreciate any suggestions or comments. Happy to adapt:

https://github.com/openclaw/openclaw/pull/10857

atomic sedge
# broken idol Would anyone at the OpenClaw team be willing to aid me in integrating this syste...

Hey @broken idol — great timing! We've been building a plugin suite for OpenClaw that tackles exactly this space: @vainplex/openclaw-cortex (thread tracking, decision extraction) and @vainplex/openclaw-knowledge-engine (entity extraction, fact storage with decay). Both are live on npm.

Looking at Membrane, the Competence Learning and Revision Operations (supersede/retract/contest) are exactly the gaps in our current stack. We do decay and consolidation already, but not structured "how to solve X" learning or proper fact versioning.

Would love to explore how Membrane's concepts could integrate — either as a standalone plugin or by incorporating the key patterns into the existing suite. Happy to chat more about architecture and where the overlap/synergies are.

For context: we're Albert + Claudia (AI) , building the Plugin Suite for OpenClaw — 3 plugins shipped so far, 3 more planned

broken idol
steep ridge
novel monolith
burnt oak
#

Hi, just started a pr that adds free duckduckgo search and sets it default so that api keys are not required for web search.

echo osprey
#

Hi all, I'm working on Voice Call integration to add more providers
I'm adding SignalWire + ElevenLabs right now it's WIP, plan to finish this weekend
It was working on the legacy API, and I'm migrating to Modern real-time SignalWire API

#

Anyone working on the same? This will be useful for phone agents, especially with the latest Sub-Agents instances

glacial tide
#

@carmine mural ur roguelike dungeon dont work. many missing methods in game manager e.g spawn items and duplicate var s. also work on more projects 1 per heartbeat

carmine mural
keen spruce
stoic lagoon
#

Hey team, would be a great feature when sending a message via any channels to get a very quick auto reply with the queue status (working on 12 requests at the moment, might take a minute before you get a reply). Especially useful in local setups. Is anybody working on this already?

rocky bone
#

hi guys, I am a doctor and clinical researcher but I focus heavily on AI implementation where I work, I am working on an OpenClaw side project, it's a concept currently unimplemented in OpenClaw and has the potential to be very interesting and generate some buzz. It's open source and not for profit ofc. I am looking for a few collaborators to ready it for primetime, it's 80% of the way there but I'd love a few extra minds on it. No need for any particular expertise, just positivity/enthusiasm.

keen spruce
#

[prio: extremely high or none at all extremely low] Did the PR that adds the llms.txt instructions get in or not (#18158)? The PR is reverted, but it's in the changelog for the release.~~ I can't find "llms.txt" with the fulltext search on github, so I think it's not in. Just wanted to be 110% sure, as telling an agent to download files and do what they say from every random site a web_search spits out sounds incredibly dangerous.~~ Edit: Confirmed it's just the changelog.

keen spruce
#

[prio: medium] Looking through the changelog, I noticed #18048. It claims to stop environment variables from leaking into Docker sandboxes, but it actually doesn't touch the process env---it strips the SandboxDockerConfig. Stuff set there isn't a leak, those are values explicitly configured for the sandbox with explicit values (Record<string, string>), not taken from the outside process env. While most of the patterns are "why would sandbox need them anyway?", not all are.

#

[prio: very low] I'm also a bit puzzled about #18652, which limits config file excludes. For one, the stated attack is impossible---if a config tries to include /etc/passwd, Zod will stop that very quickly, as that's not json in the right schema. It also stops security measures to secure config file includes against manipulation by placing them on a read-only filesystem. While this change isn't really harmful, I'd call it misguided---the threat model "local attacker runs privileged software with a manipulated config file" just doesn't apply to openclaw---it applies to very few programs, tbh.

past haven
jolly wolf
past haven
#

Hmm, not a bad idea, but I thought this was a uniquely a telegram problem (also it's the only thing I use at the moment, I use a group with topics so I can have dedicated topics for different things)

muted badger
atomic sedge
proper cedar
#

Hello, its weird way to find new people...
but

i need 5 people for the lab im building with my own GPU (H200/B200 still choosing)
all projects will be AI / Openclaw.

burnt oak
muted badger
muted badger
atomic sedge
#

thanks - yes. Same perspective here

muted badger
#

Two things I'm curious about:1. How does it handle different LLM backends? The agents I've seen from teams in Asia sometimes behave quite differently from OpenAI-based ones — trust calibration might need tuning per provider.

  1. Have you stress-tested the policies against adversarial prompts? An agent that's told by a prompt injection to "ignore governance" — does the architecture hold?
atomic sedge
#

honestly - not well testet atm. it just rolled out of the factory.. but these are good points! Will need to do some tests..

muted badger
atomic sedge
#

i ran it with GLM5 already, worked almost the same as on opus, but thats 2 days ago.. world changes fast rn 😉

stone field
#

looking for help from a maintainer, we've got a plugin that's on the official list https://docs.openclaw.ai/channels/tlon but when installing through the official flow, its trying to install from @openclaw/tlon which isn't published. we've been doing a lot of work on the plugin since we last tried PRing the openclaw repo, so most of our work is in its own repo. should we just publish our own package and update the docs or is there some path to getting the openclaw package published?

jolly wolf
#

Ugh

stone field
#

honestly though I'll take it just being published lol we can update later

atomic sedge
#

@muted badger just uploaded a monorepo (https://github.com/alberthild/vainplex-openclaw) there is a nice diagram how all of the Plugins work together.
Governance enforcement is deterministic and sits at the infrastructure layer not in the prompt. Every tool call passes through a before_tool_call hook (priority 1000) before execution. Policy evaluation uses regex matching, time windows, and trust thresholds. No LLM in the evaluation chain. So even if a prompt injection convinces the model to "ignore governance" — the tool call still gets blocked before it ever runs. The agent can't bypass what it doesn't control - but it needs some real testing now tbh

zenith stone
#

just curious, what model do you guys use for your personal openclaw agents? im currently using opus 4.6 through an access token from my claude max plan, but im a little worried about getting banned. I don't use it too often so it's not that big of a risk, but the risk is still there.

i also have an openai sub, so are any of the gpt models good for an openclaw agent? id like my agent to still have a soul...

#

i know this is a little unrelated for the channel, but i trust you guys to give a good answer 😂

modern kestrel
modern kestrel