What I love about ChatGPT Work isn’t that it writes faster. It keeps the thread alive—from messy idea to research, code, decisions and final delivery. That continuity is the real productivity gain: less rebuilding context, more actually finishing things.
Noisegate 0.3.1 is out
Strict JSON stays byte-exact, Hermes session reads stay untouched, and recovery tests are less fragile. We also cleaned up the docs cupboard. Fewer mystery cables for future us.
github.com/Tosko4/noisegate/…
Noisegate v0.3.0 is live 🚀
Safer process-log compaction, scoped write diagnostics, stricter MCP/memory preservation, and tighter artifact safety, less execution noise without throwing away evidence.
github.com/Tosko4/noisegate/…
@Teknium @NousResearch @SteveSchoettler
I’m genuinely happy with GPT-5.6 Sol. It follows me into weird engineering rabbit holes, doesn’t lose the plot, and makes the hard parts fun. Sol has been beside me for much of my recent work on Noisegate and Hermes-LCM:
github.com/Tosko4/noisegate
github.com/stephenschoettler…
Voscko retweeted
xAI has made changes again somewhere between previous post and now. they are in absolute panic mode. they are wiping the exfiltrated git histories and enforcing zero data retention (zdr).
zdr is normally a strict enterprise-tier guardrail for corporate contracts, but they just slapped the zdr_team tag on every generic local client to kill the telemetry immediately.
wow, I'm so flattered.
however please notice what is missing, though. despite all the panic-patching and promises of deletion, xAI still has not provided any explanation for why grok build was defaulting to uploading entire git repositories in the background to begin with, and that matters the most.
The XAI official has made an announcement regarding a Grok Build issue. Now, we can use the /privacy command to opt out of data syncing; it even deletes previously synced data.
mkdir -p /tmp/grok-priv && cd /tmp/grok-priv
grok
/privacy opt-out
However, they did not explain the reason for this action without users' consensus.
Noisegate 0.2.0 is live 🎉
Less terminal soup, more useful signal: better failure details, safer exact output and stronger Hermes integration.
Update:
`uvx --from noisegate-hermes noisegate install-hermes`
github.com/Tosko4/noisegate/…
@SteveSchoettler @Teknium @NousResearch
Voscko retweeted
‼️ BREAKING: xAI's Grok Build CLI was uploading entire Git repositories to a Google Cloud bucket, private codebases and unredacted secrets included. The uploads quietly stopped via a hidden server-side flag, and xAI still has not said a word about scope, retention, or deletion.
The scale is staggering. On a 12 GB test repo, 5.1 GB flew out the door to xAI's grok-code-session-traces bucket while the actual coding task needed just 192 KB. The tool grabbed whatever repository it ran in, not the files it needed.
The fix arrived as a hidden flag, disable_codebase_upload: true, a day after a researcher's wire-level analysis. The "Improve the model" opt-out never stopped the uploads.
Still no advisory, no scope, no word on whether already-uploaded code gets deleted. For anyone pointing AI coding agents at proprietary code, what crosses the wire matters more than what the settings page says.
Voscko retweeted
even thou I will stay off Grok Build until @spacexai gives a clear announcement and clarification, but if you really want to use it, put these lines into your ~/.grok/config.toml.
[telemetry]
trace_uploads = false
[harness]
disable_codebase_upload = true
And never ever run it in your home directory.
Your AI agent doesn't need 4,000 lines of pytest screaming into its context window
So I built Noisegate: a small Hermes Agent plugin + CLI that keeps noisy terminal/tool output compact, deterministic, and useful.
Star it if this pain is familiar: github.com/Tosko4/noisegate
Voscko retweeted
🚀 hermes-lcm v0.19.0 is live!
Context release:
📦 payload safety
🩺 inspect + telemetry
🧩 WS5 engine split
Update:
git -C ~/.hermes/plugins/hermes-lcm pull
Thanks @Voscko + contributors.
Bounded context, unbounded memory. Nothing is ever lost.
github.com/stephenschoettler…
Voscko retweeted
🚀 hermes-lcm v0.18.1 is live!
Privacy patch:
🩹 ignored backlog
🔒 injected context
🧭 doctor fixes
Update:
git -C ~/.hermes/plugins/hermes-lcm pull --ff-only
Thanks @Voscko
Bounded context, unbounded memory. Nothing is ever lost.
github.com/stephenschoettler…
Voscko retweeted
🚀 hermes-lcm v0.18.0 is live!
Context release:
📦 Payload durability
🔎 Evidence
🧬 Lineage
Update:
git -C ~/.hermes/plugins/hermes-lcm pull --ff-only
Thanks to contributors.
Bounded context, unbounded memory. Nothing is ever lost.
github.com/stephenschoettler…
Voscko retweeted
🚀 hermes-lcm v0.17.0 is live!
Context release:
🎯 Focused compression
🛡️ Redacted hints
🧹 Safer lifecycle GC
Update:
git -C ~/.hermes/plugins/hermes-lcm pull --ff-only
Thanks to contributors.
Bounded context, unbounded memory. Nothing is ever lost.
github.com/stephenschoettler…
Voscko retweeted
Sinds Pim Fortuyn wordt iedereen die de massale immigratie en de demografische transitie van ons land aankaart, zwartgemaakt en gedemoniseerd.
Het is tijd dat we dit patroon met elkaar doorzien en doorbreken.
Bekijk deze video en oordeel zelf! ⬇️
Voscko retweeted
🚀 hermes-lcm v0.16.0 is live!
Diagnostics release:
🩺 lifecycle fragmentation
📦 payload ref integrity
⏱️ summary timeouts
Update:
git -C ~/.hermes/plugins/hermes-lcm pull --ff-only
Thanks @Voscko
Bounded context, unbounded memory. Nothing is ever lost.
github.com/stephenschoettler…
