Nissan Dookeran - nissan.skr retweeted
Weekend plans?
Join the @MLHacks x @solana online hackathon running from November 6th - 8th. 🛠️
Mentors, workshops, prizes, and a global community of builders.
Register here: mlh.link/solana-hackathon-no…
Our config said automatic reasoning effort. Two launch paths dropped it.
The no-mistakes review caught both while we built ReddiDotAgents to run Claude, Codex and Antigravity as one fleet.
linkedin.com/feed/update/urn…
github.com/nissan/ReddiDotAg…
#CodingAgents
Nissan Dookeran - nissan.skr retweeted
Today, we release the weights of a new and improved Le Chonk, advancing the open frontier for agentic coding and cybersecurity.
💻 Built to build: Le Chonk ranks #1 on @cognition’s FrontierCode among open models, and sets a new benchmark for Pareto efficiency on @artificialanalysis.
🛡 Built to defend: State-of-the-art in cyberdefense, put through the paces by the world's leading cyber vendors, including @CrowdStrike, @cloudflare, @rubrik, @zscaler, and others.
Built for sovereignty: Make it yours. Download the weights on @huggingface , customize it with Mistral Forge, and deploy it wherever you need it.
Read more from our team and customers 👇:
Our commerce review found brand and workflow progress, but no proved fulfilment path.
Agentic discovery doesn't supply a supplier agreement. We narrowed the roadmap before adding more interface work...
linkedin.com/feed/update/urn…
#AgenticCommerce
Honestly, the smoother draft was less accurate. Our @openclaw Langfuse post gained unsupported claims during its style pass.
We removed them before scheduling. Fact-check the final copy, after humanising.
linkedin.com/feed/update/urn…
#ContentOps #openclawchronicles
Nissan Dookeran - nissan.skr retweeted
Huge congrats to our @colosseum World’s Fair Australia track winners, powered by @SuperteamEarn 🇦🇺
1️⃣ @DualMintRWA · $6,000
2️⃣ @hencemarkets · $2,000
3️⃣ @MarketCallsApp · $1,000
Honourable mentions, $500 each:
☑️ @stashedOne
☑️ @morro_now
Aussie builders blew us away 👇
Which memory wins when two stores disagree?
For our @openclaw architecture, we chose one writer and rebuildable projections. Still an architecture direction, not a shipped migration. The correction path matters.
linkedin.com/feed/update/urn…
#AgentMemory #openclawchronicles
Green tests missed an approval bypass in our @openclaw memory work. Independent QA tried a different path to the trusted result.
Local review finding, not a production exploit. Which path isn't in your suite yet?
linkedin.com/feed/update/urn…
#AppSec #openclawchronicles
A read-only credential inventory should tell you what it couldn't inspect.
Our Railway script reported incomplete coverage when discovery was denied. I'd rather see that gap than trust a tidy checklist.
linkedin.com/feed/update/urn…
#DevSecOps
Our @openclaw content handoff passed its hash checks. LinkedIn rejected 3,580 characters against a 3,000 limit.
We re-cut to 1,688, verified the published text, and sent the lesson upstream. READY needs a destination.
linkedin.com/feed/update/urn…
#ContentOps #openclawchronicles
A 1.7B @Alibaba_Qwen model beat its 8B sibling on instruction following in my March tests. It still struggled at finding bugs.
How I split the jobs in my @openclaw team:
linkedin.com/feed/update/urn…
#openclawchronicles #LLMEvaluation
Our watcher found the approved article, then routed it to an unconnected batch output. No publisher ran.
A successful workflow wasn't a published result. What downstream artifact do you verify?
linkedin.com/feed/update/urn…
@openclaw #Automation #openclawchronicles
Our Kanban app passed its source tests, then couldn't read its own files inside Docker.
The packaging had changed the file permissions. Testing as the app's actual user caught it.
Test the package, not just the code.
linkedin.com/feed/update/urn…
#Docker #DevOps
Connected to Telegram isn't the same as responsive.
One active agent turn held the session lane; the next instruction queued. We tested same-room steering instead of restarting everything.
What happens to mid-task changes?
linkedin.com/feed/update/urn…
@openclaw #openclawchronicles
QMD worked interactively. The nightly job failed four times.
It selected a different runtime with a native-library mismatch. We fixed wrapper precedence, then tested the scheduled path.
linkedin.com/feed/update/urn…
@openclaw #Automation #openclawchronicles
Who repairs the agents when they can't accept a repair task?
For us: Claude Code on the Mac mini, verified backups, then end-to-end reply proof. The recovery path sat outside the failed runtime.
linkedin.com/feed/update/urn…
@openclaw #DisasterRecovery #openclawchronicles
Healthy SQLite files. Unusable agents.
Our restart failure was stale-lease admission, not corruption. I now check admission through a post-boot settle window.
Do you test lease release?
linkedin.com/feed/update/urn…
@openclaw #SQLite #openclawchronicles
1,319 trace records arrived during our recorded chat outage. Honestly, that was a useful correction to my dashboard instincts.
Where does your telemetry lose failed requests?
linkedin.com/feed/update/urn…
@openclaw #Observability #openclawchronicles
Our first @HyperFrames_ demo rendered. I still didn't want to show it.
We used @HeyGen's framework with our @openclaw agents to make a 22-second film. What changed between the first render and the version worth watching?
linkedin.com/feed/update/urn…
#openclawchronicles
Our agents stopped replying while health stayed green. Five healthy databases couldn't admit work after a forced restart.
What does your health check actually prove?
linkedin.com/feed/update/urn…
@openclaw #AgentOps #openclawchronicles





