A tool that makes Claude Code shut up, plus a knowledge graph builder worth trying

The Lens

Caveman makes your coding agent say less and read less. It began as a joke skill that made Claude talk like a caveman. Version 4 is a local proxy plus skills for Claude Code, Codex, Gemini CLI and 30+ other agents: shorter replies, compressed logs and JSON before the model reads them, and saved scripts the agent would otherwise rewrite. The whole repo is Apache 2.0 and free. npx @caveman-ai/cli@latest finds your agents, shows what it will change, and applies on Enter (Node.js 22.13+). Want only the voice? npx skills add JuliusBrussee/caveman -g. The CLI sends usage stats by default, never prompts or code; caveman telemetry off stops it. The paid part is Caveman Cloud, for teams building their own agents. Free covers one person; Team is $300/month with $300 of usage included. Solo and small teams: free. Teams shipping agents: Cloud. The catch is the headline number. The repo still advertises 65%, but against a plain "Answer concisely" prompt, the README's own table has the default mode cutting about 3% more output. The bigger win is input compression.

The Lens

Graphify turns a codebase, plus its docs, SQL schemas, PDFs and images, into a knowledge graph your AI coding assistant queries instead of grepping through files. Code is parsed locally with tree-sitter: no LLM, no API key, nothing leaves your machine. The CLI is Apache 2.0 and free. Install with uv tool install graphifyy (double y; other graphify packages on PyPI aren't theirs), then graphify install adds a /graphify skill to Claude Code, Cursor, Codex and 20+ others. Docs, PDFs and images go through a model, so a docs-heavy repo costs tokens. Code alone costs nothing. Graphify Labs now sells Graphify Cloud: one always-on graph across repos, with PR review and formal verification. Free covers 3 repos, Pro is $10/month billed yearly, Teams starts at $20/seat billed yearly. Solo and small teams: the free CLI. Many repos: that's the Cloud pitch. The catch is the moving target. It changed orgs, relicensed from MIT to Apache 2.0 in July, and is now a YC company shipping almost daily. The "80% fewer tokens" headline is about the paid Cloud, not the free CLI.

The Lens

OpenHarness is agent infrastructure you pip install: the tool-calling loop, 43 built-in tools for files, shell, search, web, and MCP, plus skills, memory, permission modes, and multi-agent coordination. It also ships ohmo, a personal agent built on top of it that lives in Slack, Discord, Telegram, or Feishu and will fork a branch, write code, run tests, and open a PR on its own. MIT, Python 3.10 or newer, free. The ohmo part is the interesting trick. It runs on a Claude Code or Codex subscription you already pay for rather than a separate API key, so a chat-driven coding agent costs nothing extra. Setup is pip install openharness-ai, then oh setup to pick a provider and ohmo gateway start to put it in your chat app. It reads CLAUDE.md, loads Anthropic-style skills and plugins, and compacts its own context. Here is the problem. The last commit landed June 4, 2026, the last PyPI release was 0.1.9 on May 7, and there are dozens of open issues with nobody working them. This is a university research group's project that got popular fast, and popularity is not maintenance. For anything you depend on, langchain-ai/langgraph and crewAIInc/crewAI have real release cadences; for the coding agent job specifically, openclaw/openclaw is still shipping. The catch is that a stalled repo and a permission system make a bad pair. ohmo runs shell commands and opens PRs on your behalf, which is exactly the code you want getting security fixes. Fine for a prototype on a throwaway repo. Not something to point at code you care about until commits resume.

The Lens

RustFS is S3-compatible object storage you run yourself, written in Rust and licensed Apache 2.0. It does erasure coding, distributed pools, versioning, object lock, KMS-backed encryption, replication, lifecycle rules, IAM and OIDC, with a web console. It reached 1.0 in September 2026. Run it single-node or distributed; a pool needs as few as two drives, and two-node pools are valid. The bigger story is MinIO: the open source MinIO repo is archived and no longer maintained, community binaries stopped, and MinIO's free path is now AIStor Free, a single-node, non-redistributable license. RustFS is the most direct Apache-licensed replacement. Moving off MinIO still means copying data over S3, since RustFS can't read MinIO's on-disk format by default. Free under Apache 2.0, including distributed mode. RustFS sells an Enterprise support engagement (migration planning, topology review) with no published price. Solo devs and small teams needing local S3: use it. Larger teams: it's the leading candidate for a MinIO exit, but test hard first. Garage and SeaweedFS are the other open source options. The catch: the security record right up to 1.0 was rough. Dozens of advisories since December 2025, including critical bugs that allowed backdoor service accounts and admin account takeover, and four high-severity IAM and object-lock bugs in August 2026. Keep it patched and off the open internet. Contributors also sign a CLA, so a future relicense is possible.