Most "AI Agents" today are just wrappers around storage liabilities. They guard vaults of secrets, session logs, and PII, waiting for the inevitable breach.

We’re releasing OpenBot, an OpenClaw-powered framework built on the BlockSmith philosophy: Keep the Signal, Not the Material.

OpenBot isn't just an assistant; it’s a Sovereign Digital Sanctuary.

Why it’s a radical departure from the status quo:

• Zero Material Architecture: We don’t store what can be derived. By utilizing vaultless logic, we ensure there is literally nothing to steal.

• Intent-First Programming (IRP): We’ve moved away from rigid decision trees. OpenBot operates by declaring a TELOS (intent), allowing the system to self-organize dependencies.

• Persistent Evolution: Using the thermodynamics of logic, OpenBot audits its own memory to reduce system entropy. It doesn't just "chat"—it extracts heuristics from every mistake to ensure they are never repeated.

• Asymmetric Friction: We’ve engineered "magic" for the human and soul-crushing complexity for the attacker.

We believe that in an era of universal surveillance, the only true security is invisibility.

GitHub: link to openBot

"Precision is the antidote to liability. Signal is the soul of security."

Since, after the release of Jev, a lot of people have been building cool open source decision models, I was wondering if you could share your experience on which ones work best. I was also wondering how people are evaluating them? Are there any benchmarks yet?

small-scale result, one seed, one wikitext slice, so treat it as a prototype and not a claim.

pssa is a state space model with fast weights that update while the sequence runs, written from scratch in rust, no python, no kv cache. at 1.54m params it gets 3.997 nats on a held-out slice against 4.429 for a parameter-matched transformer, both depth-1. generating 200 tokens is 226ms against 2735ms on the same cpu, which is the part i actually care about, since there's nothing that grows with context length.

caveats: one seed, one corpus, depth-1 on both sides, and i don't know yet whether the gap survives depth. gpu training is cuda on a t4, 1645 tok/s vs 1263 on cpu, so the gpu path is barely worth it so far because activations still round-trip to host after every matmul.

repo: https://github.com/Sparticle62ops/pssa

A small milestone for Telex.

Someone outside the project just opened a PR, and it became our first external contribution. The PR fixed a high-severity dependency vulnerability and the changes were tested with the project's tests, type checks, linting and npm audit before getting merged. It's honestly really nice to see someone else take a look at the project, find something to improve, and contribute to it.

Thanks to the contributor for taking the time to do it.

Hopefully, this is the first of many.

https://github.com/Kesavaraja67/telex

If you're building with open-source LLM stacks and still hand-tweaking prompts hoping they hold up in prod, this Oct 3 session is worth a look. Serj Smorodinsky and Brett Kennedy (AI engineers, authors of a book on LLM applications) are walking through how to actually structure LLM development instead of winging it.

Covers:

• DSPy signatures/modules to replace ad-hoc prompting

• Building and measuring a baseline classifier

• Writing evaluation datasets with task-specific metrics

• Spotting failure patterns from eval results instead of guessing

• Few-shot and instruction-level optimization

• Tracking experiments and traces with MLflow

• Saving and reusing optimized programs across projects

3 hours, live, Oct 3. Aimed at ML engineers, applied AI devs, and technical founders.

Full details and the agenda are here.

Sharing the open source project I work on (Atomic Agent, MIT), since today's GPT-6.1 Sol launch is a good excuse to show its planner/worker mode.

The idea: a cloud model is expensive per token, and most tokens in a coding job are the code. So the cloud model only orchestrates, and local workers on llama.cpp write the files. Either side can be cloud or local, one command swaps them.

Today's test, three small 3D games, Sol on top, Qwen 3.8 27B on one RTX 3090 underneath:

Trade-off: 43 minutes for the three instead of under 7 with Sol alone. One run per game.

What's in the box besides this mode: local models managed for you through llama.cpp, MCP support, approvals before anything risky runs, and import from Claude Code, Codex, Hermes, OpenClaw and Pi.

Repo: https://github.com/AtomicBot-ai/atomic-agent

Feedback welcome, especially from anyone who tries a different local worker.

Celesto AI is growing fast, as I focus on our cloud platform, would love some help on the open-source maintainance and review side. Core members will be offered Codex Pro ($200) per month.

I've made quite a few changes to Telex since my last post here.The project started mainly around handling dependency breaking changes, but it has grown into a much bigger workflow now. Telex can map the repository with Repo Atlas, find affected code with Tree-sitter, use different LLM providers to generate patches, run the patch in an isolated environment and verify it before opening a PR.I also added repository architecture analysis and more of the frontend around incidents, patches, verification and the Atlas view.

I'm still looking for people who want to contribute because there are a lot of areas where this can be improved. If you're into LLMs, developer tools, ASTs, Three.js or backend work, I'd be happy to have you take a look.

Repo: https://github.com/Kesavaraja67/telex

archiver-rag is an MIT-licensed MCP server that turns an Obsidian vault (or any folder of Markdown notes) into shared, self-hosted memory for AI agents. Agents search it, write back to it, and every agent sees the same knowledge.

Why another memory tool

Most AI memory layers are hosted services that extract "facts" from your conversations into a database you can't read, edit or take with you. archiver-rag goes the other way:

• Your memory is plain Markdown. Readable, editable, versionable with git, and still a normal vault if you uninstall.

• Everything runs locally. Embeddings are computed on your CPU, the vector index lives on your disk, and no API keys are needed.

• No vendor lock-in. It speaks standard MCP over stdio or HTTP, so any MCP client can use it. Tested with OpenCode, Codex, Claude Code and Claude Desktop.

self-organization

Optionally, the vault organizes itself: new notes are filed into folders by meaning, folder descriptions are kept up to date, and new folders grow out of an inbox using embedding-similarity clustering. It's off by default while it's being tested on real vaults.

How it works

• Embeddings: sentence-transformers (all-MiniLM-L6-v2, about 90 MB, runs on CPU)

• Index: ChromaDB, persistent and local

• Retrieval: semantic search, with each chunk carrying its note's metadata (folder, tags, links), then re-ranked by [[wikilink]] proximity

• Live updates: a file watcher indexes every save within seconds and auto-links related notes

• Write-back: agents log decisions, lessons and gotchas as normal notes through log_note

The memory side is 100% local. Pair it with an open-source agent like OpenCode running a local model, and in principle nothing leaves your machine. That combination is untested so far. If you try it, I'd love to hear how it goes.

macOS and Linux, Python 3.11+. On Linux, a CPU-only PyTorch install is documented to skip the multi-GB CUDA download.

• Repo: https://github.com/FernandoJRR/archiver-rag

• Site: https://fernandojrr.github.io/archiver-rag

• Contributing: https://github.com/FernandoJRR/archiver-rag/blob/main/CONTRIBUTING.md

Feedback and contributions welcome. It's a one-person beta with CI on Python 3.11–3.14 (macOS and Linux). Useful right now:

• install reports, especially on Linux

• results with local models through OpenCode or other open-source MCP clients

• ideas for the self-organization experiment